Frameworks

Docusaurus on Stackap

Stackap builds a Docusaurus documentation site and serves the build folder from nginx, using the 404 page Docusaurus generates.

How Stackap recognizes Docusaurus

A project counts as a Docusaurus site when it has a build script and lists @docusaurus/core as a dependency. It takes the static-site path, which returns real 404 responses. Docusaurus's default scripts include a build script, so no renaming is needed.

What Stackap builds

Docusaurus writes its finished site to build, which is on Stackap's list of output folders. The generated image runs the build, copies that folder into nginx, and serves it.

Docusaurus also writes a 404.html, which Stackap's nginx configuration is set to use for missing pages, so your own not-found page appears with a real 404 status.

The one setting that most often breaks a first deploy is baseUrl. It defaults to /, which is correct for a site on its own domain. Projects that were published under a sub-path, such as a repository name, often carry a different value that must be changed back.

What a Docusaurus project needs

• The default build script.
• A baseUrl of / unless the site really lives under a sub-path.
• A correct url in the config, so canonical links and the sitemap are right.
• A lockfile.

Verification status

The shared static path has a real Docker build in the platform tests.

Still to verify: a Docusaurus build by us, including versioned docs, the search plugin, or internationalization with several locales, which write extra folders.

Early-access scope

• No Docusaurus site has been shipped on Stackap yet.
• Search that relies on an external service works only if that service is reachable from visitors' browsers; Stackap provides none.
• Large documentation sites build slowly and use memory the live apps share.
• The generated build image uses Node 24, so a project that needs an older Node should bring its own Dockerfile.
• No CDN, so distant readers see more latency.

Questions

Last updated 2026-10-03.