Feature Requests

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

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

Is it possible to make the last item of the TOC active even if the respective content is short and my custom footer height is minimal? The current set up only allows the TOC items to become active if they sit right on top of the page, often not enabling the last items to become active.

By default, the last modified date/user is shown at the bottom of each page, but that is the date/user of the entire repository being worked on, so I would like to see the last modified date/user of the files in each article directory. If possible, please display the last modification date/user of the entire repository as the site modification date/user in the left side menu.

It would be nice if we had a way to use docusaurus with context7

Docusaurus has the list of the locales, why ask the user to list them ? :)

Currently, Docusaurus does not natively support text highlighting using double equal signs (==text==), which is a common syntax in various Markdown flavors and documentation tools. Adding support for ==text== to highlight text would improve readability and enhance content emphasis without requiring additional HTML or custom plugins. Expected Behavior: Text wrapped with == (e.g., ==highlighted text==) should render with a background color (similar to <mark> in HTML). This feature should work consistently across Docusaurus documentation and blog pages. https://www.markdownguide.org/extended-syntax/#highlight Use Case: This syntax is widely used in documentation and note-taking tools like Obsidian and Typora. Adding it to Docusaurus would make it easier for users to maintain a consistent writing experience across platforms. Would love to see this feature integrated! 🚀