-
-
Notifications
You must be signed in to change notification settings - Fork 531
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
Investigate using Myst for documentation #1872
Comments
worth investigating this too by Stripe: https://markdoc.io/ |
So I start looking at this to generate documentation and I had a try setup an initial sphinx configuration with So I forked and tried to fix it in order to generate some valid Markdown atm... But I want to check also if this is the right path, or if you have other ideas/tools in mind @patrick91 ? |
for the website I think we should keep as much as we can in JS/TS, I've seen this https://github.com/executablebooks/mystjs but not 100% sure it is worth putting effort into this just yet, I think we'll have a new design for the website at some point in the next few months. I think we can decide then what we want to do :) |
Going to close this, I'll do some work on the website around december and hopefully I'll get around some of these things 😊 |
Myst seems quite interesting, it does support some stuff we have already built: https://myst-parser.readthedocs.io/en/latest/syntax/syntax.html
Maybe we can start using it and update the website to use a parser for myst :)
also supports autodoc via sphinx, which could be nice to have https://myst-parser.readthedocs.io/en/latest/sphinx/use.html#use-sphinx-ext-autodoc-in-markdown-files
The text was updated successfully, but these errors were encountered: