Feature Requests

Hello! Running a Snyk audit on @docusaurus/core@3.8.1 shows a Medium severity issue with inflight@1.0.6 (abandoned package, known memory leak): @docusaurus/core → @docusaurus/utils → shelljs@0.8.5 → glob@7.x → inflight@1.0.6 inflight has no patch and is unmaintained. glob@9 and rimraf@4+ removed this dependency. Is there a plan to drop shelljs / upgrade dependencies so that inflight is no longer pulled in?

When printing a page, you still see the "Edit this page" link -- but I think that should be not part of the Printable view.

I feel like this is pretty much going to be a necessity on documentation sites going forward. Would be great if you could specify an OpenAI key, vector DB key and be done.

While we have Markdown linkification that resolves [](path) links, these are just turned into plain <a> tags. Gitbook allows the {% page-ref page="./ path.md " %} syntax, which produces a nice standalone link, displaying the permalink and the target page title. We can probably expose a linkify API that takes a Markdown path and returns a page's metadata, containing permalink, title, etc., maybe even an OOTB standalone link component. Don't know how non-trivial it would be to implement such a feature, and it would probably require reaching deep into the current infrastructure.

test

test

111

The implemented effect is the same as Wikipedia and Obsidian.

Hi Docusaurus team and community, As our remote community grows, celebrating birthdays, releases, or major milestones often gets lost in the shuffle. I’d love to propose a simple, low-effort feature that brings a bit of human warmth back into our interactions: free, shareable group eCards. Imagine if we could: Generate a link that allows everyone to contribute a message, GIF, emoji, or quick note—no login required. Share it on the community or Slack channel, and view the assembled card as a celebratory moment. See Docusaurus-themed card templates, turning virtual applause into a memorable keepsake. This could help us mark releases, say thanks to core contributors, or celebrate community birthdays in a fun, inclusive way. Does this align with anything being considered, or does anyone know if something like this exists already? Thanks for listening—and for all you do in keeping our docs platform vibrant!

The goal is to combine the Download Licenses Mojo of the license-maven-plugin < https://www.mojohaus.org/license-maven-plugin/download-licenses-mojo.html > with Docusaurus in combination with versioned documentation. Our solution is a folder structure like this docs/third-party/files/ where files may contain downloaded artifacts such as Apache-2.0.txt (works) or MIT.html (does not work). This does not work, as plugins such as the transformLinks plugin ignore *.html files by intention: < https://github.com/facebook/docusaurus/blob/fa8ae13e668fcbc0481ce10c0a734e2a5b397293/packages/docusaurus-mdx-loader/src/remark/transformLinks/index.ts#L185-L187 > It is more than that, though, as *.html files are not even copied to the build/ folder (unless, according to the documentation, they are placed in the static/ folder). We tried with a Docusaurus plugin to manually copy the files, but gave up, as this requires (for versioned documentation) to follow the same strategies (like using next/ folder) as applied by the versioned docs feature. Note, that controlling the output of the Download Licenses Mojo is possible, but not feasible (e.g., because <licenseUrlFileNameSanitizers> or not applied to file extensions). For now, we just gave up linking HTML files. Supporting it "out of the box" by Docusaurus would be great... or any advice, how to add a Docusaurus plugin to support this.