summaryrefslogtreecommitdiffstats
path: root/docs/how-to-use-docs/documentation-guide.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/how-to-use-docs/documentation-guide.rst')
-rw-r--r--docs/how-to-use-docs/documentation-guide.rst5
1 files changed, 0 insertions, 5 deletions
diff --git a/docs/how-to-use-docs/documentation-guide.rst b/docs/how-to-use-docs/documentation-guide.rst
index aeabdcc0d..3c8446893 100644
--- a/docs/how-to-use-docs/documentation-guide.rst
+++ b/docs/how-to-use-docs/documentation-guide.rst
@@ -15,11 +15,6 @@ OPNFV documentation is automated and integrated into our git & gerrit toolchains
We use RST document templates in our repositories and automatically render to HTML and PDF versions of the documents in our artifact store, our WiKi is also able to integrate these rendered documents directly allowing projects to use the revision controlled documentation process for project information, content and deliverables.
Read :ref:`this page <include-documentation>` which elaborates on how documentation is to be included within opnfvdocs.
-Enabling the documentation toolchain in your project
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-There are some basic steps you will need to perform in order to get the toolchain working in your repository, this include setting up Jenkins jobs and establishing your project documentation structure. See the document toolchain instructions for more details on getting started in your project.
-The linked page above is written completely in generated artifacts, check the source to see how to do it yourself!
-
Licencing your documentation
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
All contributions to the OPNFV project are done in accordance with the OPNFV licensing requirements. Documentation in OPNFV is contributed in accordance with the `Creative Commons 4.0 <https://creativecommons.org/licenses/by/4.0/>`_ licence.