Mautic End User Documentation
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
bin fix permissions Dec 6, 2016
en Merge pull request #289 from kuzmany/twillio-alphanumeric-sender-id Oct 11, 2018
fr remove the mention of the button on the contact list and only use of … Dec 26, 2017
jp Merge pull request #278 from katzueno/katz/jp-contact-improvement-201804 Apr 30, 2018
node_modules/gitbook-plugin-customheader So CSS :not does not apply to children elements. Must be more specific Mar 12, 2018
.gitignore missed .gitignore update Apr 25, 2016
.travis.yml Add more node.js versions to travis-ci Oct 5, 2015 add fr flag Nov 29, 2016
LICENSE Updated summary Jun 22, 2017

Mautic Documentation


This repository contains the primary Mautic documentation, the open source marketing automation system. Just as the code is open source and available for everyone, so is the documentation. Everyone is welcome to help make this information better and improve as needed.

Download documentation as a PDF

Download the official Mautic documentation as a PDF in:

Contributing to the Mautic documentation

This repository serves as the source code for the Mautic documentation Gitbook published at The source code is shared here on GitHub so anyone can contribute to the documentation in the same way the programmers do with the actual Mautic code.

Steps to contribute

  1. Fork this repository
  2. Select a file to edit on your fork
  3. Make your commits
  4. Open a pull request to base fork: mautic/documentation with base: master
  5. Include and reference any Issues your Pull Request addresses

Why is git used for the documentation

  • versions. Anyone can go back and look at what the text looked like.
  • authorship. Not only every file, but every line has its author.
  • community contributions. No need to worry about deleting someone else's work while working on the same document.

Although some git knowledge is required to clone, modify, commit and push changes, there is a way to avoid that and edit the files directly in the GitHub web interface. If you know git, use the workflow you like. If not, the following guide will show you how to contribute easily.

Editing documentation using the command line

  1. Fork this repository
  2. In the command line cd to where you want the documentation repository located
  3. Run $ git clone<your-username>/documentation.git to clone your fork
  4. Once cloning has completed, open the project in your editor of choice
  5. $ git checkout -b branch/your-branch-name to create a new branch for your edits. Please name your branch something descriptive like {yourusername}-revision-readme-file
  6. Commit your changes and submit your pull request to base fork: mautic/documentation and base: master

Editing documents in the GitHub browser interface

If you're unfamiliar with the command line but still want to contribute to the Mautic documentation

Using as an example:

  1. Fork this repository under your account so you'll have permission to edit.
  2. Select the file (refer to the file structure section below if needed)
  3. With the content of visible, click on the pencil icon to begin editing the file
  4. The .md extension means this file was written in Markdown, a simple but flexible text formatting language. Mautic documentation is written with Markdown markup specifically.
  5. After you've made a change, scroll down to the Commit changes form. Saving your change requires describing what was changed and why.
  6. Before submitting your commit, select the box for Creates a new branch to start a new branch for your change. Name your branch something like {yourusername}-revision-readme-file
  7. Select Propose file change
  8. In the next dialogue box, describe what you've changed and why then select Create pull request to open a pull request proposing we add your changes to our official repository.

The File Structure

The file is serves as the introduction and description of this repository. This file does not contain any documentation.

The file defines the menu of the documentation. If you add a new page to the documentation, you'll have to also add a new line there defining the title and the link to the file (formatted like the existing menu items).

The folders in this repository are grouped together by topic. For example, within the asset folder, you'll see it has its own file which contains the primary description of the Asset menu; the file is a subitem; the media subfolder contains all the images used in the .md files.


Often you'll want to make a link to another place in the documentation. In Markdown, the link looks like this:

[link title](

This will create an external link with absolute URL. If you want to create an internal link, use a relative URL like this:

[these steps](./../plugins/integration_test.html)

This will link to plugins/integration_test.html on the documentation website created from the .md source file.


Images can be placed in the media subfolders in the different sections of this repository. For images that cannot be uploaded via the GitHub web interface, upload them to any public URL service and use the generated link.

![alternative text here]( "Tooltip text here")

Or, if you want to display an image already uploaded to the documentation repository, you can use a relative path:

![alternative text here](/assets/media/assets-newcategory.png "Tooltip text here")


The Mautic official end user documentation is licensed under the Apache 2.0, a permissive license whose main conditions require preservation of copyright and license notices. Read more.