Feature Requests

At work we have multiple teams contributing docs to a single docusaurus project. However those docs don't reside in the docs folder, instead they are published via npm by their respective teams (as it was decided that they want to colocate their documentation with their app that they are developing). Thus, when building the docusaurus project those markdown files (from within the node_modules folder) are then copied to the docs folder so that docusaurus can find it and build it. (In the docusaurus.config.ts file we copy the external documenation to the docs folder) However while it works, its not at all smooth and its a little unfortunate that you cannot programmatically create pages, like with other static site generators like Astro. I tried to look at plugins but I couldn't figure out how to add pages to the existing content, just brand new pages (they were missing side bar etc.) Some of the pain we currently experience: needed to adapt logic from v2 to v3 (was triggering an infinite build, due to how docusaurus.config.ts is imported and parsed) since the files are actually copied to the docs folder we use gitignore to not version them. when switching branches those files then persist As said it would be nice if docusaurus could support that use case natively like other static site generators. Basically programmatically create pages that have sidebar, header etc, where you only need to provide the content.

As the amount of content grows in numbers and in depth, a fixed width sidebar makes it cumbersome to navigate.

I'm seeing integrations like this on many technical documentation pages: https://cityweft.gitbook.io/docs/getting-started/quickstart Click on the copy dropdown and you'll get options to: Copy page as Markdown for LLMs View as Markdown Open in ChatGPT Open in Claude Connect with MCP Connect to VS Code It would be great if Docusaurus had a similar built in integration. It's something our users are asking us for.

An alternative to Algolia search. Working offline, under VPN and in private networks.

An implementation to the markdown rendering similar to how adoc does it would be awesome: https://asciidoctor.org/docs/asciidoc-writers-guide/#listing-and-source-code-blocks I would love to be able to add notes like this to codeblocks.

When writing tutorials, one may need to provide the content in different "flavors" (e.g., different prog. language and IDE combinations). Currently this can be done by using tabs or by embedding the variants into the docs structure. It would be nice if we could instead have a dropdown selector for something like this.

Many times, user may need to download the documents to view later, print, or collaborate with others. Having the ability to download a rendered page as PDF by clicking on some icon would be very useful

I have a usecase which multi-level navbar is usefull for me. Also it can be used for nested docs.

Docs are full of jargon, and it's way more convenient to get quick definitions of key terms through tooltips. Otherwise we're stuck with using hyperlinks, and people have to jump around or open a dozen tabs until they learn all the terms well enough not to have to. Tooltips are a better way!

The possibility to add a swagger documentation into Docusaurus