> The phasing in my mind was start with the content and then phase 2, core > build and deployment changes. For the users of Cassandra, my initial big lift > was giving them first class docs(and are they?) > > The items you mentioned are when I start moving things over to trunk, and > yes, there will be a lot of things to get th…
My concern here is that you're putting the cart before the horse – you can't commit any of the new docs until you can build them the way they get built for the website. So, I guess, you have to be extra clear with folk that phase 1 is only content and layout review, and that those things may change and need to be reviewed again after phase 2. when the build is fixed/adapted. Take for example Scott's mention about rendering latex, that's moot because it can and will change again. If phase 1 is what you need as the driving force for motivation and to bring in collaboration, that's fine by me, just so long as everyone understands the above.
