Hi, In general, I think that building a new outline from scratch and then populating with existing/new content is a good idea, as it allows us to break from the organically-grown content where it's hard to find what you are looking for.
Having a clean, properly structured documentation tree where everything is sensibly / logically placed is a big +1. I see the biggest issue here as a clean split between reference material and usage/howto material. As ever, we need to be careful not to throw the baby out with the bathwater though: - can we be sure we have enough time to rebuild all docs from scratch? - can we be sure that in the interim, three sets (2.0, 2.1, -docs) will be maintained? I also *really* want to get my thoughts on merging/versioning and literate programming together before we do this (since it should reduce effort significantly in the long term), but I'm fighting with several deadlines that I won't be clear of until after the weekend. Andrew. -- Andrew Savory Email: [EMAIL PROTECTED] Managing Director Tel: +44 (0)870 741 6658 Luminas Internet Applications Fax: +44 (0)700 598 1135 This is not an official statement or order. Web: www.luminas.co.uk
