> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superoffice.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Contribute to SuperOffice Docs

> An overview of why and how SuperOffice Docs is community-generated, and the two main ways to contribute - editing directly in GitHub's browser editor, or working locally.

Thanks for being awesome & contributing to SuperOffice Docs! Our community is better because of your contributions... let's get started.

## SuperOfficeDocs on GitHub

GitHub is a web-based hosting service for version control using Git. If you're not familiar with Git and/or GitHub, no worries! Having our documentation center on GitHub brings many benefits to our community as we can now build SuperOffice documentation in the open, together, as a community. If you see areas for improvement or gaps in the documentation, you can easily update and/or fill those gaps. SuperOffice Docs will be a living and breathing, community-generated, collection of awesome learning materials moving forward.

SuperOffice Docs are located on GitHub at [https://github.com/SuperOfficeDocs][1].

## How SuperOfficeDocs are generated

The SuperOffice Docs system uses [Mintlify][2], [Markdown][3], and GitHub to ultimately output a statically generated site, which is currently located at [docs.superoffice.com][4]. You don't have to understand the components that are used to generate the docs to contribute.

## Authoring and editing content in SuperOfficeDocs

There are 2 primary ways to contribute to the documentation on this website. SuperOffice Docs can be updated in the browser in GitHub and also locally on one's machine. The latter is only necessary if you're making complex edits and maybe are more technical.

### Editing in GitHub

If you are just updating text, typos, or adding a few sentences it may be easiest to edit the content directly from GitHub's browser.

<Note>
  If you are working on an existing issue, self-assign. Otherwise, first, please create a new issue. Reference the issue ID in both the branch name, commit messages, and pull request.
</Note>

1. Find the file you want to edit in the docs repo.

2. Click the **Edit** button.

   ![Edit article in browser][img1]

3. Edit the markdown as needed, opt to "Create a New Branch".

   ![Edit Markdown in browser][img2]

4. Propose the changes.

   ![Edit Markdown in browser][img3]

5. Update the title to include the issue #ID and submit the pull request.

   ![Edit Markdown in browser][img4]

Be sure to also check out the [Markdown guide][6] to ensure you're formatting the code correctly, and know that we're using MDX, which adds JSX component support on top of standard Markdown.

### Editing locally

If you are making more complex edits you may want to [get SuperOfficeDocs running on your local machine][8]. In this case, after getting SuperOfficeDocs running locally, you'll follow the [edit SuperOfficeDocs locally][9] guide.

## Helpful links

* [How to edit an article][9]
* [Markdown guide][6]

[1]: https://github.com/SuperOfficeDocs

[2]: https://mintlify.com/docs

[3]: https://en.wikipedia.org/wiki/Markdown

[4]: https://docs.superoffice.com

[6]: ./markdown-guide/index

[8]: ./getting-started

[9]: ./how-to-edit-an-article

[img1]: /media/loc/en/contribute/edit-article-on-github.png

[img2]: /media/loc/en/contribute/edit-markdown-on-github.png

[img3]: /media/loc/en/contribute/propose-changes-on-github.png

[img4]: /media/loc/en/contribute/create-pull-request-on-github.png