Cleanup of rst files to preserve formatting during mkdocs conversion (#…

…245) * cleanup of rst files to preserve formatting during mkdocs conversion * small updates to fix missing anchor * additional formatting fixes from mkdocs review * cleanup warnings
geonetwork · Oct 19, 2023 · dd1a7a6 · dd1a7a6
1 parent 8e91bd5
commit dd1a7a6
Show file tree

Hide file tree

Showing 84 changed files with 5,842 additions and 6,405 deletions.
diff --git a/source/administrator-guide/configuring-the-catalog/inspire-configuration.rst b/source/administrator-guide/configuring-the-catalog/inspire-configuration.rst
@@ -138,7 +138,7 @@ Array's ``value-type`` attribute must be defined as Java strings: ``<array value
 To define which test suites will be executed when using the editor dashboard's INSPIRE validation option you can modify the ``inspireEtfValidatorTestsuitesConditions`` bean. It's a map with an entry for each schema and test suite to execute. The map entry key attribute must be in the format ``SCHEMA_ID::TEST_SUITE_NAME``, where ``TEST_SUITE_NAME`` is one of the  ``inspireEtfValidatorTestsuites`` map entry key. For each entry you can define a XPath condition that the metadata must pass to be sent to the validator.
 
 .. note::
-  
+
   If a metadata schema doesn't match, the schema dependency hierarchy is checked to verify if any parent schema matches any rules.
 
 .. warning::

diff --git a/source/administrator-guide/configuring-the-catalog/portal-configuration.rst b/source/administrator-guide/configuring-the-catalog/portal-configuration.rst
@@ -11,11 +11,11 @@ Portals can be configured under the  ``sources`` section in ``admin console`` >
 
 There are 3 types of sources:
 
- - the main catalogue,
+- the main catalogue,
 
- - sub-portal, which can be a subset of the main catalogue
+- sub-portal, which can be a subset of the main catalogue
 
- - harvesters.
+- harvesters.
 
 
 .. figure:: img/portal-types.png

diff --git a/source/administrator-guide/configuring-the-catalog/system-configuration.rst b/source/administrator-guide/configuring-the-catalog/system-configuration.rst
@@ -59,13 +59,13 @@ Catalog Server
   they are used during metadata editing to create resource links and
   when returning the server's capabilities during a CSW request.
 
- - If your node is publicly accessible from the Internet, you have to use the domain name.
+  - If your node is publicly accessible from the Internet, you have to use the domain name.
 
- - If your node is hidden inside your private network and you have a firewall or web server
-   that redirects incoming requests to the node, you have to enter the public address of
-   the firewall or web server. A typical configuration is to have an Apache web server
-   on address A that is publicly accessible and redirects the requests to a Tomcat server
-   on a private address B. In this case you have to enter A in the host parameter.
+  - If your node is hidden inside your private network and you have a firewall or web server
+    that redirects incoming requests to the node, you have to enter the public address of
+    the firewall or web server. A typical configuration is to have an Apache web server
+    on address A that is publicly accessible and redirects the requests to a Tomcat server
+    on a private address B. In this case you have to enter A in the host parameter.
 
 
 - **Port** The server's port number (usually 80 or 8080). If using HTTP, set it to 80.

diff --git a/source/administrator-guide/index.rst b/source/administrator-guide/index.rst
@@ -3,7 +3,6 @@
 Administrator guide
 ###################
 
-
 .. toctree::
    :maxdepth: 2
 
@@ -17,4 +16,4 @@ Administrator guide
 
 
 All Admin functions are available from the Admin Dashboard from the main menu.
-On the Admin Dashboard you will find shortcuts to any administration option your role can access.
+On the Admin Dashboard you will find shortcuts to any administration option your role can access.
diff --git a/source/administrator-guide/managing-classification-systems/managing-thesaurus.rst b/source/administrator-guide/managing-classification-systems/managing-thesaurus.rst
@@ -245,4 +245,4 @@ Notice that a URL pointing to the source thesaurus is included in the Thesaurus
 Search criteria: keywords
 -------------------------
 
-You can search on keywords using the facet panel. All keywords are stored in the index field ```tag``` and are also available in field depending on thesaurus name eg. ```th_theme``` for INSPIRE themes. The field name is based on the thesaurus type and filename.
+You can search on keywords using the facet panel. All keywords are stored in the index field ``tag`` and are also available in field depending on thesaurus name eg. ``th_theme`` for INSPIRE themes. The field name is based on the thesaurus type and filename.
diff --git a/source/administrator-guide/managing-metadata-standards/standards.rst b/source/administrator-guide/managing-metadata-standards/standards.rst
@@ -26,28 +26,28 @@ To add a metadata schema to the catalog, a rebuild of the sources is required. I
 - Add a reference in /schemas/pom.xml to the newly added schema
 
 
-.. code-block:: xml
+  .. code-block:: xml
 
-    <module>{myschema}</module>
+      <module>{myschema}</module>
 
 - Add references to the newly added schema in /web/pom.xml
 
 
-.. code-block:: xml
+  .. code-block:: xml
 
-    <dependency>
-      <groupId>${project.groupId}</groupId>
-      <artifactId>{myschema}</artifactId>
-      <version>${project.version}</version>
-    </dependency>
+      <dependency>
+        <groupId>${project.groupId}</groupId>
+        <artifactId>{myschema}</artifactId>
+        <version>${project.version}</version>
+      </dependency>
 
 - and
 
-.. code-block:: xml
+  .. code-block:: xml
 
-    <resource>
-      <directory>${project.basedir}/../schemas/{myschema}/src/main/plugin</directory>
-      <targetPath>${basedir}/src/main/webapp/WEB-INF/data/config/schema_plugins</targetPath>
-    </resource>
+      <resource>
+        <directory>${project.basedir}/../schemas/{myschema}/src/main/plugin</directory>
+        <targetPath>${basedir}/src/main/webapp/WEB-INF/data/config/schema_plugins</targetPath>
+      </resource>
 
 Then Build and deploy your instance of GeoNetwork.