Enable Pages Update Feed for OSCAL Pages Site

[aj-stein-nist]

User Story

As a community user, in order to properly to see what pages in particular update from time to time on the site without individually inspecting each site, I would like a machine-readable mechanism friendly for web browsers, email clients, and/or relevant consumer software on personal computers to know about site updates.

Goals

• [ ] Communicate website page updates consistently and effectively on a change by change basis
• [ ] Use a well-known, industry/community-accepted format that allows producers and consumers to exchange these changes in a way web browsers, email clients, or other software commonly used and popularized for work websites.
  • [ ] Research Atom (maybe traditional RSS), discuss with team and/or community if there is any reason to pick an alternative

Dependencies

No response

Acceptance Criteria

• [ ] Integrate a solution into the hugo website publication pipeline with the machine-readable with Atom, RSS, or recommended alternative update notification mechanism.
• [ ] All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
• [ ] A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
• [ ] The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

[david-waltermire]

Maybe Hugo templating can be used to address this?

[aj-stein-nist]

Given the current approach charted in the #1638 draft, we can close this and reopen accordingly as needed if that approach, counter to this issue's recommendation, doesn't work short-term or long-term.