author Ehsan Akhgari <>
Fri, 02 Jan 2015 21:13:39 -0500
changeset 247993 bc7e683ef708f64d1cefdc4a01762ea79ec48534
parent 176100 0eec37596a6d1c0a0ff1077d518cd1df3e0e0c26
permissions -rw-r--r--
Bug 1117264 - Mark virtual overridden functions as MOZ_OVERRIDE in dom/base code; r=baku

Mozilla Source Tree Documentation

.. toctree::
   :maxdepth: 1


Python Packages

.. toctree::
   :maxdepth: 2


Managing Documentation

This documentation is generated via the
`Sphinx <>`_ tool from sources in the tree.

To build the documentation, run ``mach build-docs``. Run
``mach help build-docs`` to see configurable options.

Adding Documentation

To add new documentation, define the ``SPHINX_TREES`` and
``SPHINX_PYTHON_PACKAGE_DIRS`` variables in ```` files in
the tree and documentation will automatically get picked up.

Say you have a directory ``featureX`` you would like to write some
documentation for. Here are the steps to create Sphinx documentation
for it:

1. Create a directory for the docs. This is typically ``docs``. e.g.
2. Create an ``index.rst`` file in this directory. The ``index.rst`` file
   is the root documentation for that section. See ``build/docs/index.rst``
   for an example file.
3. In a ```` file (typically the one in the parent directory of
   the ``docs`` directory), define ``SPHINX_TREES`` to hook up the plumbing.
   e.g. ``SPHINX_TREES['featureX'] = 'docs'``. This says *the ``docs``
   directory under the current directory should be installed into the
   Sphinx documentation tree under ``/featureX``*.
4. If you have Python packages you would like to generate Python API
   documentation for, you can use ``SPHINX_PYTHON_PACKAGE_DIRS`` to
   declare directories containing Python packages. e.g.
   ``SPHINX_PYTHON_PACKAGE_DIRS += ['mozpackage']``.

Indices and tables

* :ref:`genindex`
* :ref:`modindex`
* :ref:`search`