summaryrefslogtreecommitdiffstats
path: root/docs/guides/onap-developer/how-to-use-docs/templates/sections/architecture.rst
diff options
context:
space:
mode:
authorEric Debeau <eric.debeau@orange.com>2020-11-30 15:32:31 +0100
committerSofia Wallin <sofia.wallin@est.tech>2020-12-02 09:55:30 +0000
commit0ba07f5c9a94fcd460f1f1914d9b6ffa8f46dd7e (patch)
treecbc4dc114be6b5f4a543bcc698e4236202f9a28b /docs/guides/onap-developer/how-to-use-docs/templates/sections/architecture.rst
parentc67eda8a8efd73a8b7388930e2fef30b9f0511bb (diff)
Remove all warnings during Documentation buildings
Remove files with not links: - guides/onap-developer/architecture/blueprint-enr.rst old file based on Beijing - smsummary.rst: no more relevant as no more submodules used - templates/sections/vnf-reference.rst : not referenced - guides/onap-user/onapportal.rst: redundant - guides/onap-developer/tutorials/index.rst: no tutorial Add new files to inlude templates Move templates directory under how-to-use-docs Modify global release not label with onap_release_notes to avoid confusion Issue-ID: DOC-692 Signed-off-by: Eric Debeau <eric.debeau@orange.com> Change-Id: I709765beb02403c4ad058863c2b5136f42968cff (cherry picked from commit ab0c78bb275b345eb5e995a40a90e633980d7bca)
Diffstat (limited to 'docs/guides/onap-developer/how-to-use-docs/templates/sections/architecture.rst')
-rw-r--r--docs/guides/onap-developer/how-to-use-docs/templates/sections/architecture.rst27
1 files changed, 27 insertions, 0 deletions
diff --git a/docs/guides/onap-developer/how-to-use-docs/templates/sections/architecture.rst b/docs/guides/onap-developer/how-to-use-docs/templates/sections/architecture.rst
new file mode 100644
index 000000000..8daa0d3bc
--- /dev/null
+++ b/docs/guides/onap-developer/how-to-use-docs/templates/sections/architecture.rst
@@ -0,0 +1,27 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+Architecture
+============
+
+.. note::
+ * This section is used to describe a software component from a high level
+ view of capability, common usage scenarios, and interactions with other
+ components required in the usage scenarios.
+
+ * The architecture section is typically: provided in a platform-component
+ and sdk collections; and referenced from developer and user guides.
+
+ * This note must be removed after content has been added.
+
+
+Capabilities
+------------
+
+
+Usage Scenarios
+---------------
+
+
+Interactions
+------------