Code Review
/
opnfvdocs.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
review
|
tree
raw
|
inline
| side by side
Update git submodules
[opnfvdocs.git]
/
docs
/
how-to-use-docs
/
documentation-guide.rst
diff --git
a/docs/how-to-use-docs/documentation-guide.rst
b/docs/how-to-use-docs/documentation-guide.rst
index
fed42a4
..
56bf273
100644
(file)
--- a/
docs/how-to-use-docs/documentation-guide.rst
+++ b/
docs/how-to-use-docs/documentation-guide.rst
@@
-62,10
+62,14
@@
Following representation shows the expected structure:
│ ├── scenarios
│ │ └── scenario.name
│ └── userguide
│ ├── scenarios
│ │ └── scenario.name
│ └── userguide
- └── testing
- ├── developer
- └── user
-
+ ├── testing
+ │ ├── developer
+ │ └── user
+ └── infrastructure
+ ├── hardware-infrastructure
+ ├── software-infrastructure
+ ├── continuous-integration
+ └── cross-community-continuous-integration
Release documentation
^^^^^^^^^^^^^^^^^^^^^
Release documentation
^^^^^^^^^^^^^^^^^^^^^
@@
-133,3
+137,8
@@
You are encouraged to establish the following basic structure for your project a
**Project overview**: :code:`<repo>/docs/development/overview`
- Folder for any project specific documentation.
**Project overview**: :code:`<repo>/docs/development/overview`
- Folder for any project specific documentation.
+
+Infrastructure Documentation
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Infrastructure documentation can be stored under :code:`<repo>/docs/` folder of
+corresponding infrastructure project.