docs/how-to-use-docs/addendum.rst


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72

@media only all and (prefers-color-scheme: dark) {
.highlight .hll { background-color: #49483e }
.highlight .c { color: #75715e } /* Comment */
.highlight .err { color: #960050; background-color: #1e0010 } /* Error */
.highlight .k { ========
Addendum
========

Index File
==========

The index file must relatively refence your other rst files in that directory.

Here is an example index.rst :

.. code-block:: bash

    *******************
    Documentation Title
    *******************

    .. toctree::
       :numbered:
       :maxdepth: 2

       documentation-example

Source Files
============

Document source files have to be written in reStructuredText format (rst).
Each file would be build as an html page.

Here is an example source rst file :

.. code-block:: bash

    =============
    Chapter Title
    =============

    Section Title
    =============

    Subsection Title
    ----------------

    Hello!

Writing RST Markdown
====================

See http://sphinx-doc.org/rest.html .

**Hint:**
You can add dedicated contents by using 'only' directive with build type
('html' and 'singlehtml') for OPNFV document. But, this is not encouraged to
use since this may make different views.

.. code-block:: bash

    .. only:: html
        This line will be shown only in html version.

Verify Job
----------

The verify job name is **docs-verify-rtd-{branch}**.

When you send document changes to gerrit, jenkins will create your documents
in HTML formats (normal and single-page) to verify that new document can be
built successfully. Please check the jenkins log and artifact carefully.
You can improve your document even though if the build job succeeded.

Merge Job
----------

The merge job name is **docs-merge-rtd-{branch}**.

Once the patch is merged, jenkins will automatically trigger building of
the new documentation. This might take about 15 minutes while readthedocs
builds the documentatation. The newly built documentation shall show up
as appropriate placed in docs.opnfv.org/{branch}/path-to-file.