Feature Requests

Right now, the Docusaurus homepage talks about features like MDX, plugins, versioning, and search. But it doesn’t clearly say the most amazing part: 👉 You can build a full website just by writing Markdown. No setup, no coding, and it even comes with built-in search (Algolia), versioning, and translation. That message is really powerful — especially for people who aren't developers. It would be great to have a clearer headline like: “Turn your words into a website — instantly.” This makes the purpose of Docusaurus easy to understand at a glance. This is my first time contributing, and I’m just looking at ways to make the project even better. Thank you.

We have an extensive React based project with component library and utilities and would like to have the ability to generate API documentation from TypeScript. If Docusaurus can support MarkDown + TypeDoc APIs + 100% custom React themes it would meet most documentation requirements for engineering teams.

It'll also be cool to have themes like fumadocs - https://fumadocs.vercel.app/docs/ui/theme#themes If you fully enable Tailwind, the community could develop a lot more themes making Docusaurus look more modern like fumadocs, nextra and starlight.

I want to group the blog content based on my desired categories.

At the bottom of every GitBook doc page, there's a feedback widget that users can use to provide feedback to the docs maintainers about the page. The traditional way of opening an issue/pull request is usually too troublesome. This feedback widget could be a frictionless way of getting feedback on docs. Users would have to be in-charge of finding their own back ends for feedback storage or simply leverage on their analytics solution. Example: https://docs.gitbook.com/content-editing/pages-structure

There is a new standard for admonitions in markdown using block quotes. This is supported by Github ( https://github.com/orgs/community/discussions/16925 ) and Gitlab ( https://docs.gitlab.com/user/markdown/#alerts ). It would be great to support this syntax in Docusaurus as well!

If you create a folder structure like the following: - docs/ - test.mdx - subfolder/ - a/ - index.mdx - index.mdx You'll end up with document IDs test , subfolder/a/index and subfolder/index . The URL docs/subfolder works perfectly fine and resolves to index.mdx , but you have to specify subfolder/index in the sidebars file. When the file is called index.mdx , the ID should be auto-computed to just the directory name. This would ensure that document IDs and URLs match by default. Currently the logic to calculate auto-computed IDs is hard-coded in the docs plugin, so the only way of overriding it is to fork the whole plugin.

I don't think the current layout of the blog page is engaging enough or encourages users to click and read. The super large title, author information, post summary, image, and "Read More" button — while simple — make the page look like a site without CSS. It doesn't match the overall design and aesthetic of Docusaurus. I hope that a future version of Docusaurus will offer a card-style layout option for the blog page, similar to the layout used on the Showcase page.

Docusaurus currently uses Terser to minify source and generate license files, and Terser requires that source code either have a license comment /*! comment or use the @license tag in a comment in order for it to generate and include license information in the output. This can result in sites that may be distributing OSS code to browsers without properly fulfilling the license requirements of that code. For example, the theme-mermaid plugin distributes mermaidjs to the browser, but the bundle process in docusaurus does not capture the mermaidjs license like it does with React, prism, mark.js, etc. This can easily be accomplished using the license-webpack-plugin ( https://www.npmjs.com/package/license-webpack-plugin ) in the webpack bundle process