Deltares · savente93 · Sep 21, 2023 · Jul 17, 2023 · Jul 18, 2023 · Jul 18, 2023
diff --git a/docs/_static/model_building_process.png b/docs/_static/model_building_process.png
diff --git a/docs/_static/plugin_structure.png b/docs/_static/plugin_structure.png
diff --git a/docs/api.rst b/docs/api.rst
@@ -167,9 +167,9 @@ Model attributes
 
    Model.crs
    Model.region
+   Model.root
    Model.api
 
-
 Model components and attributes
 -------------------------------
 
@@ -374,6 +374,7 @@ Setup methods
    MeshModel.setup_maps_from_rasterdataset
    MeshModel.setup_maps_from_raster_reclass
 
+.. _workflows_api:
 
 =========
 Workflows
@@ -495,6 +496,7 @@ Raster writing methods
    DataArray.raster.to_raster
    Dataset.raster.to_mapstack
 
+.. _raster_api:
 
 ==============
 Raster methods
@@ -640,6 +642,8 @@ Low level methods
    gis_utils.axes_attrs
    gis_utils.meridian_offset
 
+.. _geodataset_api:
+
 ==================
 GeoDataset methods
 ==================

diff --git a/docs/changelog.rst b/docs/changelog.rst
@@ -25,6 +25,7 @@ Added
 - Allow the root of a data catalog to point to an archive, this will be extracted to the ~/.hydromt_data folder. (PR #512)
 - Support for reading overviews from (Cloud Optimized) GeoTIFFs using the zoom_level argument of ``DataCatalog.get_rasterdataset``. (PR #514)
 - Support for writing overviews to (Cloud Optimized) GeoTIFFs in the ``raster.to_raster`` method. (PR #514)
+- Added documentation for how to start your own plugin (#446)
 
 Changed
 -------

diff --git a/docs/dev/intro.rst b/docs/dev/intro.rst
@@ -13,3 +13,4 @@ Furthermore it informs you on recent and planned developments.
    contributing.rst
    dev_install.rst
    team.rst
+   plugin-quickstart.rst
diff --git a/docs/dev/plugin-quickstart.rst b/docs/dev/plugin-quickstart.rst
diff --git a/docs/getting_started/examples_index.rst b/docs/getting_started/examples_index.rst
@@ -32,3 +32,8 @@ GIS operations:
 
 * `Working with raster data <../_examples/working_with_raster.ipynb>`_
 * `Working with flow direction data <../_examples/working_with_flow_directions.ipynb>`_
+
+Statistical Analysis:
+***********************
+
+* `Extreme Value Analysis <../_examples/doing_extreme_value_analysis.ipynb>`_
diff --git a/docs/plugins.rst b/docs/plugins.rst
@@ -66,3 +66,12 @@ About the model software
 .. _SFINCS: https://sfincs.readthedocs.io/en/latest/
 .. _Delwaq: https://www.deltares.nl/en/software/module/d-water-quality/
 .. _Delft-FIAT: https://publicwiki.deltares.nl/display/DFIAT/Delft-FIAT+Home
+
+Starting your own plugin
+------------------------
+
+If you would like to start your own HydroMT plugin for another model or software, we have some
+tips or a quick start page for you: :ref:`plugin_quickstart`.
+
+If you would like your plugin to appear on this page, please contact us via the issue board of
+HydroMT!
diff --git a/docs/user_guide/intro.rst b/docs/user_guide/intro.rst
@@ -17,7 +17,23 @@ or analyze model results. Furthermore, a Python interface is available that expo
 all functionality for experienced users. A schematic overview of the package architecture is provided
 in the figure below and each HydroMT component is discussed below.
 
-HydroMT is organized in the following way:
+In short, there are three important concepts in HydroMT core that are important to cover:
+
+- ``DataAdapters`` and ``DataCatalog``: These are what basically hold all information about how to approach and read data as well as some of the metadata
+  about it. While a lot of the work in HydroMT happens here, plugins or users shouldn't really need to know about these beyond using
+  the proper ``data_type`` in their configuration. ``DataCatalog`` are basically just a thin wrapper around the ``DataAdapters`` that does some book keeping.
+- ``Workflows``: These are functions that transform input data and can call a set of methods to for example, resample, fill nodata, reproject, derive
+  other variables etc. The core has some of these workflows but you may need new ones for your plugin.
+- ``Model``: This is where the magic happens (as far as the plugin is concerned). We have provided some generic models that you can
+  override to get basic/generic functionality, but using the model functionality is where it will be at for you. The scheme below lists the current
+  relationship between the HydroMT ``Model`` and generic sub-Model classes and the know plugins.
+
+
+.. figure:: ../_static/plugin_structure.png
+
+  Schematic of Model and plugin structure of HydroMT
+
+More concretely HydroMT is organized in the following way:
 
 - **Input Data**
 
@@ -159,3 +175,4 @@ Region                          Argument of the *build* and *clip* CLI methods t
    ../_examples/working_with_raster.ipynb
    ../_examples/working_with_geodatasets.ipynb
    ../_examples/working_with_flow_directions.ipynb
+   ../_examples/doing_extreme_value_analysis.ipynb