-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document OSCAL Markdown #357
Comments
5/23/2019#283 is nearly done so we can start working on this issue. |
@wendellpiez It would be good to update the website prose page to include a mapping between HTML and Markdown features that are supported. This can be bumped to sprint 22, as it is not a blocker for the M1 release. |
#452 needs to be completed before this is closed. |
#451 needs to be fixed to ensure parameter insertion is handled as expected before this is closed. |
This has been completed in PR #449. |
User Story:
As an OSCAL User building interfaces, I may need to know how OSCAL's flavor of Markdown works and what it permits.
Goals:
Dependencies:
#343 must be finished so we have confidence that OSCAL Markdown works as currently designed.
#452 needs to be completed to ensure that the prose documentation page is in sync with the actual content generation behavior.
#451 needs to be fixed to ensure parameter insertion is handled as expected.
Acceptance Criteria
Users can find some help on using OSCAL Markdown on the Pages site.
The text was updated successfully, but these errors were encountered: