Ok, no need to rush it. If I get some stuff ready before next week, I'll just mail / PM it to you so you can have a look at it and comment on it. Besides, if we want to make a documentation that's good, all chapters should fit together...
The basic structure I had in mind is actually quite similar to the old document's:
- Note for PB 2.5 waypointers (short info o what's new and which chapters ought to be read with priority
- What are waypoints? (Explanation for newbies, basic principles)
- List of commands / meu items and functions (maybe some hints about binding here? A link to this script thingy? A sample waypoint.cfg to go with the docs? Just thinking...
- List of all waypoint types plus some brief explanation (nothing about fine-tuning or difficult cases yet, just basic functionality)
- A list of all connection types (what connections exist and how to add / del them)
- Common mistakes / things to avoid
Very similar to the original doc indeed. This first doc would teach ppl to use the WP editor, but will focus more or less on the technical point of view, with just some very general hints and strategies.
I was always planning to write something about the more complicated tricks (ledges, ladder bug, WPs inside walls, where to place camp WPs, how to balance a map etc.) ... I wonder if it would be a good idea to place links to it in corresponding sections of the basic doc (like "if you wanna know more about ladders, click here)... but maybe it would be too much work to update all those links when a new release comes. Nah, maybe two static docs would be better...
Ok, this is just a first general idea of how I'd do it... I'm always open for different ideas suggestion, of course. I don't want to say "that's the way we're gonna do it", just post some of my thoughts...