-
Notifications
You must be signed in to change notification settings - Fork 126
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.
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
docs: set up get-started directory tree #1303
Conversation
Signed-off-by: Meg McRoberts <[email protected]>
✅ Deploy Preview for keptn-lifecycle-toolkit ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@@ -0,0 +1,6 @@ | |||
--- | |||
title: Getting started with the Lifecycle Toolkit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has the same title as the previous section. Maybe we can call this Deployment Orchestration
. This can be done in a follow up :)
@StackScribe
#1299
This sets up the get-started tree for the "Getting Started" guides, specifically those for use cases.
It also moves the "integrating.md" page (about annotations and labels) from install to implementing, which is where it belongs.
This structure is required so I can begin writing the actual guides. The only content here are temporary stubs for new files and the virtually unmodified text of the original "Getting Started" guide. The actual text is not important for this PR -- we will review that later when we have more content.