Convert Contributing to Mautic section to RST [multiple sub-issues]

[RCheesley]

We are in the process of moving this repository to Read the Docs, and to do that we need to convert our pages from Markdown to RST. This issue is to transfer the Contribute to Mautic section: https://contribute.mautic.org/contributing-to-mautic. You can also update and improve the content on these pages if you like - do check with the relevant team leads to ensure it's up to date and relevant.

Sections to migrate

As this is a large section I recommend that we take it one section at a time. Drop a message in the comments to be assigned to a section.

• [ ] Designer
• [ ] Developer
• [ ] Marketer
• [ ] Tester
• [ ] Translator
• [ ] Writing for Mautic
• [ ] Event organiser
• [ ] Web developer
• [ ] Server administrator
• [ ] Contributing financially
• [ ] Google Summer of Code @Iqmaa

You can do this in the current repo, as we've got a folder set up, /docs, which will be used for Read The Docs.

You can build this documentation locally by cloning this repository, and following these steps: https://github.com/mautic/user-documentation/tree/5.x?tab=readme-ov-file#build-documentation-locally. Change into the /docs folder and then (assuming you have DDEV and Docker/Colima installed) type ddev config and select build/htmlas the root folder when configuring DDEV. Then when complete, type ddev start and it'll give you the link to your local testing environment.

If you need to make a link file to add an external URL, please use the command line tool 'make link'. This will generate a reference macro and a link file for you.

For internal linking check the docs on using the :ref: role for linking within the same document, and using :doc: to link across pages.

Please note: if you see folders called .revs these are old version control files from Grav. Ignore them! (they should be deleted) and instead work on the actual files.

When you've converted the file/s, they need to live within the /docs folder. We can create a structure using sub-folders to organise the sections. You also need to add the pages to the Table of Contents in the index.rst file for them to show on the menu. Docs on the ToC can be found here.

We highly recommend that you use VS Code with Vale installed. Let us know if you have any problems.

Some useful resources:

• https://sublime-and-sphinx-guide.readthedocs.io/en/latest guide to Sphinx/RST formatting
• https://sublime-and-sphinx-guide.readthedocs.io/en/latest/references.html#use-the-external-links-extension how to do external links - always check the /docs/links directory first! You can use the terminal command 'make link' to create the link file automagically.

There are many MD to RST tools out there which can help speed up the process, however you will still need to review your output to ensure it passes our Vale grammar rules. Headings must always be unique, as well.

We use the following for headings:

H1 ###
H2 ***
H3 ===
H4 ---
H5 ~~~

Please ask in #t-education on Slack if you get stuck with anything!

[Iqmaa]

Hi @RCheesley, I'd like to be assigned the 'google summer of code' section please.

[RCheesley]

Absolutely @Iqmaa please read the updated description above! Worth mentioning that we have the Assembly now on the community portal: https://community.mautic.org/assemblies/gsoc which is where we'll be taking ideas for projects, and also where our projects and updates from students are posted.