Integration section in developers guide

docs/source/developer/index.rst

@@ -29,7 +29,7 @@ To start using the MapStore geOrchestra project as a developer you need the foll
 .. toctree::
    :maxdepth: 4
 
-   ./security/index
+   ./integration/index
 
 
 Configuring the backend

docs/source/developer/security/index.rst → docs/source/developer/integration/index.rst

@@ -1,5 +1,24 @@
+Integration
+===========
+
+MapStore integration inside geOrchestra is realized mainly:
+
+1. **Including it in the build and in the general workflow of geOrchestra**:
+
+Here the list of files involved:
+
+ * `Header <https://github.com/georchestra/georchestra/blob/master/header/src/main/webapp/WEB-INF/jsp/index.jsp>`_ (and `header localization <https://github.com/georchestra/georchestra/tree/master/header/src/main/resources/_header/i18n>`_)
+ * `Database Creation scripts <https://github.com/georchestra/georchestra/blob/master/postgresql/110-mapstore.sql>`_
+ * `Docker <https://github.com/georchestra/docker/blob/master/docker-compose.yml#L153>`_
+ * `Data Dir <https://github.com/georchestra/datadir/tree/master/mapstore>`_
+ * `Github Workflows <https://github.com/georchestra/mapstore2-georchestra/blob/master/.github/workflows/mapstore.yml>`_
+
+2. **Realizing a custom build that integrates with datadir, security ... and can be integrated in the docker build.**
+
+Here below a detailed explanation of how security integration is realized:
+
 Security Integration
-====================
+^^^^^^^^^^^^^^^^^^^^
 MapStore is integrated with the geOrchestra security infrastructure. This happens thanks to:
  * an authentication filter using the geOrchestra security proxy headers to authenticate the user and assign proper MapStore groups and roles
  * LDAP enabled DAOs to get available roles from the geOrchestra LDAP repository
@@ -102,3 +121,4 @@ Here a diagram of how the various pieces work together:
 Here some of the most important MapStore workflows and their relation to the security infrastructure:
 
 .. image:: security_flows.svg
+