Update README and Archive Project

[aj-stein-nist]

• [x] Create a PR and add this section to the top of the README, using the wording I am providing in this HackMD, get it reviewed, and merged as quickly as possible.
• [x] Add a banner to the application landing page. If you do not use the USWDS, you should still mimic the style of the example as seen in the example below. You are imitating the blue box in this screenshot. Replace "This website is in the alpha stage of development. Help us improve ->" with the following text for this project's website: "This website and its code are no longer under active development, read more details here." You do not want to include help us improve: the link to the README page with the updated project status will suffice. Instead of the bright blue color, please set the background to #d9e8f6.

• [x] Confirm usnistgov/OSCAL#118 is complete (see dependencies below)
• [x] Archive the project using the instructions from GitHub. If you do not have sufficient permissions, please reach out to @aj-stein-nist to get this done.

Dependencies:

• [x] Completion of all XSLT for OSCAL pipeline support moved to oscal-xslt.
• [x] Completion of https://github.com/usnistgov/oscal-cat/issues/118 so notice of similar pause of OSCAL CAT is present in last push of this site to pages.nist.gov

[aj-stein-nist]

@wendellpiez as discussed today when pairing on related issues, can you please work on this during the sprint with the intent to resolve it by 15 March 2023? If you have concerns about finishing it by then, or think you need help to do so to finish it by then, please let me know. It will be superful help, thanks!

[wendellpiez]

Started on this by copying all the WIP sitting in my fork out to a branch of the oscal-xslt repo to be merged there.

Next steps here (in a branch):

• [ ] remove xslt and other unwanted folders
• [ ] rewrite top-level readme
• [ ] rewrite site under docs directory w/ Hugo precheck

(I am not sure you are currently using this checklist, but please make sure to complete all identified work expressly mentioned in issue description, we will discuss during the next status update.)

[nikitawootten-nist]

Update: the team plans to draft a unified archiving message before making individual PRs.

[aj-stein-nist]

@wendellpiez I updated the checklist for completion of this task to address some questions and ambiguities around the work it is in the updated issue description above. I hope this clarifies what needs to be done. Please let me know if you cannot complete by COB tomorrow (end of sprint).

[wendellpiez]

@aj-stein-nist I can work on this but it's going to be a close one.

Main reason being that adding a banner in Hugo with language and styling has to be done through templating. Is anyone else having to set this up in Hugo?

[aj-stein-nist]

@aj-stein-nist I can work on this but it's going to be a close one.

Main reason being that adding a banner in Hugo with language and styling has to be done through templating. Is anyone else having to set this up in Hugo?

We can work together on this but it seems beyond the USA banner there is a DRAFT equivalent we can work off of:

https://github.com/usnistgov/hugo-uswds/blob/2d6444fcb9f788e275dcc56cbee2ef7002045e2c/layouts/partials/components/draft-banner.html

https://github.com/usnistgov/hugo-uswds/blob/2d6444fcb9f788e275dcc56cbee2ef7002045e2c/layouts/_default/index.html#L7

Similar idea, different content, is this a good starting point? It is like usabanner: true you use and draftbanner: true could work we just need to make an archivebanner and set that to true. I guess that would require either: setting up in hugo-uswds or overriding the default template here. I guess that changes the timeline.

[wendellpiez]

I actually designed and deployed a 'draft' banner -- problem there being it requires a flag on each page as you say.

Instead I am hacking a usa-banner into the banner.html template, which seems to work so far.

[wendellpiez]

I changed the language slightly to say a tiny bit less.