VSCode is a highly popular IDE for working with Markdown files in Docusaurus repos. However, .mdx files are not natively supported by VSCode, and you're required to install the 3rd party, open source MDX Extension to support working with .mdx files in VSCode. A significant issue as of this datestamp (7-Nov-2024) is that the MDX Extension for VSCode doesn't support IntelliSense link path completion for # and ## triggers in .mdx files. This means that a critical everyday authoring task for your front-line technical writers -- creating links within and among all the topics in your docsite -- is greatly crippled if you force your front-line tech writers to work ONLY with .mdx files. I've raised an issue for this at mdx-analyzer: https://github.com/mdx-js/mdx-analyzer/issues/482 I've also raised a discussion for this at mdx-js: https://github.com/orgs/mdx-js/discussions/2557 However, since mdx-js and mdx-analyzer are OSS repos, it's anyone's guess when they will be able to prioritize fixing this problem. Perhaps one lever that the Docusaurus team can apply is evidenced in the discussion at mdx-js: they do seem to be open to PRs from anyone with the capability to fix this issue.