Sébastien Lorber

I'm in touch on Twitter, we'll take over the PR if needed

This usage should be supported, but it's a current limitation of the existing system. Unfortunately, I'm not sure how to implement this technically, and still busy on i18n. In the...

@oriooctopus unfortunately I suspect this to be quite complex to implement, and can't even give you much help to do so because I'm not sure how this should be done....

Yes @jknoxville this is what I have in mind: a recursive visitor that is able to "flatten" the TOC structure of multiple MDX docs (and preserve the correct TOC ordering)....

if that helps I remembered that Gatsby has a way to extract all imports/exports from MDX. https://github.com/gatsbyjs/gatsby/blob/2e42197025e2e1bac06c721c3cc44135bf8ef526/packages/gatsby-plugin-mdx/utils/gen-mdx.js#L199

@Laptopmini, I think extracting headings from React components is an edge case, more complicated and expensive (as it would require rendering the comp to see what's the output), so it's...

@Laptopmini what I understand is that you want to create a TOC dynamically from data fetched from an API. This is unrelated to the current issue which is about importing...

Some related notes: - We added better support for the _ prefix convention so that doc partials are not creating additional routes: https://github.com/facebook/docusaurus/pull/5173 - Instead of using MDX imports (which...

A temporary workaround could be to export your own TOC manually, eventually re-using the TOC exported by the MDX partials you used. I've used this trick on our changelog page,...

The doc page is static. At the end of the day, the HTML markup produced by the CI must output a date in a given format. And at this time...