We're starting a new documentation effort for the streams repository. Pretty much the entire suite of documentation we inherited from the Hubzilla project years ago has been tossed - because hardly any of it still applies. It's better to have no documentation than it is to have wrong documentation. The format has also changed back to the old ways. We're not trying to provide one or two files containing all the documentation of every feature in the codebase. Instead the intent is to break it up into bite-sized chunks that can each be read in a couple of minutes and focuses on one feature or software attribute.
All documentation must be in Multicode (.mc) files. It is preferred that documentation be in a very simple Markdown format, using bbcode or html only if it is absolutely necessary. This is so it can be exported easily with pandoc and used anywhere, like in the repository pages. "User documentation" should also include screenshots or any relevant media which helps to quickly describe where to find a particular setting and/or show it in action. a picture is worth a thousand words. A brief video is worth a thousand times that.
If you wish to see some topic get special documentation coverage, please reply to this post with the topic description so that these can be prioritised. At the top of the list at the moment are Registration and Channels, making and managing connections, using the editor, managing files, working with permissions, and backing-up or cloning your channel.
Basically, end-user documentation should go in doc/en (or a suitable language folder for your needs), and developer documentation in doc/develop/en . Once the number of available topics reaches critical mass I'll open an issue to improve and categorise the top level help index. For now, don't worry about it.
Anybody is welcome to submit documentation pull requests. The more, the merrier. Going forward, code (feature) submissions will be rejected unless they contain relevant documentation and either a test plan or automated tests (which should have been executed prior to submitting the pull request).