Skip to article frontmatterSkip to article content

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 specification[1]. 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 List of MEPs is where you can find all of our MEPs.

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 List of MEPs.

Table 1:List of MyST Enhancement Proposals

NumberTitleCreatedStatusDiscussion
0001MyST Enhancement Proposal Bootstrap Process2022/10/16Accepted#843
0002Cross Reference Simplifications using Markdown Links2023/03/03Accepted#10
Footnotes

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

    ↩
MyST Enhancement Proposals
Process Overview