Skip to content

Contributing to MatrixOne Documentation

Contributions to the MatrixOne documentation are welcome from everyone. The MatrixOne community strives to make the contribution process simple and straightforward. To do that, we create this page to walk you through the whole process step by step.

Before you start

Before you contribute, please take a minute to familiarize yourself with basic Markdown syntax and look at our Code of Conduct and the Google Developer Documentation Style Guide for some guidance on writing accessible, consistent, and inclusive documentation.

How is MatrixOne documentation project organized?

The MatrixOne documentation is managed in 3 repositories:

The images are referred to as web image links from artwork repo. The and have implemented a CI&CD project, which will be triggered by a new code merge and manual launch. This CI&CD workflow publishes the documentation to

The documentation project is based on the mkdocs-material. You can find the corresponding syntax and commands with this project.

MatrixOne Documentation Structure

The MatrixOne documentation content is planned with 6 main modules.

  • Overview: MatrixOne's introduction, features and architecture.

  • Getting Started: How to quickly deploy and run a standalone MatrixOne.

  • Developing Guide: How to develop some applications based on MatrixOne using different programming languages.

  • Deploying: How to quickly deploy and run MatrixOne cluster.

  • Tutorials: Examples of developing application demos.

  • Maintenance: How to maintain MatrixOne, including backing up and restoring data.

  • Migrating: How to migrate data from other databases to MatrixOne.

  • Testing: How to perform a self-test or MatrixOne performance test using the test tool.

  • Performance Tuning: How to tune the MatrixOne performance in a stand-alone or distributed environment.

  • Privilege: Multi-account management, account lifecycle management, and authorization in MatrixOne clusters.

  • Reference: SQL reference, Configuration parameters.

  • Troubleshooting: Introduce common errors and debugging tools.

  • FAQs: Product, Technical Design, SQL, Deployment FAQs.

  • Release Notes: Release notes of all versions.

  • Contribution Guide: How to contribute to MatrixOne project.

  • Glossary: Table of noun definitions.

Lift a finger

If you are correcting a typo or grammatical error, feel free to go ahead and create a pull request for English docs or create a pull request for Chinese docs.

Contribute Workflow

When you need to change the specific content of the document but do not involve the adjustment of the chapter order and structure organization, you need to modify or to operate.

If you need to adjust the chapter order and structure organization, you must modify the or

The following process shows the case of modifying both, and the actual situation can be simplified according to your needs.

1. File an English doc issue or File an Chinese doc issue and assign it to yourself by commenting /assign.

2. Fork and repos. 3. Clone the and repos.

git clone
git clone

4. Add and repos as the remote repository in your local folder with:

  • Add repo as a remote repository in your local folder with:
git remote add upstream
  • Add repo as a remote repository in your local folder with:
git remote add upstream

5. As the local repo has the full documentation project code, you can run mkdocs serve under or folder, and check http://localhost:8000 to check if this project runs well.

mkdocs serve

6. Make your modification. If the modification concerns the project settings, update the sitemap with new pages, or update the CI&CD workflow code. You can always check http://localhost:8000 to see if your modification is effective.

7. Push your git commits to your remote Github and matrixone repos. We recommend you push to a new branch using the following commands:

git push origin main:NEW_BRANCH

8. Go back to GitHub, and submit a pull request in NEW_BRANCH so that we can review your changes.

9. Once your code for both repositories is merged, you'll wait for a CI&CD workflow to restart running until the documentation website being updated.


So once your pull requests are merged, the update to the website is not immediate. We'll need to run a manual launch to update it.

10. At last, you should update your local and remote repo to help keep committing history clean. Override your local committing repo with:

git pull --force upstream main:main

Update the main branch of your remote repo in Github:

git push --force origin main:main


Most processes should be implemented in both and

Contribute a blog article

If you would like to write an article for our blog, please file an issue or send it to Feel free to submit either a completed draft or any article ideas. All submissions will be reviewed as quickly as possible. If your article or idea seems like a good fit for the blog, we will reach out to you directly.