docs: rename publishing section (#2128)

* docs: rename publishing section

* fix ref

Author: tomkralidis

docs/source/conf.py

@@ -93,7 +93,7 @@ def __getattr__(cls, name):
 # You can specify multiple suffix as a list of string:
 #
 # source_suffix = ['.rst', '.md']
-source_suffix = '.rst'
+source_suffix = {'.rst': 'restructuredtext'}
 
 # The master toctree document.
 master_doc = 'index'

docs/source/data-publishing/index.rst

@@ -37,7 +37,7 @@ reference documentation on all aspects of the project.
    running-with-docker
    tour
    openapi
-   data-publishing/index
+   publishing/index
    transactions
    admin-api
    security

docs/source/index.rst

@@ -0,0 +1,56 @@
+.. _publishing:
+
+Publishing
+==========
+
+Let's start working on integrating your data, metadata, and processes.  pygeoapi provides the capability to
+publish vector/coverage data, catalogues, processes and exposing filesystems of geospatial data.
+
+A key component of publishing is the pygeoapi plugin framework (data/metadata providers, processes).  Default/core
+plugins are described below.
+
+.. seealso::
+   :ref:`plugins` for writing custom plugins.
+
+Data publishing
+---------------
+
+Data providers allow for configuring data files, databases, search indexes, other APIs, cloud storage,
+to be able to return back data to the pygeoapi API framework in a plug and play fashion.
+
+.. toctree::
+   :maxdepth: 2
+
+   ogcapi-features
+   ogcapi-coverages
+   ogcapi-maps
+   ogcapi-tiles
+   ogcapi-edr
+
+.. seealso::
+   :ref:`configuration` for more information on publishing hidden data.
+
+Metadata publishing
+-------------------
+
+Metadata providers work in the same manner as data providers, with a focus on geospatial metadata (data about data).
+
+.. toctree::
+   :maxdepth: 2
+
+   ogcapi-records
+   stac
+
+.. seealso::
+   :ref:`configuration` for more information on publishing hidden metadata.
+
+Process publishing
+------------------
+
+In addition to data publishing, pygeoapi also provides the capability to publish
+processes that can be executed via the OGC API - Processes standard.
+
+.. toctree::
+   :maxdepth: 3
+
+   ogcapi-processes

docs/source/publishing/index.rst

@@ -79,11 +79,10 @@ The below configuration is an example of a process defined as part of a custom P
     my-process:
         type: process
         processor:
-            name: HelloWorld
-               # refer to a process in the standard PYTHONPATH
-               # e.g. my_package/my_module/my_file.py (class MyProcess)
-               # the MyProcess class must subclass from pygeoapi.process.base.BaseProcessor
-               name: my_package.my_module.my_file.MyProcess
+            # refer to a process in the standard PYTHONPATH
+            # e.g. my_package/my_module/my_file.py (class MyProcess)
+            # the MyProcess class must subclass from pygeoapi.process.base.BaseProcessor
+            name: my_package.my_module.my_file.MyProcess
 
 
 See :ref:`example-custom-pygeoapi-processing-plugin` for full processing plugin examples.