Skip to content

chore: create the "deployment" documentation tree #32

@lucaaamaral

Description

@lucaaamaral

chore: create the "deployment" documentation tree

Problem

As discussed in #18 , having accessible documentation, separated by purpose, shall lower the entry barrier and ease the maintenance of the documentation.

Solution

Implement the "deployment" documentation tree, comprised, but not limited, by:

  • Deployment [content: Community validated scenarios] (page)
    • Orc8r
      • Kubernetes (page)
      • Docker (page)
      • Baremetal (page)
    • AGW
      • Kubernetes (page)
      • Docker (page)
      • Baremetal (page)
    • FEG
    • CWAG

Non core components shall receive a placeholder file if no documentation is found currently in the repository.

Non-goals

Documentation contents for FEG, CWAG and other non core components.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions