Skip to content

Latest commit

 

History

History
32 lines (20 loc) · 1.41 KB

index.md

File metadata and controls

32 lines (20 loc) · 1.41 KB

(governance:meps)=

MyST Enhancement Proposals

A formal process for changing the MyST Markdown Specification and an archive of present and past proposals.

Because the MyST specification has many interior and exterior stakeholders, we use a more formal and structured process around changing the specification1. These are called MyST Enhancement Proposals (MEPs).

This process is encoded in https://github.com/jupyter-book/myst-enhancement-proposals and in this documentation. The sections below describe the process, and the is where you can find all of our MEPs.

This process is relatively new.
Bear with us, and please provide feedback if you think the process can be improved!

MyST Specification

The MyST specification is at spec.mystmd.org (repository: https://github.com/jupyter-book/myst-spec). It is the source of truth for MyST Markdown syntax.

When a MEP is accepted, it is generally implemented by modifying the specification and the documentation around it. MyST parsers may then choose to implement these changes on their own.

List of MEPs

Below is a list of all past and current MEPs, you can also find this table at .

Footnotes

  1. See our Team Compass for other governance and decision-making processes in the Executable Books community. ↩