WIP DOC: Server structure.

src/doc/development/devel.rst

+Developing CaosDB
+=================
+
+.. toctree::
+   :glob:
+   :maxdepth: 2
+
+   Structure of the Java code <structure>
+   Benchmarking CaosDB <benchmarking>
+
+CaosDB is an Open-Source project, so anyone may modify the source as they like. These pages aim to
+provide some help for all CaosDB developers.
+
+More generally, these are the most common ways to contribute to CaosDB:
+
+- You found a bug, have a question, or want to request a feature? Please `create an issue
+  <https://gitlab.com/caosdb/caosdb-server/-/issues>`_.
+- You want to contribute code? Please fork the repository and create a merge request in GitLab and
+  choose this repository as target. Make sure to select "Allow commits from members who can merge
+  the target branch" under Contribution when creating the merge request. This allows our team to
+  work with you on your request.
+- If you have a suggestion for this `documentation <https://docs.indiscale.com/caosdb-server/>`_,
+  the preferred way is also a merge request as describe above (the documentation resides in
+  ``src/doc``).  However, you can also create an issue for it.
+- You can also contact the developers at *info (AT) caosdb.de*.

src/doc/development/structure.rst

+CaosDB's internal structure
+===========================
+
+

src/doc/index.rst

@@ -12,7 +12,7 @@ Welcome to caosdb-server's documentation!
    Concepts <concepts>
    Query Language <CaosDB-Query-Language>
    administration
-   development/*
+   Development <development/devel>
    specification/index.rst
    Glossary
    API documentation<_apidoc/packages>

src/doc/specification/Fileserver.md

@@ -35,7 +35,8 @@ where
 ### HTTP upload stream
 #### Files
 
-There is an example on file upload using cURL described in detail in [the curl section of this wiki](manuals/curl/curl-access).
+There is an example on file upload using cURL described in detail in [the curl section of this
+documentation](../administration/curl-access.md).
 
 File upload via HTTP is implemented in a [rfc1867](http://www.ietf.org/rfc/rfc1867.txt) consistent way. This is a de-facto standard that defines a file upload as a part of an HTML form submission. This concept shall not be amplified here. But it has to be noticed that this protocol is not designed for uploads of complete structured folders. Therefore the HeartDB file components have to impose that structure on the upload protocol. 
 

src/doc/specification/index.rst

@@ -8,15 +8,13 @@ Specification
    :hidden:                                                                     
                                                                                 
    AbstractProperty                                                                  
-   C-Client  
    Fileserver  
    Record      
-   Server-side-scripting       
    Specification of the Entity API <Specification-of-the-Entity-API>
    Authentication    
    Datatype  
    Paging      
    RecordType  
-   Server side scripting <Server-side-scripting-v0.1>
+   Server side scripting <Server-side-scripting>
    Specification of the Message API <Specification-of-the-Message-API>