1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
9 The index file must relatively reference your other rst files in that directory.
11 Here is an example index.rst :
28 Document source files have to be written in reStructuredText format (rst).
29 Each file would be build as an html page.
31 Here is an example source rst file :
50 See http://sphinx-doc.org/rest.html .
53 You can add html content that only appears in html output by using the
54 'only' directive with build type
55 ('html' and 'singlehtml') for an ONAP document. But, this is not encouraged.
60 This line will be shown only in html version.
62 .. index:: single: indices
67 Building an index for your Sphinx project is relatively simple. First, tell Sphinx that
68 you want it to build an index by adding something like this after your TOC tree:
79 Note that search was included here. It works out of the box with any Sphinx project, so you
80 don't need to do anything except include a reference to it in your :code:`index.rst` file.
82 Now, to generate a index entry in your RST, do one of the following:
86 Some content that requires an :index:`index`.
95 Some header containing myterm
96 =============================
98 In the second case, Sphinx will create a link in the index to the paragraph that follows
99 the index entry declaration.
101 When your project is built, Sphinx will generate an index page populated with the entries
102 you created in the source RST.
104 These are simple cases with simple options. For more information about indexing with Sphinx,
105 please see the `official Sphinx documentation <http://www.sphinx-doc.org/en/stable/markup/misc.html#directive-index>`_.
113 The verify job name is **doc-{stream}-verify-rtd**
115 Proposed changes in doc or any other repository that has been added as a
116 git submodule will be verified by this job prior to a gerrit code review.
117 Please check the Jenkins log carefully for warnings.
118 You can improve your document even if the verify job succeeded.
123 The merge job name is **doc-{stream}-merge-rtd**.
125 When a committer merges a patch, Jenkins will automatically trigger building of
126 the new documentation. This might take about 15 minutes while readthedocs
127 builds the documentation. The newly built documentation shall show up
128 as appropriate placed in docs.onap.org/{branch}/path-to-file.