Skip to content

Contributing to the CiviCRM User Guide

The documentation on this page is a starting point for contributing to the CiviCRM user guide. There is a more advanced documentation for contributing in the CiviCRM developer guide.

Style guide

When proposing changes please follow the Documentation style guide.

Contributing single changes

  1. Sign up for an (if you don't already have one) and login at
  2. Find the page in the manual that you want to edit. For example, Menu, Dashboard and Dashlets
  3. Click the pencil icon next to the page title.
    Image of the pencil icon
  4. You will be taken to a GitLab editing screen at Make your changes, describe your changes in a descriptive commit message and commit changes.

This will create a merge request for your changes, which will be published as soon as they are reviewed by someone on our documentation team.

Contributing multiple changes

  1. Sign up for an (if you don't already have one) and login at
  2. Create a Fork with the fork button on the top right of the page.

Fork icon from

  1. In your git client clone the CiviCRM user guide repository to your computer.
  2. Locate the Markdown file (.md) in your file system that you want to edit by matching it to the file that that you want to change. For example, if you want to edit "What is CiviCRM?" you would find <your_file_system>/docs/getting-prepared/
  3. Make one or more related changes and commit them in your git client.
  4. Push your changes from your git client to your fork.
  5. In GitLab click merge request to create the new merge request.

New PR in Github Interface

  1. Click merge request.
  2. Leave a descriptive message and then click Create merge request.

Your PR will be reviewed by someone on the documentation team and published once they are approved.

Additional resources

Additional resources on how CiviCRM does documentation and Markdown can be found in the developer docs.

Versioning (which version should I edit?)

All edits based on the current version of CiviCRM should be committed against the master branch. The Developer guide has more detailed information.