Skip to content

Documentation contributing guide {How to edit the docs)

Interested in updating existing pages or writing your own page? Here you'll learn the basics on contributing to RoR's documentation. This guide assumes you're running Windows, but most steps should be valid on Linux as well.


Forking the repository

To begin, head over to the GitHub repository and click the github-fork button at the top right. This will create a copy of the repository on your GitHub account where your changes will be made.

Using GitHub Desktop

After installing GitHub Desktop, launch the app and sign into your GitHub account. After signing in, it'll ask you to clone a repository. Select the repository you forked earlier along with where you want the repository to be stored locally:


When the cloning process is finished, it will ask how you plan on using this repository. I recommend selecting "For my own purposes" as this will prevent confusion between your fork and the main repository.

In the toolbar, click Repository -> Open in Command Prompt This is where you'll run the commands in the following steps.

Installing MkDocs

The documentation is powered by MkDocs. it will need to be installed if you wish to be able to preview your changes in real time. Go to the official MkDocs installation page and follow the steps listed there, come back here once you've reached the "Installing MkDocs" section.

After you've successfully installed Python and pip, run the following commands one by one in the command prompt window you opened earlier:

pip install mkdocs
pip install mkdocs-material
pip install mkdocs-minify-plugin
pip install mkdocs-git-revision-date-localized-plugin

These packages can also be found in the requirements.txt file in the root of the repository.

Once everything is installed, you should now be able to view a local version of the docs by running mkdocs serve. Your command prompt window should now look like this: powershell-mkdocs

The documentation should now be viewable in your browser at

The page will automatically reload when changes are made.

Making changes

In GitHub Desktop, it is highly recommended that you create a new branch by selecting Branch -> New branch... in the toolbar. This will ensure you don't make changes you didn't want to the main branch, as undoing them can be a pain without creating unnecessary commits.

Pages are written in Markdown, the same formatting syntax used on GitHub. See this page to learn the basic Markdown syntax.

Adding images

To add a new image to a page, add the image to the source\images folder: explorer-images-folder

Give the image a name that describes what the image is of (example for the above image: explorer-images-folder.png) Then reference the image in the page using this syntax:


Note: It seems in recent versions of MkDocs, the mkdocs serve command can crash after adding an image to the folder. Just run it again if this happens to you.

Creating new pages

To create a new page, simply create a new file with the .md file extension in the appropriate category folder.

Make sure you also add the page to the sidebar by editing mkdocs.yml, otherwise mkdocs serve will show a warning!

Linking other docs pages

To link to other pages on the docs, use the following syntax:

[Beginner's Guide](/gameplay/beginners-guide/)
[Beginner's Guide](

Making a pull request

Once you're finished editing, your GitHub Desktop app will probably look similar to this: github-desktop-docs

Write a title and description for your changes, then click "Commit to branch" to add your changes to the branch. When ready, select Branch -> Create pull request to create a pull request on the main repository, and if everything goes well, it'll be merged!

Syncing your fork

After new commits are pushed to the main repository, you'll want to make sure your fork is up to date. Unfortunately GitHub Desktop doesn't appear to have an easy way to do this without creating a merge commit. Open a command prompt (Repository -> Open in Command Prompt in GitHub Desktop) and run the following:

git remote remove upstream
git remote add upstream
git fetch upstream
git merge upstream/master

To update your fork in the future, run only the last two commands.

In GitHub Desktop, click "Push to origin" after running the above commands.


I hope this helps anyone who becomes interested in helping contribute to the docs.