The OSCAL Styler is an XSLT 1.0 Fiddle application set up for OSCAL.
It should work with any XML and XSLT 1.0, however, not only OSCAL.
The user can provide an XSLT, and additionally CSS code, and edit both on the page.
Plus, it has a companion (little) application, the OSCAL Painter - same, except with a pre-coded XSLT to save that step, so only CSS is a factor.
Along with the new project are a couple of minor tweaks and updates elsewhere.
Completeness checklist:
Within the scope of work,
[x] All readme files and documentation resources are current
[x] Initial comments look reasonable
[x] Everything touched has been checked for parsing as appropriate (wf/valid)
[x] Everything is tested in multiple browsers (minimally: FF and Chrome)
[x] The top-level directory is current or planned for updating
[x] As appropriate, outbound external links are marked as class="external" (drives popup)
PR/merge guidelines:
Despite its being a bit cumbersome with respect to commit history, we are using git in a 'safe' mode to avoid potential issues aligning the publication branch, nist-pages.
Merging into main, squashing commits in a PR is okay (recommended)
Don't merge anything into nist-pages except main, and never squash commits in those PRs
The main branch also keeps up with nist-pages (merge commits), so after committing to nist-pages, pulling back is necessary
The OSCAL Styler is an XSLT 1.0 Fiddle application set up for OSCAL.
It should work with any XML and XSLT 1.0, however, not only OSCAL.
The user can provide an XSLT, and additionally CSS code, and edit both on the page.
Plus, it has a companion (little) application, the OSCAL Painter - same, except with a pre-coded XSLT to save that step, so only CSS is a factor.
Along with the new project are a couple of minor tweaks and updates elsewhere.
Completeness checklist:
Within the scope of work,
class="external"(drives popup)PR/merge guidelines:
Despite its being a bit cumbersome with respect to commit history, we are using git in a 'safe' mode to avoid potential issues aligning the publication branch,
nist-pages.main, squashing commits in a PR is okay (recommended)nist-pagesexceptmain, and never squash commits in those PRsmainbranch also keeps up withnist-pages(merge commits), so after committing tonist-pages, pulling back is necessary