I was thinking about doing a complete book and then publish it under one directory, but then that's going to take forever, so I guess I should split it into multiple directories.
www.mozill.org/docs/end-user/ is too long;
I'm sorry you don't like it - but it's where all the end-user documentation is now, and there's no immediate plan to move it :-)
Another issue is what happens when Mozilla is finally splitted into standalone clients? Putting Mozilla Firebird info in project/firebird/ is currently acceptable because Firebird is not ready for primetime. But when it is, we'd need a more friendly place for browser user info. We shouldn't reuse end-user/ directory because it would become crowded with files with prefix (or suffix) everywhere.
If it's all one book, then docs/end-user/getting-started/ is fine. If you are splitting it up by app, then docs/end-user/browser/ and docs/end-user/mail.
I do not want to document the standalone clients, and I imagine most d11n contributors to have preferences on what to document, the application suite or the standalone clients.
The application suite only has a future as the 1.4 stable branch, as far as I am aware. There does not seem to be sufficient interest in continuing application suite development as we move to standalone apps.
Gerv
