Well, I was fixing issue #13 (add detail for snippet dispatch) and I decided that the whole Fundamentals chapter was just becoming one big pit of "put everything in here". In an attempt to try and make the chapters more logical, I ripped out most stuff related directly to snippets from "fundamentals" and put it into its own "Snippets" chapter. I'm seriously considering reworking the sections more into something like:
- Welcome
- PocketChange - needs a lot of embellishment, commenting, etc
- Fundamentals - change this to talk mostly about Boot, LiftRules, package resolution, and other things that are more "central" functionality. I'm not sure if I should briefly touch on things like Snippets, Templates and SiteMap here, or if it would be better to show and discuss in the PocketChange chapter...
- Templates and Views - basically, how do we get from request to template XML? Probably also include things like rewrite here, since that's roughly this stage of the chain
- Snippets
- Forms
- SiteMap
- Mapper and (a much improved section on) Record
I think that I can take parts of the "Advanced Architecture" chapter and move them into their respective chapters. I feel like that's probably a better way to organize things than to make people flip between chapters for all things Snippet, say.
As for Lift 2.0 specific stuff, The things I'm planning on adding are:
- The new Menu DSL
- Screens and Wizards (maybe their own chapter?)
- Revise the Web Services chapter to show the new REST API
- Maybe a chapter on the new JSON support, or at least a big section in the JavaScript chapter
- Touch on CouchDB and MongoDB support
Thoughts on the reorg or what I should be covering vis-a-vis 2.0?
Derek