About MongoDB Documentation¶
On this page
The MongoDB Manual contains comprehensive documentation on MongoDB. This page describes the manual’s licensing, editions, and versions, and describes how to make a change request and how to contribute to the manual.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States License
© MongoDB, Inc. 2008-2016
In addition to the MongoDB Manual, you can also access this content in the following editions:
Version and Revisions¶
This version of the manual reflects version 3.2 of MongoDB.
See the MongoDB Documentation Project Page for an overview of all editions and output formats of the MongoDB Manual. You can see the full revision history and track ongoing improvements and additions for all versions of the manual from its GitHub repository.
This edition reflects “v3.2” branch of the documentation as of the “a67257eec4d8fcf0fc4970e05759fb4f3d1b757f” revision. This branch is explicitly accessible via “https://docs.mongodb.com/v3.2” and you can always reference the commit of the current manual in the release.txt file.
The most up-to-date, current, and stable version of the manual is always available at “http://docs.mongodb.org/manual/”.
Report an Issue or Make a Change Request¶
To report an issue with this manual or to make a change request, file a ticket at the MongoDB DOCS Project on Jira.
Contribute to the Documentation¶
In order for the documentation team to accept your change, you must complete the MongoDB Contributor Agreement.
You can clone the repository by issuing the following command at your system shell:
git clone git://github.com/mongodb/docs.git
About the Documentation Process¶
The MongoDB Manual uses Sphinx, a sophisticated documentation engine built upon Python Docutils. The original reStructured Text files, as well as all necessary Sphinx extensions and build tools, are available in the same repository as the documentation.
For more information on the MongoDB documentation process, see:
If you have any questions, please feel free to open a Jira Case.