Skip to content

Rewrite the guides to Markdown #450

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

jsmitka
Copy link
Contributor

@jsmitka jsmitka commented Jul 18, 2025

In the spirit of #434, I rewrote all the pages under "guides" to markdown. If this gets accepted, I can continue to rewrite the rest of the docs.

However, if we end up using MkDocs, please note that MyST (the markdown parser for Sphinx) use a different syntax than MkDocs for several elements:

  • Extra properties of Images: MyST vs Material for MkDocs
  • Admonitions - notes, warnings, etc.: MyST vs Material for MkDocs
  • Cross-references: MyST vs regular links with anchors in MkDocs (there might be another solution I am not aware of).
  • Custom in-line roles: {slack}`<...>`, {twitter}`<...>`, {gh-repo}`<...>` - those will need to be re-implemented as plugins, or just rewritten as plain links (might be an better option).
  • Source comments: MyST vs HTML comments in PyMdown extensions.

There might be more differences, but these are the ones I run into. Additonal work will be needed to get it working properly under MkDocs.

jsmitka added 2 commits July 18, 2025 16:59
linkify extra was added to the `myst-parser` dependency and `uv.lock`
was updated accordingly.
Please note that the MyST syntax of several elements (e.g., admonitions,
images, cross-references etc.) is different from the syntax used by
MkDocs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant