Build
Run npm run build and use Docusaurus's generated build/ output, or the directory selected with --out-dir.
All static exports
For documentation review
Preview a Docusaurus documentation build for review.
Docusaurus generates a static documentation site when you build it. HTMLShare can publish the generated build directory as a ZIP so reviewers can read the docs in a browser and check navigation, deep links, base paths, and assets. It does not run Docusaurus or provide a documentation server, backend, authentication, or production hosting.
Static export contract
Documentation is more than index.html
A useful documentation review checks the generated site as a reader experiences it, including the links and assets beyond the home page.
Navigation
Open the navbar, sidebars, breadcrumbs, version or locale links included in the build and confirm each path leads where expected.
Paths
Test direct deep links, the configured baseUrl or base path, CSS and JavaScript bundles, images, and downloadable assets at the preview location.
Where the export helps
A browser link makes the next conversation concrete.
Documentation release review
Give writers, developers, and product owners a browser link to read the generated docs before a release is announced.
Sidebar and navigation QA
Check category order, navbar links, breadcrumbs, version or locale controls, and the paths readers use to move through the site.
Deep-link and asset check
Open representative documentation URLs directly and confirm that base paths, CSS, JavaScript, images, and downloads resolve from the preview.
Why this handoff works
Keep the useful part close to the artifact.
Review documentation in context
Readers can inspect the generated pages, navigation, code examples, and supporting assets without installing Docusaurus or opening the source repository.
Catch path issues before release
A fresh static URL makes incorrect base paths, broken deep links, missing bundles, and misplaced images easier to find.
Keep the build replaceable
Publish a new ZIP for each review round while the docs team keeps ownership of source Markdown, configuration, versioning, and release automation.
A three-step workflow
From the right files to the right reaction.
- 01
Build the documentation site
Run the Docusaurus build command in your normal local or CI workflow and locate build/, or the custom directory selected with --out-dir.
- 02
Zip the generated site
Package the complete static output with index.html, documentation route folders, CSS, JavaScript, images, fonts, downloads, and other generated assets.
- 03
Test the reader paths
Open the preview and representative deep links, then check navbar and sidebar navigation, baseUrl or base path, asset loading, and mobile behavior before sharing.
Know the boundary
A preview is useful because it is honest.
HTMLShare publishes browser-ready static output. Keep builds, source tools, private access, live data, and production operations in the systems built for them.
HTMLShare does not run Docusaurus
Build the documentation site in your local or CI workflow first. HTMLShare publishes the resulting static files.
Static documentation snapshot
The ZIP contains generated documentation pages and assets. It does not provide live docs APIs, server rendering, backend logic, authentication, or content editing.
Preview before production
Use production documentation infrastructure when the site needs a durable domain, release automation, access controls, monitoring, or ongoing operations.
Keep exploring
The next useful page is nearby.
Before you publish
Docusaurus static docs build FAQ
Can HTMLShare build my Docusaurus site?
No. Run the Docusaurus build in your local or CI workflow, then upload the generated static output.
What should I upload for a Docusaurus preview?
Zip the complete build directory with index.html, documentation route folders, CSS, JavaScript, images, fonts, downloads, and other generated assets.
How do I check Docusaurus deep links and base paths?
Open representative documentation URLs directly from the preview and verify that the configured baseUrl or base path matches the preview location. HTMLShare does not rewrite Docusaurus links.
Is this production hosting for Docusaurus?
No. It is a static build preview for documentation review. Keep release hosting, access control, server behavior, and ongoing operations in the production documentation environment.
Ready for the next review
Put the current page in front of the right person.
Create a noindex preview link for the static HTML or ZIP project, then move approved work to production when it is ready.