-
Notifications
You must be signed in to change notification settings - Fork 44
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
Host documentation on readthedocs.io #72
Comments
Ideally Sphinx + MyST + RTD, the same as the rest of EBP 😬 You don't actually need to run a GH action, just turn on PR runs on RTD: |
Thanks for the input, I really don't have much experience in any of this. Sphinx + MyST + RTD sounds great. Or if we want to keep using
Nice! Maybe it's possible to use a GH action to "validate" the docs though? Fail CI if docs fail building, so we know not to merge a PR unless the docs are fixed? Or does Sphinx build ever fail? I'm still a noob here 😄 |
Oh MyST is already commonmark compliant. Its just add extra (optional) syntax plugins to the parser. If you don't use them, then it works exactly the same as CommonMark (we are in fact in talks with RTD to deprectate ReCommonMark in favour of MyST)
Yep this already happens with the RTD builds (you can see the check e.g. in executablebooks/markdown-it-py#58), you just need to add to the repo https://github.com/executablebooks/markdown-it-py/blob/master/.readthedocs.yml |
I can try to get round to making a PR for it at some point 😄 |
Yeah this is what I was thinking could be problematic. But I think you are right, we don't really have to use the extra syntax and if we want to in some files, then skip mdformatting that file etc.
Nice!
This would be amazing! |
Create docs with either
- MkDocs
- Sphinx + CommonMark or MyST
Build the docs in Github Actions.
Publish on readthedocs.io
The text was updated successfully, but these errors were encountered: