[BUGFIX] Fix diverse rendering warnings

Add documents that were referenced but not included

Author: linawolf

docs/architecture.rst

@@ -3,14 +3,15 @@ Architecture
 ============
 
 The project is built around the core library that is called ``guides``. This library
-contains all core components of the project. Like the different layers :doc:`parser`,
-:doc:`compiler` and :doc:`render` and includes the basic Nodes and templates to create
+contains all core components of the project. Like the different layers :ref:`parser-component`,
+:ref:`compiler-component` and :ref:`renderer-component` and includes the basic Nodes and templates to create
 output.
 
-Installation of the core library can be done using ``composer``::
+Installation of the core library can be done using ``composer``:
 
-.. code:: bash
-        composer require phpdocumentor/guides
+..  code-block:: bash
+
+    composer require phpdocumentor/guides
 
 The other components are using the core library and extend it with additional
 functionality. For example the ``guides-markdown`` component adds support for
@@ -30,18 +31,21 @@ Application flow
 
 Processing documents is done in a few steps.
 
-#. :php:class:`Parsing <\phpDocumentor\Guides\Parser>` The first step is to parse the document. This is done by the :doc:`parser` component. The
-   parser component will parse the document and create a tree of nodes. Each node
-   represents a part of the document. For example a paragraph, a list or a table.
-#. :php:class:`Compiling <\phpDocumentor\Guides\Compiler\Compiler>` The second step is to compile the tree of nodes. This is done by the :doc:`compiler`
-   component. During the compilation, modifications can be made to the tree of nodes. For
-   example the compiler can add a table of contents to the tree of nodes.
-
-#. :php:class:`Rendering <\phpDocumentor\Guides\Renderer\BaseTypeRenderer>` The third step is to render the tree of nodes. This is done by the :doc:`render`
-   component. The render component will render the tree of nodes to a specific output
-   format. By default twig templates are used to render nodes to HTML. But you can
-   create your own templates to render nodes to other formats. Or implement your own
-   renderer to use a different template engine.
-
-.. uml:: _uml/application-flow.puml
+#.  :php:class:`Parsing <\phpDocumentor\Guides\Parser>` The first step is to parse the document.
+    This is done by the :ref:`parser-component` component. The
+    parser component will parse the document and create a tree of nodes. Each node
+    represents a part of the document. For example a paragraph, a list or a table.
+#. :php:class:`Compiling <\phpDocumentor\Guides\Compiler\Compiler>` The second step is to compile the tree of nodes.
+    This is done by the :ref:`compiler-component`
+    component. During the compilation, modifications can be made to the tree of nodes. For
+    example the compiler can add a table of contents to the tree of nodes.
+
+#.  :php:class:`Rendering <\phpDocumentor\Guides\Renderer\BaseTypeRenderer>` The third step is to render
+    the tree of nodes. This is done by the :ref:`renderer-component`
+    component. The render component will render the tree of nodes to a specific output
+    format. By default twig templates are used to render nodes to HTML. But you can
+    create your own templates to render nodes to other formats. Or implement your own
+    renderer to use a different template engine.
+
+..  uml:: _uml/application-flow.puml
     :caption: Application flow

docs/components/parser.rst

@@ -6,4 +6,5 @@
 Parser
 ======
 
-..  warning:: This needs to be documented
+..  warning::
+    This needs to be documented

docs/components/renderer.rst

@@ -6,4 +6,5 @@
 Renderer
 ========
 
-..  warning:: This needs to be documented
+..  warning::
+    This needs to be documented

docs/developers/extensions/text-roles.rst

@@ -1,5 +1,7 @@
 ..  include:: /include.rst.txt
 
+..  _custom_text_roles:
+
 ==========
 Text Roles
 ==========

docs/reference/restructuredtext/text-roles.rst

@@ -6,7 +6,7 @@ Text Roles
 
 Text roles can be used to style content inline. Some text roles have advanced processing such as reference resolving.
 
-You can also :doc:`add your own custom text roles </extension/text-roles>`.
+You can also :ref:`add your own custom text roles <custom_text_roles>`.
 
 Currently the following text roles are implemented: