Skip to content

Docs: Refactor/review linked guidance usage, and move jsonschema directive to end of sections #1467

@yolile

Description

@yolile

At the same time we can make the changes suggested in #1434 (comment):

...we want all content except the extensions list above the jsonschema directive, as otherwise it's easy to miss.)

I think we might start using a simpler format of "seealso ... How to [do X]" when linking to guidance.

Originally posted by @duncandewhurst in #1297 (comment)

We can search for "For more information". In many cases (not all), seealso would be better. There are also some {note} that start with For that can be changed to seealso.

Metadata

Metadata

Assignees

Labels

Focus - DocumentationIncludes corrections, clarifications, new guidance, and UI/UX issues

Type

No type

Projects

Status

To do: Reference

Relationships

None yet

Development

No branches or pull requests

Issue actions