Contributing to docs - starting on documentation

.github/styles/config/vocabularies/Mautic/accept.txt

@@ -65,6 +65,7 @@ Jitsi
 Jono
 Joomla
 Joomla!
+Knowledgebase
 Kubuntu
 Libre
 Licensor
@@ -125,6 +126,7 @@ Unpublish
 URL
 URLs
 UTM
+VSCode
 Vtiger
 Webmecanik
 www

docs/conf.py

@@ -66,4 +66,6 @@
 # Please add links here that do not pass the "make checklinks" check.
 # A little context on the reason for ignoring is greatly appreciated!
 
-linkcheck_ignore = []
+linkcheck_ignore = [
+    # Anchors are picked up as broken
+    r"https://github.com/abiosoft/colima?tab=readme-ov-file#installation",]

docs/contributing/contributing_docs_rst.rst

@@ -0,0 +1,198 @@
+Contributing to Mautic's documentation
+######################################
+
+So you're interested in contributing to Mautic's documentation? That's fantastic. Mautic is always looking for help to improve the documentation and make it as useful as possible for the Mautic community. There are three main repositories on GitHub open to contributions. These are:
+
+1. The :xref:`User Documentation` - :xref:`User Docs GitHub` 
+2. The :xref:`Developer Docs` - :xref:`Developer Docs GitHub`
+3. The :xref:`Community Handbook` - :xref:`Community Handbook GitHub`
+
+Getting started
+***************
+
+You can work with the documentation locally, using DDEV and an editor like VSCode. This allows you to make changes and see them in real-time on a locally hosted version of the documentation. It's recommended as you can benefit from having syntax highlighting, and also generate the docs to verify the layout of your work as you go.
+
+You can also use the web-based tool :xref:`Gitpod`, which allows you to spin up a temporary cloud-hosted instance of the documentation, make changes, and submit a pull request to have your changes merged back into the main repository. You can also test PRs with Gitpod, too.
+
+Working locally
+===============
+
+To get started with one of the documentation repositories locally, it's advised to install:
+
+- Git - :xref:`install Git`
+- Docker Desktop - All operating systems, :xref:`install Docker Desktop` - or Colima - Mac and Linux, :xref:`install Colima`
+- DDEV - :xref:`install DDEV`
+- VSCode - :xref:`install VSCode`
+- GitHub CLI - :xref:`install GitHub CLI`
+- Vale linter - :xref:`install Vale`
+- Python 3 - :xref:`install Python`
+- Sphinx - ``pip3 install sphinx``
+- Sphinx Read the Docs theme - ``pip3 install sphinx-rtd-theme``
+- MyST Parser - ``pip3 install myst_parser``
+
+Once you have these installed, you can clone the repository you want to work on.
+
+To do this follow these steps:
+
+1. Open the GitHub repository that you want to work on
+2. Click the "Fork" button in the top right corner of the repository
+3. Create a directory on your local computer which you can use for working on this project. For example, ``~/Documents/Sites/local.user-documentation``
+4. Clone your fork of the repository to your local machine by running the following command in your terminal - this assumes you have GitHub CLI installed:
+
+.. code-block:: bash
+
+    gh repo clone <your-username>/<repository-name>
+
+4. Change into the docs subdirectory of the repository you just cloned using the ``cd`` command - for example ``cd ~/Documents/Sites/local.user-documentation/docs`` - this is the working directory where all the files are located.
+5. Type ``ddev config`` and press enter. This creates a ``.ddev`` directory in your project with the necessary configuration files. Accept all the settings as they're - you don't need to make any changes unless you know what you're doing.
+6. Type ``ddev start`` and press enter. This starts the Docker containers and create a local development environment for you to work in. Open the URL that it creates in the browser - ``ctrl`` + ``click`` on the URL in the terminal to open it.
+7. Type ``make html`` to build the HTML for the documentation. This creates a ``_build`` directory in your project with the compiled HTML files which you can now access at the URL that DDEV informed you of in step 6.
+8. Refresh the web browser, and verify that the documentation is showing as expected.
+
+Hurrah, now you're ready to get started with contributing to the documentation. 🥳
+
+Making your first pull request
+==============================
+
+When you want to make a change in the documentation, you need to submit a Pull Request - PR - to the relevant repository. This is a request to the maintainers of the repository to merge your changes into the main branch of the repository. While it sounds a bit confusing, once you've done it a few times it becomes second nature.
+
+Here's how to get started:
+
+1. Set up your local environment as described in :ref:`Working locally`
+
+2. By default you start on the default branch for the repository, but be sure to verify this is the case. In VSCode it'll show this in the bottom left hand toolbar. If you're not on the default branch, you can switch to it by running the following command in your terminal: ``git checkout 5.x`` - replace ``5.x`` with the name of the default branch if it's different. At the command line, use the command ``git status`` to see which branch you're on and ``git checkout 5.x`` to change to the default branch - replacing ``5.x`` with the name of the default branch if it's different.
+
+.. image:: images/change_branch.png
+    :alt: VSCode screenshot showing how to change branches
+    :width: 600px
+    :align: center
+
+3. Create a branch in your local repository to work on your changes by running the following command in your terminal: ``git checkout -b <branch-name>`` - for example, ``git checkout -b fix-typo-in-introduction``. In VSCode you can also create a new branch by clicking on the branch name in the bottom left corner of the window and selecting 'Create new branch' and providing a relevant name. Keep branch names relevant to what you're working on, as this helps you to keep track of what you're doing and clean up old branches once they aren't needed any more.
+
+4. Make your changes in the documentation. You can do this in your editor of choice, and see the changes in real-time in your browser by typing ``make html`` in the terminal and refreshing the browser.
+
+5. Fix any issues that the Vale linter flags up while you are working - you'll see these as red, yellow or blue squiggly lines in your editor with the color denoting them being an error, warning or notice respectively.
+
+.. image:: images/vale_syntax_highlighter.png
+    :alt: VSCode screenshot showing Vale linter errors
+    :width: 600px
+    :align: center
+
+6. Be sure to regularly build the HTML files by typing ``make html`` in the terminal, and refresh the browser to verify that your changes are showing as expected. When you build the files, it highlights any syntax errors such as incorrect heading nesting or broken links for you to fix.
+
+.. image:: images/rst_heading_too_short.png
+    :alt: VSCode screenshot showing an error with an underline being too short
+    :width: 600px
+    :align: center
+
+7. Commit your changes to your local repository by running the following command in your terminal: ``git add <filename>`` to stage specific files, and then ``git commit -m "A brief description of the changes you made"`` - for example, ``git commit -m "Fix typo in introduction"``. You can also do this in the VSCode editor by clicking on the source control icon in the left-hand toolbar, staging the files you want to commit by clicking the plus icon which appears on hover, and then adding a commit message in the box above.
+
+.. image:: images/staging_changes.png
+    :alt: VSCode screenshot showing how to stage and commit changes
+    :width: 600px
+    :align: center
+
+8. Push your changes to your fork of the repository by running the following command in your terminal: ``git push origin <branch-name>`` - for example, ``git push origin fix-typo-in-introduction``. This sends your changes to your fork on GitHub. To do this in the VSCode editor, first publish the branch by clicking on the blue button in the version control panel, and then push the changes by clicking on the three dots next to the branch name and selecting 'Push' or clicking the blue button marked 'synchronize changes'.  Continue to make and stage changes and synchronize in this way until you've completed your work.
+
+9. Go back to the original repository - not your fork, but the upstream version - and create a new pull request by clicking on the green button which shows at the top of the page. This takes you to a page where you can review the changes you've made, and add a description of what you've done. Once you're happy with the changes, click the 'Create pull request' button to submit your changes for review.
+
+10. Don't forget to add a clear description of what you've done in the pull request, and if you're fixing an issue, be sure to reference it in the description. This helps the maintainers to understand what you're doing and why.
+
+11. Wait for the maintainers to review your PR and when they do, be sure to respond to any comments they make. This might involve making further changes to your PR, or answering questions they have about your work. Once they're happy with your changes, they'll merge them into the main branch of the repository and your work is automatically deployed on the documentation site. Great job, you're now the latest contributor to Mautic. 🥳
+
+
+Important considerations
+************************
+
+When contributing to the documentation, there are a few things to keep in mind:
+
+Nesting headings
+================
+
+Mautic uses the following syntax for headings:
+
+.. code-block:: rst
+
+    H1
+    ###
+
+    H2
+    ***
+
+    H3
+    ===
+
+    H4
+    ---
+
+    H5
+    ~~~
+
+    H6
+    ^^^
+
+When you're writing documentation, be sure to nest your headings correctly. This means that you should only use one H1 heading per page, and then nest your headings in the order shown. This helps to keep the documentation consistent and easy to read.
+
+Also be sure to extend the underline to fit the length of the heading text. This is a requirement of RST syntax and helps to keep the documentation looking neat and tidy.
+
+Linking to other pages
+======================
+
+When you're linking to other pages in the documentation, be sure to use the correct syntax. This means that you should use the following syntax:
+
+Linking within the current page
+-------------------------------
+
+.. code-block:: rst
+
+    :ref:`A heading`
+    :ref:`Target to paragraph <my heading>`
+    :ref:`Target inside a paragraph <my heading>`
+
+In this example the target could be a heading on the page called 'A heading'. The first example uses the name of the heading and outputs it exactly as it's on the page where it's used.
+
+The second and third options use a title to override what's already used on the heading. The content within the ``<`` and ``>`` is the heading from the page that you want to link to - it must be an exact match for a heading used elsewhere on the page - and the text displayed before or after is what you want the words to display in the link.
+
+An example from this page, linking to the earlier section on linking to other pages would look like this:
+
+.. code-block:: rst
+
+    :ref:`My link title <Linking to other pages>`
+
+This renders as:
+
+:ref:`My link title <Linking to other pages>`
+
+
+Read more in the :xref:`ref role documentation`.
+
+Linking to another page in the same documentation repository
+------------------------------------------------------------
+
+.. code-block:: rst
+
+    :doc:`documentation-page`
+    :doc:`/guides/documentation-page`
+    :doc:`Custom title </guides/documentation-page>`
+
+In this example the target could be a page called 'documentation-page'. The first example uses the name of the page as if it was in the same directory as the current file. The second option uses the full path to the file if it were in a different folder, and the third option uses a title to override what's already used on the page heading.
+
+.. note::
+
+        When linking to another page in the same documentation repository, you don't need to include the file extension. This is automatically added by Sphinx when building the documentation. Using paths relative to the documentation root is preferable, to avoid changing the target name when restructuring content.
+
+
+Read more in the :xref:`doc role documentation`.
+
+External links
+--------------
+
+Mautic makes use of link files, located in /links, which means that there's a single place to update links if they change. This is especially useful for links to external sites, such as the Mautic GitHub repository. It also allows us to check that the links are still valid with each new contribution.
+
+There's a quick way to create those link files using the ``make link`` command. This creates a new file in the /links directory with the name of the link, and the URL as the content. This is then used in the documentation like this:
+
+.. code-block:: rst
+
+    :xref:`Mautic GitHub`
+
+Use the command ``make link`` in the terminal to create a link file then copy the resulting ``xref`` macro. Read more in the :xref:`xref role documentation`.

docs/index.rst

@@ -29,13 +29,15 @@ The vision is that it grows over time as the teams and governance structure evol
    :hidden:
 
    teams/legal_and_finance_team
-
+   teams/education_team/education_team
+
 .. toctree::
    :maxdepth: 2
    :caption: Contributing
    :hidden:
 
    contributing/google_summer_of_code
+   contributing/contributing_docs_rst
 
 .. toctree::
    :maxdepth: 2

docs/links/colima_install.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "install Colima" 
+link_text = "install Colima" 
+link_url = "https://github.com/abiosoft/colima?tab=readme-ov-file#installation" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/community_handbook.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Community Handbook" 
+link_text = "Community Handbook" 
+link_url = "https://contribute.mautic.org" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/community_handbook_gh.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Community Handbook GitHub" 
+link_text = "Community Handbook on GitHub" 
+link_url = "https://github.com/mautic/mautic-community-handbook" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/ddev_install.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "install DDEV" 
+link_text = "install DDEV" 
+link_url = "https://ddev.readthedocs.io/en/stable/users/install/ddev-installation/" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/dev_docs_GH.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Developer Docs GitHub" 
+link_text = "Developer Docs on GitHub" 
+link_url = "https://github.com/mautic/developer-documentation-new" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/developer_documentation.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Developer Docs" 
+link_text = "Developer Documentation" 
+link_url = "https://devdocs.mautic.org" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/docker_desktop_install.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "install Docker Desktop" 
+link_text = "install Docker Desktop" 
+link_url = "https://www.docker.com/products/docker-desktop/" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/education_team_slack.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Education Team on Slack" 
+link_text = "#t-education" 
+link_url = "https://mautic.slack.com/archives/CQGQ0D4KU" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/end_user_docs.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "User Documentation" 
+link_text = "End-User Documentation" 
+link_url = "https://docs.mautic.org" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/git_download.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "install Git" 
+link_text = "install Git" 
+link_url = "https://git-scm.com/downloads" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/github_cli_install.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "install GitHub CLI" 
+link_text = "install GitHub CLI" 
+link_url = "https://cli.github.com/" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/gitpod.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "Gitpod" 
+link_text = "Gitpod" 
+link_url = "https://gitpod.io/" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/python_install.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "install Python" 
+link_text = "install Python 3" 
+link_url = "https://www.python.org/downloads/" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/sphinx_doc_role.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "doc role documentation" 
+link_text = ":doc: role documentation" 
+link_url = "https://docs.readthedocs.io/en/stable/guides/cross-referencing-with-sphinx.html#the-doc-role" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/sphinx_ref_role.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "ref role documentation" 
+link_text = ":ref: role documentation" 
+link_url = "https://docs.readthedocs.io/en/stable/guides/cross-referencing-with-sphinx.html#the-ref-role" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/sphinx_xref_role.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "xref role documentation" 
+link_text = ":xref: role documentation" 
+link_url = "https://sublime-and-sphinx-guide.readthedocs.io/en/latest/references.html#add-link-make-command" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/user_docs_GH.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "User Docs GitHub" 
+link_text = "User Docs on GitHub" 
+link_url = "https://github.com/mautic/user-documentation" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/vale_install.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "install Vale" 
+link_text = "install Vale" 
+link_url = "https://vale.sh/docs/vale-cli/installation/" 
+
+link.xref_links.update({link_name: (link_text, link_url)})

docs/links/vscode_install.py

@@ -0,0 +1,7 @@
+from . import link
+
+link_name = "install VSCode" 
+link_text = "install VSCode" 
+link_url = "https://code.visualstudio.com/download" 
+
+link.xref_links.update({link_name: (link_text, link_url)})