Automate the production of documentation on pages.nist.gov using metaschema and a CI/CD pipeline

[akarmel]

User Story:

As an OSCAL content consumer, I have access to documentation that is continuously up-to-date via an automated CI/CD pipeline.

Goals:

Develop a NIST CI/CD pipeline to automate the production of documentation on pages.nist.gov using the metaschema (@david-waltermire-nist)

Dependencies:

#273

Acceptance Criteria

1. Documentation is automatically developed for pages.nist.gov using a NIST CI/CD pipleline from the OSCAL metaschema

[anweiss]

This is dependent on support for some sort of "staging" endpoint on NIST Pages so documentation changes can be verified before pushing into prod ... i.e. https://pages-staging.nist.gov/OSCAL. According to the NIST Pages wiki, NIST Pages is based off of 18F's old pages-server project which had support for multi-branch publishing. However, @david-waltermire-nist would probably have to do some digging to see if this capability carried over into NIST Pages.

[wendellpiez]

There is also a dependency here, or at least a relation to #273, the Issue regarding (re)structuring the Pages site -- when the pages site changes, the CI/CD will also have to.

[david-waltermire]

This is done.