3 ms·
> reStructuredText (reST) by itself can be pretty rough. reST combined with Sphinx is pretty great. So, you've made a convincing argument of why we should pref
by einpoklum 2y ago
> reStructuredText (reST) by itself can be pretty rough. reST combined with Sphinx is pretty great.
So, you've made a convincing argument of why we should prefer Markdown to reST, 9 times out of 10. If we're working with Sphinx we'll give it serious consideration.
- Spivak 2y agoI'm not really sure what your point is. What you're saying agrees with both the parent and the OP.
- einpoklum 2y agoMy point is that the reason GP prefers rST is a reason not to prefer it, usually.
- kaycebasques 2y agoI heard recently that MyST [1] now has full feature parity with everything that reST provides. If I were starting a new project today I would seriously look into Markdown-based Sphinx site powered through MyST. For Pigweed we collectively don't seem to hate reST enough to justify the huge project of migrating everything over from reST to Markdown. So yeah, I don't really have strong opinions on sticking with rest per so. I only have strong opinions about Sphinx being probably the best choice out there for large docs sites. [1] https://myst-parser.readthedocs.io/en/latest/ https://myst-parser.readthedocs.io/en/latest/