You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The draft registry is built with Jekyll collections. Each item in the collection, representing a registry entry, is a markdown file containing machine-readable properties in YAML front matter, followed by the content of the registry entry page. Here's an example of an Alternative Schema registry entry:
We agreed on a recent TSC call that we'd like to better encapsulate the layout for registry entry pages. There are several benefits:
It's less boilerplate code that contributors have to copy-and-paste into a new registry entry.
It's easier for TSC reviewers to verify that the submission is correct and conformant.
This ensures that we see a uniform layout on all registry entry pages.
It's easy for us to update the layout of all entries in a given registry (i.e. a given Jekyll collection) without having to edit individual registry entries.
This seems to be easy to solve with Jekyll {% include %} tags, described here.
The text was updated successfully, but these errors were encountered:
tedepstein
added a commit
to RepreZen/OpenAPI-Specification
that referenced
this issue
Feb 4, 2019
The draft registry is built with Jekyll collections. Each item in the collection, representing a registry entry, is a markdown file containing machine-readable properties in YAML front matter, followed by the content of the registry entry page. Here's an example of an Alternative Schema registry entry:
We agreed on a recent TSC call that we'd like to better encapsulate the layout for registry entry pages. There are several benefits:
This seems to be easy to solve with Jekyll
{% include %}
tags, described here.The text was updated successfully, but these errors were encountered: