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.

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

Recommend MyST-Parser for Markdown usage #9112

Merged
merged 1 commit into from
Apr 18, 2021

Conversation

astrojuanlu
Copy link
Contributor

Subject: Recommend MyST-Parser for Markdown usage, instad of recommonmark.

Feature or Bugfix

Not sure if I'd consider this a feature, a bugfix or a refactoring, but if I had to choose I guess it would be a bugfix.

Purpose

The recommonmark maintainers have proposed to sunset recommonmark in favor of MyST-Parser since the latter enjoys more community support, is more flexible, and has a brighter future. A few projects have already migrated since the announcement was made, and so far nobody has found unexpected problems. Both projects are configured as Sphinx extensions and work in a very similar way.

Disclaimer: I started working recently at Read the Docs as Developer Advocate, and my mission is to help projects improve their documentation. In particular, Sphinx is a core piece of what we do ❤️ and I would like to make more contributions in the future!

Relates

readthedocs/recommonmark#221

@tk0miya tk0miya merged commit c75ad02 into sphinx-doc:4.x Apr 18, 2021
@tk0miya
Copy link
Member

tk0miya commented Apr 18, 2021

Thanks!

@tk0miya tk0miya added this to the 4.1.0 milestone Apr 18, 2021
@astrojuanlu astrojuanlu deleted the markdown-myst branch April 18, 2021 16:38
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants