Extended Description
As user, I would like a good introduction to the ASAP validations, so I can learn how to navigate the rules and apply them to my documents.
Context: the home page of the documentation currently is 10x phase 3/4-specific, and in need of updating for the long-term.
Acceptance Criteria
[ ] Documentation is appropriate for FedRAMP post-10x
[x] Documentation gives credit to 10x
[ ] Not just SSP - all OSCAL documents
[x] Use present-tense rather than future tense (eg, nix "will")
[ ] Consider making a distinction between "stakeholders" and "users" (users: drafters of documentation, developers integrating rules, reviewers viewing validation results)
Definition of Done
[ ] Acceptance criteria met
[ ] Unit test coverage of our code > 90% - needs automation story
[ ] Accessibility tests pass - needs automation story
[x] Automated code quality checks pass
[ ] Security reviewed and reported - check in with Wes on what we could do here
[ ] Reviewed against plain language guidelines
[x] Design QA passed
[x] Code must be self-documenting
[x] No local tech debt
[x] Documentation updated
[ ] Architectural Decision Record completed as necessary for significant design choices
Extended Description As user, I would like a good introduction to the ASAP validations, so I can learn how to navigate the rules and apply them to my documents.
Context: the home page of the documentation currently is 10x phase 3/4-specific, and in need of updating for the long-term.
Acceptance Criteria
Definition of Done