# Other Output Formats

In addition to the default native HTML output, Documenter also provides a built-in LaTeX-based PDF output. Additional output formats are provided through plugin packages. Once the corresponding package is loaded, the output format can be specified using the format option in makedocs.

## PDF Output via LaTeX

makedocs can be switched over to use the PDF/LaTeX backend by passing a Documenter.LaTeX object as the format keyword:

using Documenter
makedocs(format = Documenter.LaTeX(), ...)

Documenter will then generate a PDF file of the documentation using LaTeX, which will be placed in the output (build/) directory.

The makedocs argument sitename will be used for the \title field in the tex document, and if the build is for a release tag (i.e. when the "TRAVIS_TAG" environment variable is set) the version number will be appended to the title. The makedocs argument authors should also be specified, it will be used for the \authors field in the tex document.

### Compiling using natively installed latex

The following is required to build the documentation:

• You need pdflatex and latexmk commands to be installed and available to Documenter.
• You need the minted LaTeX package and its backend source highlighter Pygments installed.
• You need the DejaVu Sans and DejaVu Sans Mono fonts installed.

### Compiling using docker image

It is also possible to use a prebuilt docker image to compile the .tex file. The image contains all of the required installs described in the section above. The only requirement for using the image is that docker is installed and available for the builder to call. You also need to tell Documenter to use the docker image, instead of natively installed tex which is the default. This is done with the LaTeX specifier:

using DocumenterLaTeX
makedocs(
format = LaTeX(platform = "docker"),
...
)

If you build the documentation on Travis you need to add

services:
- docker

to your .travis.yml file.

### Compiling to LaTeX only

There's a possibility to save only the .tex file and skip the PDF compilation. For this purpose use the platform="none" keyword:

using DocumenterLaTeX
makedocs(
format = LaTeX(platform = "none"),
...
)

## Markdown & MkDocs

Markdown output requires the DocumenterMarkdown package to be available and loaded. For Travis setups, add the package to the docs/Project.toml environment as a dependency. You also need to import the package in make.jl:

using DocumenterMarkdown

When DocumenterMarkdown is loaded, you can specify format = Markdown() in makedocs. Documenter will then output a set of Markdown files to the build directory that can then further be processed with MkDocs into HTML pages.

MkDocs, of course, is not the only option you have – any markdown to HTML converter should work fine with some amount of setting up.

Note

Markdown output used to be the default option (i.e. when leaving the format option unspecified). The default now is the HTML output.

### The MkDocs mkdocs.yml file

A MkDocs build is controlled by the mkdocs.yml configuration file. Add the file with the following content to the docs/ directory:

site_name:        PACKAGE_NAME.jl
repo_url:         https://github.com/USER_NAME/PACKAGE_NAME.jl
site_description: Description...
site_author:      USER_NAME

extra_css:
- assets/Documenter.css

extra_javascript:
- https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js?config=TeX-AMS_HTML
- assets/mathjaxhelper.js

markdown_extensions:
- extra
- tables
- fenced_code
- mdx_math

docs_dir: 'build'

pages:
- Home: index.md

If you have run Documenter and it has generated a build/ directory, you can now try running mkdocs build – this should now generate the site/ directory. You should also add the docs/site/ directory into your .gitignore file, which should now look like:

docs/build/
docs/site/

This is only a basic skeleton. Read through the MkDocs documentation if you would like to know more about the available settings.

### Deployment with MkDocs

To deploy MkDocs on Travis, you also need to provide additional keyword arguments to deploydocs. Your deploydocs call should look something like

deploydocs(
repo   = "github.com/USER_NAME/PACKAGE_NAME.jl.git",
deps   = Deps.pip("mkdocs", "pygments", "python-markdown-math"),
make   = () -> run(mkdocs build)
target = "site"
)
• deps serves to provide the required Python dependencies to build the documentation
• make specifies the function that calls mkdocs to perform the second build step
• target, which specified which files get copied to gh-pages, needs to point to the site/ directory

In the example above we include the dependencies mkdocs and python-markdown-math. The former makes sure that MkDocs is installed to deploy the documentation, and the latter provides the mdx_math markdown extension to exploit MathJax rendering of latex equations in markdown. Other dependencies should be included here.

### $\LaTeX$: MkDocs and MathJax

To get MkDocs to display $\LaTeX$ equations correctly we need to update several of this configuration files described in the Package Guide.

docs/make.jl should add the python-markdown-math dependency to allow for equations to be rendered correctly.

# ...

deploydocs(
deps = Deps.pip("pygments", "mkdocs", "python-markdown-math"),
# ...
)

This package should also be installed locally so that you can preview the generated documentation prior to pushing new commits to a repository.

\$ pip install python-markdown-math

The docs/mkdocs.yml file must add the python-markdown-math extension, called mdx_math, as well as two MathJax JavaScript files:

# ...
markdown_extensions:
- mdx_math
# ...

extra_javascript:
- https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js?config=TeX-AMS_HTML
- assets/mathjaxhelper.js
# ...

Final Remarks

Following this guide and adding the necessary changes to the configuration files should enable properly rendered mathematical equations within your documentation both locally and when built and deployed using the Travis built service.