This model provides a steady stream of posts for students to read and respond to. See http://instructors.cwrl.utexas.edu/tnelson for a sample, though keep in mind that this model is not oriented toward a finished product. Unlike the book model, this model does not create a fixed document of the course. It users the front page or instructor's blog rather than a dedicated node, so is by nature transient.
Rationale
Using a blog as the main web interface for a class allows for frequent, reflective instructor updates and greater student interaction. Such a class interface is not only administrative resource (as a repository of documents and assignments), but an extension of class discourse. Since a blog enables frequent updates and arranges them chronologically, this course page becomes a fluid text, reacting to and recording classroom events. Instructors can elaborate on the material presented, reflect on events in class, and solicit reactions from students (posted as comments). With comments, students can ask questions to which instructors can then either answer or ask other students to respond. New questions or directions for the class can arise from this exchange.
Content
Because the purpose of a CMS is to manage content, this model could draw on an existing body of blog posts. If for instance you used Moveable Type as a course interface, you could consider importing individual entries into Drupal for reuse. (At this point, cutting and pasting is the easiest option. We are looking for a good automated transfer from Moveable Type.) If you used categories in MT, you can recreate them in Drupal (see Taxonomy above). Otherwise, consider devising a descriptive taxonomy based on rhetorical concepts, class business, etc.
If you enable the privacy by node module, you will be able to restrict access of your posts until such time you decide to make them public. Using the search function and taxonomy terms, you can find posts which you can then adapt for use.
Adminstrative Settings
Go to Administer>Modules and make sure the following are enabled: blog, book, comment, node, node privacy by role, search, taxonomy, and any other modules you might like to use.
Go to Access Control and make sure the modules have the proper permissions: probably read for anonymous, authenticated or enrolled status to post comments. You may want to reserve Search for Administrator use only.
Go to Content>Configure>Content Types and set the default permissions of the content type you wish to use (blog or book). Make sure to grant the Administrator permissions for View, Edit and "Permissions for Permission" (for privacy).
While this model is based on blogs, you can use book pages to fit posts into hierarchies. Enabling book blocks will create a menu that shows users how a post figures into the overall course.
This model can also incorporate individual student blogs, forums, and other options.