Once asset documentation has been added to the schema (#792) and once that index content is wired up to conditionally render asset page tabs for usage, style, code, and accessibility (#793), we'll want markdown templates for each of those sub-pages so contributors can copy/paste the template so they have a skeleton of recommended headings and sections to fill out.
[ ] The platform web app has contribution guidance where you can understand the indent of each asset documentation page, as well as templates to copy so we can guide users to have consistent asset documentation
Once asset documentation has been added to the schema (#792) and once that index content is wired up to conditionally render asset page tabs for usage, style, code, and accessibility (#793), we'll want markdown templates for each of those sub-pages so contributors can copy/paste the template so they have a skeleton of recommended headings and sections to fill out.
We have two component usage docs templates:
No style templates:
One code template:
No accessibility template.
And two pattern templates:
Acceptance criteria