Setup and Configuration Clone the repository: 

git clone git://github.com/mongodb/docs.git 

## Building the Documentation 

The MongoDB documentation build system is entirely accessible via make targets. For example, to build an HTML version of the documentation issue the following command: 

make html 

You can find the build output in build/<branch>/html , where <branch> is the name of the current branch. 

In addition to the html target, the build system provides the following targets: 

publish Builds and integrates all output for the production build. Build output is in build/public/<branch>/ . When you run publish in the master , the build will generate some output in build/public/ . 

push ; stage Uploads the production build to the production or staging web servers. Depends on publish . Re- quires access production or staging environment. 

push-all ; stage-all Uploads the entire content of build/public/ to the web servers. Depends on publish . Not used in common practice. 

push-with-delete ; stage-with-delete Modifies the action of push and stage to remove remote file that don’t exist in the local build. Use with caution. 

html ; latex ; dirhtml ; epub ; texinfo ; man ; json These are standard targets derived from the default Sphinx Makefile, with adjusted dependencies. Additionally, for all of these targets you can append -nitpick to increase Sphinx’s verbosity, or -clean to remove all Sphinx build artifacts. 

latex performs several additional post-processing steps on .tex output generated by Sphinx. This target will also compile PDFs using pdflatex . 

html and man also generates a .tar.gz file of the build outputs for inclusion in the final releases. 

If you have any questions, please feel free to open a Jira Case$^{51}$. 

