In many cases we need some equivalence of structure tags in rST, most of that can be supported via embedding rST(because markdown was not designed for related constructs). Then it is a bit like inlining asm in another language. The general new constructions in myST dialect might need some time to settle down. Because Sphinx enjoys a wider community support for rST, most features are also more well tested, sometimes the markdown translation suffered some problems. In a lot of cases we found that we need to fallback to embedding rST for control as well as the API documentation generation. At that point, rST became a more appealing choice.
We initially enabled mixed markdown and rST support with the assumption that such option would have been easier. As we start to use more structured reference tags we found that the difference was not as huge compared to the amount other effort (of putting up text and figured) --- [Visit Topic](https://discuss.tvm.apache.org/t/docs-discuss-convert-restructuredtext-docs-to-markdown/10264/6) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/5a72aea0c743fe33bc4fd72c691c93a21de3530834c20f8415e513ca416590e0).
