Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Documentation Engineering: Landscape Deployment Documentation #53

Closed
g-pavlov opened this issue Nov 10, 2020 · 1 comment
Closed

Documentation Engineering: Landscape Deployment Documentation #53

g-pavlov opened this issue Nov 10, 2020 · 1 comment
Labels
effort/6m Effort for issue is around 6 months kind/epic Large multi-story topic

Comments

@g-pavlov
Copy link
Contributor

g-pavlov commented Nov 10, 2020 •
edited
Loading

Documentation Engineering

Milestone stage in #51

Landscape Deployment Documentation

Each Gardener landscape consists of component in a certain version that collectively constitute a BoM for that landscape. Operators and users need to be able to access the documentation for the exact version of the components in the landscape, preferably efficiently, without searching for it among other components and versions not relevant for that landscape.

The documentation bundle for a landscape should be built automatically e.g. using the static Gardener component model.

The documentation should be published on a dedicated website and accessible via the landscape Dashboard UI.

This epic can be considered a special case and a subset of #52 .
@g-pavlov g-pavlov added kind/epic Large multi-story topic size/xl Size of pull request is huge (see gardener-robot robot/bots/size.py) roadmap/cloud-sap labels Nov 10, 2020
@g-pavlov g-pavlov added this to the 2021-Q1 milestone Nov 10, 2020
@g-pavlov g-pavlov pinned this issue Nov 10, 2020
@gardener-robot gardener-robot added effort/6m Effort for issue is around 6 months and removed size/xl Size of pull request is huge (see gardener-robot robot/bots/size.py) labels Mar 8, 2021
@vlerenc vlerenc removed this from the 2021-Q1 milestone Jun 15, 2021
@Kristian-ZH
Copy link

not anymore in the backlog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/6m Effort for issue is around 6 months kind/epic Large multi-story topic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@vlerenc @g-pavlov @Kristian-ZH @gardener-robot