Reorganize docs into flat folder layout

docs/source/Contributing-Docs.md

@@ -14,9 +14,40 @@ Markdown files are simple text files that can be edited with a normal text edito
 contain raw HTML directives (but that is very rarely needed). They primarly use
 the [Markdown][commonmark] syntax. See [the syntax section below](#Editing-syntax) for more help.
 
-> Note: Don't edit the files in `evennia/docs/source/api/`. These are auto-generated and your
-changes
-> will be lost.
+## Source file structure 
+
+The sources are organized into several rough categories, with only a few administrative documents
+at the root of `evennia/docs/source/`. The folders are named in singular form since they will 
+primarily be accessed as link refs (e.g. `Component/Account`)
+
+- `source/Components/` are docs describing separate Evennia building blocks, that is, things
+  that you can import and use. This extends and elaborates on what can be found out by reading
+  the api docs themselves. Example are documentation for `Accounts`, `Objects` and `Commands`.
+- `source/Concepts/` describes how larger-scale features of Evennia hang together - things that 
+  can't easily be broken down into one isolated component. This can be general descriptions of 
+  how Models and Typeclasses interact to the path a message takes from the client to the server 
+  and back.
+- `source/Setup/` holds detailed docs on installing, running and maintaining the Evennia server and 
+  the infrastructure around it. 
+- `source/Coding/` has help on how to interact with, use and navigate the Evennia codebase itself. 
+  This also has non-Evennia-specific help on general development concepts and how to set up a sane
+  development environment.
+- `source/Contribs/` holds documentation specifically for packages in the `evennia/contribs/` folder.
+  Any contrib-specific tutorials will be found here instead of in `Howtos`
+- `source/Howtos/` holds docs that describe how to achieve a specific goal, effect or 
+  result in Evennia. This is often on a tutorial or FAQ form and will refer to the rest of the 
+  documentation for further reading.
+  - `source/Howtos/StartingTutorial/` holds all documents part of the initial tutorial sequence.
+  
+  
+ Other files and folders:
+  - `source/api/` contains the auto-generated API documentation as `.rst` files. Don't edit these
+    files manually, your changes will be lost. 
+  - `source/_templates` and `source/_static` should not be modified unless adding a new doc-page 
+    feature or changing the look of the HTML documentation.
+  - `conf.py` holds the Sphinx configuration. It should usually not be modified except to update
+    the Evennia version on a new branch.
+    
 
 ## Building the docs locally