Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rebrand to mystmd #21

Merged
merged 1 commit into from
Jun 16, 2023
Merged

Rebrand to mystmd #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,5 @@
# extension-proposals
EBP Extension Proposals (EEP)
# MyST Enhancement Proposals

A formal process for changing [the MyST Markdown Specification](https://mystmd.org/spec) and an archive of present and past proposals.

See the [MyST Enhancement Proposals Documentation](https://mep.mystmd.org).
6 changes: 3 additions & 3 deletions docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
(governance:meps)=
# MyST Enhancement Proposals

A formal process for changing [the MyST Markdown Specification](https://myst-tools.org/docs/spec) and an archive of present and past proposals.
A formal process for changing [the MyST Markdown Specification](https://mystmd.org/spec) 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[^gov].
These are called **MyST Enhancement Proposals (MEPs)**.
Expand Down Expand Up @@ -31,15 +31,15 @@ Bear with us, and please provide feedback if you think the process can be improv

## MyST Specification

The MyST specification is at [`spec.myst-tools.org`](https://spec.myst-tools.org) (repository: https://github.com/executablebooks/myst-spec).
The MyST specification is at [`spec.mystmd.org`](https://spec.mystmd.org) (repository: https://github.com/executablebooks/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.

```{toctree}
:hidden:
MyST specification <https://spec.myst-tools.org>
MyST specification <https://spec.mystmd.org>
```

## List of MEPs
Expand Down
2 changes: 1 addition & 1 deletion docs/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ Merging this PR implements the MEP, and makes it a formal part of the spec.
Parsers may now implement this change as well. This MEP process is now finished.

```{admonition} Update the MyST documentation as well
While not formally part of the MyST spec, the MyST guide at [myst-tools.org](https://myst-tools.org) should also be updated as quickly as possible, so that users can more easily learn about the most up-to-date MyST specification.
While not formally part of the MyST spec, the MyST guide at [mystmd.org](https://mystmd.org) should also be updated as quickly as possible, so that users can more easily learn about the most up-to-date MyST specification.
```

## Appendix: When should I open a MEP?
Expand Down