-
Notifications
You must be signed in to change notification settings - Fork 82
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
Handle .mdx files #604
Comments
@olafurpg I wonder if adding
will be enough? As far I can tell it should allow to process mdx files but I've never seen mdoc codebase before and I'm not sure.
|
I think that should work, did you manage to test it out @kpodsiad ? |
It's not enough, |
Have you tried the flag —markdown-extensions=mdx? Everything in that settings file can be configured via the command line or sbt plugin |
I tried and it worked, though it feels more like a workaround than a proper configuration. I'm not sure how to configure these things from the SBT plugin level, since mdocExtraArguments ++= Seq("--markdown-extensions", "mdx", "--markdown-extensions", "md", "--markdown-extensions", "html") (I had to repeat It seems to me that Putting aside the fact that Docusaurus has moved ahead of Mdoc (which by default supports Docusaurus v1 only), it's worth considering supporting the latest version. Even from version 2, it offers several key benefits, like more customization options and better UX. They are essential for modern-looking, clear and easy-to-read documentation. And generally, not many changes are needed. I'm currently using Mdoc with Docusaurus 3 (but without using the DocusaurusPlugin to avoid hacks and workarounds). To sum up, I tested it and everything works 😄 Just takes a bit of stubbornness and perseverance. |
mdoc seems to be designed to work with Docusaurus, which uses MDX. Tools understand MDX better when the file extension is .mdx. Mdoc should process .mdx files the same way as .md files.
The text was updated successfully, but these errors were encountered: