Starting with Lift - the official guide

Contents
1 Welcome to Lift!
1.1 Why Lift?
1.2 For more information
1.3 Your first Lift application
2 Basic Lift
2.1 What we’re going to cover
2.2 Creating a new project
2.3 Adding a model
2.4 Boot and Schemifier
2.5 Snippets: Bridging View and Logic
2.6 Lift’s “View First” design
2.7 Updating the ToDo view
2.8 Seeing if the snippet works
2.9 Creating a to-do item
2.10 Updating the priority and desc fields
2.11 Hooking up the view to the form
2.12 Trying it out again
2.13 Display and Editting to-do items

Lift project tutorial

Steps for Setting up a Lift website

Lift AMQP with RabbitMQ and Scala - Tutorial and Screencast

"AMQP – Advanced Message Queuing Protocol to the lay’ man not familiar with the acronym. Essentially AMQP is an open standard for enterprise messaging. There are several implementations of the standard, namely, Open AMQ and RabbitMQ – the latter is newer and generally considered to be the defacto implementation. Rabbit MQ is written in ERLang and has clients for Java, .NET, Ruby etc etc."

First Steps to Scala by Bill Venners, Martin Odersky, and Lex Spoon

Now that you've worked with Scala variables, you'll probably want to write some methods. Here's how you do that in Scala: scala> def max(x: Int, y: Int): Int = if (x < y) y else x
max: (Int,Int)Int
Method definitions start with def instead of val or var. The method's name, in this case max, is followed by a list of parameters in parentheses. A type annotation must follow every method parameter, preceded by a colon in the Scala way, because the Scala compiler (and interpreter, but from now on we'll just say compiler) does not infer method parameter types. In this example, the method named max takes two parameters, x and y, both of type Int. After the close parenthesis of max's parameter list you'll find another “: Int” type specifier. This one defines the result type of the max method itself.
Sometimes the Scala compiler will require you to specify the result type of a method. If the method is recursive1, for example, you must explicitly specify the method result type. In the case of max however, you may leave the result type specifier off and the compiler will infer it. Thus, the max method could have been written: scala> def max2(x: Int, y: Int) = if (x < y) y else x
max2: (Int,Int)Int
Note that you must always explicitly specify a method's parameter types regardless of whether you explicitly specify its result type.