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.

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

Merged
merged 3 commits into from
Oct 4, 2019
Merged

Storyboarded documentation files #355

merged 3 commits into from
Oct 4, 2019

Conversation

KeithJRome
Copy link
Contributor

All Submissions:


  • [YES] Have you followed the guidelines in our Contributing document?
  • [YES] Have you added an explanation of what your changes do and why you'd like us to include them?
  • [YES] I have updated the documentation accordingly.
  • [NA] I have added tests to cover my changes.
  • [NA] All new and existing tests passed.
  • [NA] My code follows the code style of this project.
  • [NA] I ran lint checks locally prior to submission.
  • [YES] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

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.

  • If it makes sense to do so, the index doc could be moved over and embedded directly within the main project README.md

Does this introduce a breaking change?


  • [NO]

Any relevant logs, error output, etc?


(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Other information


@@ -0,0 +1,13 @@
# 3. Creating a New Stack
Copy link
Contributor

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)

Copy link
Contributor Author

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

Copy link
Contributor

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?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 on CIT

@@ -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").
Copy link
Contributor

@TechnicallyWilliams TechnicallyWilliams Oct 3, 2019

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

Copy link
Contributor

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)

KeithJRome and others added 2 commits October 2, 2019 23:44
Co-Authored-By: Dexter Williams <dexterwilliams04@gmail.com>
@KeithJRome KeithJRome merged commit 00d0cc3 into master Oct 4, 2019
@KeithJRome KeithJRome deleted the 347-story-board branch October 4, 2019 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants