-
Notifications
You must be signed in to change notification settings - Fork 79
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
Storyboarded documentation files #355
Conversation
docs/3_NEW_STACK.md
Outdated
@@ -0,0 +1,13 @@ | |||
# 3. Creating a New Stack |
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.
@iphilpot @erikschlegel If this PR is merged, we'll be introducing "Stack" as the official term for Cobalt Templates into the code base. I propose the following alternative: Kobalt Infrastructure Templates (KIT)
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.
Updated to use "template" nomenclature for now, as per today's discussion
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.
@KeithJRome @erikschlegel @TechnicallyWilliams How about we go with Cobalt Infrastructure Template (CIT) pronounced kit?
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.
+1 on CIT
docs/1_USING_COBALT.md
Outdated
@@ -0,0 +1,13 @@ | |||
# 1. Using and Customizing Cobalt | |||
|
|||
[Documentation WIP] A series of hands-on labs that helps a user of Cobalt understand how to effectively create, test, and operationalize an infrastructure template ("stack"). |
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.
IMO, the concept of the "lab" should be expressed in our documentation but explicitly using the term "lab" feels academic, like a readme for a class room assignment. Would "manuals/tutorials" work better here?
@iphilpot @erikschlegel
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.
let's leave out lab/manual etc... KISS (Keep it Simple)
Co-Authored-By: Dexter Williams <dexterwilliams04@gmail.com>
All Submissions:
What is the current behavior?
To support users with adequate and current documentation of this project, a set of walkthroughs are being provided. These documents need a place to live.
Issue Number: #347
What is the new behavior?
This PR introduces a set of starter docs to contain the various walkthrough steps, along with an index doc.
Does this introduce a breaking change?
Any relevant logs, error output, etc?
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Other information