Refine content to create Pages in GitHub

[kscarf1]

Work to do once we have better documentation:

1. Create a branch named "nist-pages".
2. Move content to that branch.
3. Setup a webhook to publish to: https://pages.nist.gov/deploy

Goals:

Provide a useful collection of OSCAL documentation on https://pages.nist.gov that: 1) explains the concepts comprising OSCAL, 2) provides documentation on how to use OSCAL, and 3) decribes how to create and use the example catalogs and profiles we have created, and 4) describes how to create new content using OSCAL.

Acceptance Criteria:

• Verify that the site is deployed to https://pages.nist.gov
• Validate that the site provides documentation that addresses the goals above.

Was originally issue #30

[kscarf1]

3/15/2018 - Sprint 9 Progress Notes

• No progress this week - should have some progress to report next week.

[akarmel]

3/22/2018 - Sprint 9 Progress Notes

• Need Andrew's input to determine next steps (Karen will reach out to Andrew)
  • Will we be pulling docs from the "nist-pages" branch?, etc.
  • How will the workflow work?

[kscarf1]

Documentation on prep for pages.nist.gov publishing is posted at: https://github.com/usnistgov/pages-root/wiki/Configuring-your-repo-for-publishing-on-pages.nist.gov

[kscarf1]

Wendell, Dave, Andrew, and I met to discuss documentation workflow. When we are ready to generate content for pages.nist.gov, it will take just a few minutes to run scripts that automatically generate the page content without actually publishing it to pages.nist.gov. This will allow our team to review it and refine it before publishing the final version to pages.nist.gov. The nist-pages branch and other needed parts of this will automatically be created by the scripts. Andrew has demonstrated how this works at https://github.com/anweiss/OSCAL/tree/nist-pages.

Everything is ready for us to create pages.nist.gov pages. I need to first complete the content development in issues #110, #127, and #130.

[akarmel]

3/29/2018 - Sprint 9 Progress Notes

• See Karen's progress note above
• Just need to have content ready to run through this documentation workflow
• Intent is to setup a web hook to automate publishing at the end of this sprint

[kscarf1]

I have completed drafts of all content needed for pages.nist.gov release during Sprint 9. I have asked Andrew to convert the source documents into a Slate format for core team review.

[akarmel]

4/5/2018 - Sprint 9 Progress Notes

• See Karen's progress note above
• This is the final component that needs to be completed by Thursday, 4/12
• Two meetings scheduled for next week to both review documentation and to publish pages.nist.gov/OSCAL at the end of the Sprint.

[akarmel]

4/12/2018 - Sprint 9 Acceptance

• Publishing pages.nist.gov/OSCAL
• Closing issue.