JSON Schema for Humans configuration file

Type: object

Choose how to generate JSON Schema for Humans documentation file.

Configuration parameters can be provided in several ways:

Type: boolean Default: true

Minify the output HTML document.

Type: boolean Default: true

Whether to consider the description as markdown and render it accordingly.

Type: boolean Default: false

Add an Expand all and a Collapse all button at the top of the generated documentation.

Type: boolean Default: true

For each property, show the relative place of that property in the schema.

Type: boolean Default: true

If a description is considered big, show only the beginning and add a Read more button.

Type: integer Default: 25

Advanced option
If link_to_reused_ref is false and a $ref in the schema refers to a parent of itself, we would get a RecursionError trying to render the documentation. To avoid this, each reference is checked for circular references.

This option determines the number of times to recursively follow definitions looking for a circular reference.

In other words, if a schema has a deeply nested element that refers to itself, this option may need to be increased.

Type: boolean Default: false

Mark a property as deprecated (with a big red badge) if the description contains the string [Deprecated.

Type: boolean Default: false

Extract the default value of a property from the description like this: [Default `the_default_value`].

The default value from the "default" attribute will be used in priority.

Type: boolean Default: true

Copy schema_doc.css to the same directory as RESULT_FILE after generation.

Type: boolean Default: true

Copy schema_doc.min.js to the same directory as RESULT_FILE after generation.

This file contains the logic for the anchor links.

Type: string


Type: enum (of string) Default: "js"

The name of the built-in template to use to render the documentation.

js is the default and uses javascript for anchor links, collapsible sections and tabs. flat uses no javascript, but has no interactivity.

Must be one of:

  • "flat"
  • "js"
  • "md"
  • "md_nested"

Type: string Default: null

Path to a custom Jinja2 template file.

There can be multiple files to split the template, but this path should be the entry point.

If no output file is specified, the extension of the template file will be used to determine the output documentation extension. i.e. if the template is in ./custom_template/content.html, the resulting documentation will have the html extension.

Type: boolean Default: true

Whether to render table of contents.

Type: boolean Default: false

Whether to display examples as YAML instead of JSON

Type: object Default: {"fenced-code-blocks": {"break-on-newline": true, "cssclass": "highlight jumbotron", "tables": null}, "tables": null}

Markdown 2 options for the descriptions. description_is_markdown must be true for this to have any effect.

Adding an extra, even if the value is false, will activate it. For example {"break-on-newline": false} will activate the break-on-newline extra.


    "fenced-code-blocks": {
        "cssclass": "highlight jumbotron"
    "tables": null,
    "break-on-newline": true,
    "cuddled-lists": true

Type: object

specific options to md template

Type: boolean Default: false

if true generate badges(eg: optional, required) using embedded image (https://img.shields.io).

if false, use text instead

Type: boolean Default: true

if true generate heading numbers to correspond to table of contents.

if false, do not generate heading numbers

Type: boolean Default: true

if true generate array restrictions section.

if false, do not generate