Move web content from OSCAL, and other streamlining. (Revised for Release)

[Compton-US]

Committer Notes

This is a corrected PR based on the issues around #1824.

In support of Issue #1802

Currently in rapid prototype mode with the team.

• Website content moved to OSCAL-Pages project. This project will build and publish the public website.
• Reference content moved to OSCAL-Reference project. This project will build and publish the developer documentation. AKA OSCAL Reference.
• OSCAL repo in this branch has been reduced to only the model content.

Remaining to determine:

• Linking up the websites so that it is least disruptive to the public.
• The generated xml and json content has been removed from this branch. We need to talk about this, and what is the "right" way moving forward. I think there are a number of options and opinions to consider.
• Figuring out the entry point into the public website. (linking, landing page, etc)

Benefits:

• Less activity on the OSCAL project unrelated to models.
• Will make it easier for the community to monitor.
• More focused workstreams between model development, website content/education and experiments with models.
• Depending on how we publish the schemas-and-converters artifact, may make it easier for the public to access and use releases of OSCAL with less tooling.
• Reference will be in position to be updated and enhanced over time for development use.
• Public website can update at-will without impacting the OSCAL model project.

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Do all automated CI/CD checks pass?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable? A.J. is waving this, N/A.
• Have you included examples of how to use your new feature(s)? A.J. is waving this, N/A.
• Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.

[aj-stein-nist]

I am very very happy with this. I will test more but I assume we need to answer the one big question before moving forward.

[aj-stein-nist]

Maybe blocking 🤷: we still need to figure out this piece (stick with this, move to metaschema-xslt in the same PR) before we can formally, merge, right?

[Compton-US]

I'll take guidance here. I'm not quite as confident on the best course.

[aj-stein-nist]

@nikitawootten-nist with usnistgov/metaschema-xslt#45 on the way and close to setting off the baking timer in the oven, I assume we are close to ready to switch out this sprint?

[nikitawootten-nist]

Based on previous discussions we've had, this all looks great!