> 1. Real hard-core documentation that describes a particular part of Piper > design or use. I agree with you that this should be done in LaTeX (or > rather, the format of whoever works on it first). > > 2. Documentation on ideas, design discussion, and "softer" documentation, > like how to install Piper, how to get started coding on Piper, ToDo > lists, etc. The distinction between this and "hard-core" documentation is > that this stuff is more likely to change regularly, and have multiple > people contribute to it (ie. to make install instructions more clear, add > to a discussion, etc). Anyways, I am for this type of documentation being > done in Wiki. Sounds reasonable. In the worst case, we'd just switch from Wiki to standard HTML, which is easy to do. I agree that what you call soft doc is mostly useful in HTML form anyway. Jean-Marc -- Jean-Marc Valin Universite de Sherbrooke - Genie Electrique valj01 at gel.usherb.ca