zephyr/doc
Allan Stephens fa2e040198 doc: Enhance usability of top-level documentation page
Regroups documents into 3 sets::

1) Documents needed when first encountering Zephyr. (Basically what
   you need to decide if you're interested in Zephyr, what it can do
   for you, and how to get the code so you can experiment with it.)

2) Documents used when developing new Zephyr software.

3) Reference documents for Zephyr. (Having these on the main page
   instead of a sub-page make sense, since the API guide and
   configuration option guide will be consulted frequently by users.)

Change-Id: Ifee7ac83f041c24e1efbe3ba7379c21a2ba8b9bc
Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
2016-02-05 20:15:21 -05:00
..
application Doc: Creates the Application Dev. Primer with the existing content. 2016-02-05 20:15:19 -05:00
collaboration doc: Adds step by step procedure to develop microkernel apps. 2016-02-05 20:14:37 -05:00
development Doc: Create the Reference Guides part. 2016-02-05 20:15:20 -05:00
documentation doc: remove references to BSP 2016-02-05 20:15:21 -05:00
doxygen Rename nano_node_tick_get_32 in documentation 2016-02-05 20:15:20 -05:00
kernel doc: Add information about atomic APIs 2016-02-05 20:15:21 -05:00
platform Doc: Add the Platform Development Primer to the structure. 2016-02-05 20:15:19 -05:00
quick_start doc: quick start: installing: New Zephyr SDK 2016-02-05 20:15:21 -05:00
reference doc: Enhance usability of top-level documentation page 2016-02-05 20:15:21 -05:00
themes/zephyr doc: add custom zephyr theme 2016-02-05 20:14:28 -05:00
about_zephyr.rst doc: Add "About Zephyr" section 2016-02-05 20:15:21 -05:00
conf.py doc: add custom zephyr theme 2016-02-05 20:14:28 -05:00
disclaimers.rst Fix the index page and headers 2016-02-05 20:14:21 -05:00
documentation_license.rst Fix the index page and headers 2016-02-05 20:14:21 -05:00
doxygen.config Doc: Changes doxygen.config for index & auto-generated files. 2016-02-05 20:14:45 -05:00
index.rst doc: Enhance usability of top-level documentation page 2016-02-05 20:15:21 -05:00
Makefile doc: fix docs target 2016-02-05 20:14:45 -05:00
README.rst Adapt installation guide with current requirements 2016-02-05 20:14:16 -05:00
substitutions.rst Rename Zephyr OS into Zephyr Kernel 2016-02-05 20:14:26 -05:00
zephyr_project.rst DOC: Restructures the documentation in two parts. 2016-02-05 20:14:39 -05:00

.. include:: substitutions.rst

Welcome to |codename|
#####################

.. This document is in Restructured Text Format.

   More information at `<http://sphinx-doc.org/rest.html>`_.
   This is a comment that won't show up in formatted output

Welcome to the |project|.

Thank you for your interest in the |project|. These instructions are
designed to walk you through generating the |project|'s documentation.


Documentation Notes
*******************

The project's documentation currently comprises the following items:

* An Installation Guide for Linux host systems

* A set of Collaboration Guidelines for the project.

* Raw Doxygen output from the code base.

Installing the documentation processors
***************************************

Install the current version of :program:`Sphinx`, type:

.. code-block:: bash

   $ git clone https://github.com/sphinx-doc/sphinx.git sphinx

   $ cd sphinx

   $ sudo -E python setup.py install

   $ cd ..

   $ git clone https://github.com/michaeljones/breathe.git breathe

   $ cd breathe

   $ sudo -E python setup.py install

.. note::

   Make sure that :program:`Doxygen` is installed in your system.
   The installation of Doxygen is beyond the scope of this document.

Running the documentation generators
************************************

Assuming that the |project| tree with the doc directory is in
:file:`DIRECTORY`, type:

.. code-block:: bash

   $ cd DIRECTORY/doc

   $ make doxy html

Find the output in :file:`DIRECTORY/doc/_build/html/index.html`

Review the available formats with:

.. code-block:: bash

   $ make -C DIRECTORY/doc doxy html

If you want the LaTeX PDF output, you need to install all the Latex
packages first. That installation is beyond the scope of this document.