Update documentation format for new builder

Author: navarr

configuration.md

@@ -1,4 +1,4 @@
-## Configuration
+# Configuration
 
 ```{toctree}
 ---

environments.md

@@ -1,4 +1,4 @@
-## Environments
+# Environments
 
 ```{toctree}
 ---

environments/magento2.md

@@ -2,7 +2,7 @@
 
 The below example demonstrates the from-scratch setup of the Magento 2 application for local development. A similar process can easily be used to configure an environment of any other type. This assumes that Warden has been previously started via `warden svc up` as part of the installation procedure.
 
-```note::
+```{note}
     In addition to the below manual process, there is a `Github Template available for Magento 2 <https://github.com/wardenenv/warden-env-magento2>`_ allowing for quick setup of new Magento projects. To use this, click the green "Use this template" button to create your own repository based on the template repository, run the init script and update the README with any project specific information.
 ```
 
@@ -64,7 +64,7 @@ The below example demonstrates the from-scratch setup of the Magento 2 applicati
 
         warden env up
 
-    ```warning::
+    ```{warning}
         If you encounter an error about ``Mounts denied``, follow the instructions in the error message and run ``warden env up`` again.
     ```
 
@@ -76,7 +76,7 @@ The below example demonstrates the from-scratch setup of the Magento 2 applicati
 
     	composer global config http-basic.repo.magento.com <username> <password>
 
-    ```note::
+    ```{note}
         To locate your authentication keys for Magento 2 repository, `reference DevDocs <https://devdocs.magento.com/guides/v2.3/install-gde/prereq/connect-auth.html>`_.
 
         If you have previously configured global credentials, you may skip this step, as ``~/.composer/`` is mounted into the container from the host machine in order to share composer cache between projects, and also shares the global ``auth.json`` from the host machine.
@@ -154,7 +154,7 @@ The below example demonstrates the from-scratch setup of the Magento 2 applicati
         bin/magento indexer:reindex
         bin/magento cache:flush
 
-    ```note::
+    ```{note}
         Prior to Magento ``2.4.x`` it was not required to enter search-engine and elasticsearch configuration during installation and these params to ``setup:install`` are not supported by Magento ``2.3.x``. These should be omitted on older versions where not supported and Elasticsearch configured via ``config:set`` instead:
 
         .. code::
@@ -197,7 +197,7 @@ The below example demonstrates the from-scratch setup of the Magento 2 applicati
         segno "${OTPAUTH_URL}" -s 4 -o "pub/media/${ADMIN_USER}-totp-qr.png"
         printf "%s\n\n" "https://${TRAEFIK_SUBDOMAIN}.${TRAEFIK_DOMAIN}/media/${ADMIN_USER}-totp-qr.png?t=$(date +%s)"
 
-    ```note::
+    ```{note}
         Use of 2FA is mandatory on Magento ``2.4.x`` and setup of 2FA should be skipped when installing ``2.3.x`` or earlier. Where 2FA is setup manually via UI upon login rather than using the CLI commands above, the 2FA configuration email may be retrieved from `the Mailhog service <https://mailhog.warden.test/>`_.
     ```
 
@@ -208,6 +208,6 @@ The below example demonstrates the from-scratch setup of the Magento 2 applicati
     - [https://rabbitmq.exampleproject.test/](https://rabbitmq.exampleproject.test/)
     - [https://elasticsearch.exampleproject.test/](https://elasticsearch.exampleproject.test/)
 
-```note::
+```{note}
     To completely destroy the ``exampleproject`` environment we just created, run ``warden env down -v`` to tear down the project's Docker containers, volumes, etc.
 ```

environments/shopware.md

@@ -51,7 +51,7 @@ The below example demonstrates the from-scratch setup of the Shopware 6 applicat
 
         warden env up
 
-    ```warning::
+    ```{warning}
         If you encounter an error about ``Mounts denied``, follow the instructions in the error message and run ``warden env up`` again.
     ```
 
@@ -72,10 +72,10 @@ The below example demonstrates the from-scratch setup of the Shopware 6 applicat
     - [https://app.exampleproject.test/](https://app.exampleproject.test/)
     - [https://app.exampleproject.test/admin/](https://app.exampleproject.test/admin/)
 
-```note::
+```{note}
     The default username for Shopware 6 is ``admin`` with password ``shopware``.
 ```
 
-```note::
+```{note}
     To completely destroy the ``exampleproject`` environment we just created, run ``warden env down -v`` to tear down the project's Docker containers, volumes, etc.
 ```

images.md

@@ -1,3 +1,3 @@
-## Docker Images
+# Docker Images
 
 Each of the docker images used by Warden environments are published on Docker Hub: [https://hub.docker.com/u/wardenenv](https://hub.docker.com/u/wardenenv). Source files used to build these images may be found in the `images` directory of the main project repository. Github Actions are used to automatically build and push new images to Docker Hub when image sources are modified. Please refer to the repositories on Docker Hub for a list of available image versions and tags.