The SchemaBlocks Github organisation contains several specifically scoped repositories. Please use the relevant Github Issues to and/or GH pull requests comment and contribute there.
The structure of the code repositories is a pre-requisite for the parsing of the
schema files. Please refer to the documentation in the tools
repository.
SchemaBlocks is organized around individual “donor”-repositories. The standard setup is to have a donor schema and the derived documents represented in its own repository. Those repositories follow an “sb-“ prefixed naming convention.
{S}[B] code repositories adhere a consistent structure & naming:
sb-code # each of the code repositories
|
|- source # original code
|- working # for editing, temporary...
|- schemas # master transformed JSON Schema files as YAML; read to produce the output files
|- generated # contains files generated from main schema YAML files
|- json # .json version of the schema
|- examples # .json example data, from inline examples
|- doc # .md documentation, from inline documentation