Update Style for Generating Reference Model Anchors at Build Time

[JustKuzya]

Committer Notes

Partial fix for usnistgov/issue#1681

These two files hoos up anchors-js stuff for the older style deep-links at the recommended time in the event-lifecycle
Also makes sure that CSS hooks up behaviors to old site and ignores the newer versions.

• 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 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.
• Have you written new tests for your core changes, as applicable?
• Have you included examples of how to use your new feature(s)?

[aj-stein-nist]

Excellent work, just some important but very minor feedback to make the class names more legible to me. Also, I have some follow-up questions about layover AnchorJS styles we will be removing.

[aj-stein-nist]

@JustKuzya, did you get a chance to updated PR feedback? We will wrap up the sprint today so I wanted to know if we can close this out for this sprint or not.

[JustKuzya]

I thought that I pushed it either Monday last week or Friday the week before. I probably need to map the changes to the Issue from github DC From: A.J. Stein ***@***.***> Sent: Tuesday, May 30, 2023 9:44 AM To: usnistgov/OSCAL ***@***.***> Cc: Cousin, Dmitry A. (Fed) ***@***.***>; Mention ***@***.***> Subject: Re: [usnistgov/OSCAL] Update Style for Generating Reference Model Anchors at Build Time (PR #1789) @JustKuzya<https://github.com/JustKuzya>, did you get a chance to updated PR feedback? We will wrap up the sprint today so I wanted to know if we can close this out for this sprint or not. - Reply to this email directly, view it on GitHub<#1789 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACS6IVT6KWI3FR5YEH2N3RDXIX2QFANCNFSM6AAAAAAX6WL5H4>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[JustKuzya]

The "hooked up" apparently is just one right-hand ring-finger flutter away from the "hooled up" :) My bad for not catching it before push

[aj-stein-nist]

@JustKuzya can you update the metaschema submodule to the current develop branch commit now that PR has been merged?

[aj-stein-nist]

@JustKuzya can you update the metaschema submodule to the current develop branch commit now that PR has been merged?

Bump on this @JustKuzya, because we need the submodule moved up before I can approve and merge this (or I wouldn't keep bringing it up).

[aj-stein-nist]

Sigh, how can we even get a merge conflict on pushing up a submodule!? I didn't notice this while pairing. I will have to investigate later.

[aj-stein-nist]

The local performance metrics were dubious when run in a virtualized developer weird ways but Dmitry provided interim metrics (Site-Benchmarks.xlsx). Running hugo serve locally seems to have weird crashes even with Chrome Lighthouse running locally in weird ways I also encountered, so more to follow on that as we close out this issue.