Get contextual feedback on your deployed Docusaurus site

Q: Should I share docusaurus serve with a client?

The command is documented for testing the build locally and opens localhost on port 3000 by default. Use a deployed browser-accessible URL for external review.

Q: What do url and baseUrl control?

url identifies the site origin. baseUrl identifies the project path, must include a trailing slash, and is important when the site is hosted below the domain root.

Q: Why can the same build behave differently on another host?

Docusaurus notes that hosts handle URL and filename patterns differently. Check the trailingSlash setting and the selected host's behavior.

Q: Does Docusaurus require a particular hosting provider?

No. Its documented responsibility is building the site and emitting static files; the project team chooses how those files are hosted.

Q: What happens to files in the static directory?

Docusaurus copies them to the root of the build directory. Review their final deployed URLs rather than their source-directory paths.

Q: Do reviewers need repository access?

No. They review the deployed browser output, not the Docusaurus source, build environment, or hosting dashboard.

Paste the browser-accessible URL for the deployed documentation site, send one review link, and collect comments on the static pages your readers will actually browse.

See how it works

Loved by1,250+Agenciesand companies in 100+ countries

Docusaurus builds the files. Review happens on the deployed site.

Docusaurus generates static production files, while the project team chooses how and where those files are hosted. BugSmash reviews the resulting browser-accessible deployment.

Four documented build and routing details shape the review:

The production output is the build directory.
Running docusaurus build generates the static production files in the build directory. Docusaurus leaves the choice of host to the project team.
docusaurus serve is a local build check.
The serve command previews the built site locally and uses localhost on port 3000 by default. It is not a durable external review address.
url and baseUrl control the published location.
Docusaurus requires url for the site origin and baseUrl, with a trailing slash, for the path where the project is served.
trailingSlash can change hosting behavior.
The trailingSlash setting changes generated URLs, links, and emitted filename patterns. Docusaurus notes that static hosts can handle these patterns differently.

BugSmash adds a review layer around that deployed output:

share the accessible documentation URL, keep comments attached to the rendered page, and, when the script is installed on the rendered site, use the Feedback Widget for an authenticated browser session that a pasted URL cannot open by itself.

How it works

Three steps to a reviewed Docusaurus deployment

Build and deploy the intended revision

Run docusaurus build and publish the build directory with the url, baseUrl, and trailingSlash settings intended for that host.

Send one review link

Paste the deployed site URL into BugSmash and share the generated link. Reviewers work on the rendered documentation rather than the repository or local server.

Resolve comments on the deployed pages

Use each comment's page, selected location, screenshot, browser, operating system, and viewport context to update and redeploy the site.

Review the Docusaurus output readers will browse

Comment on rendered documentation

Attach each note to the deployed page instead of translating it into a Markdown file, React component, or route name.

Check nested deployment paths

Review the full deployed path after url and baseUrl are configured for the hosting location.

Inspect responsive layouts

Collect feedback at desktop, tablet, and mobile viewport sizes with that viewport kept in the report.

Capture browser context

Keep the page URL, screenshot, browser, operating system, and viewport with every website comment.

Verify static assets

Check the deployed asset URLs after files from the static directory have been copied to the root of the build output.

Keep hosting separate from review

Use the browser URL supplied by the chosen host without treating any one hosting provider as required by Docusaurus.

Which Docusaurus URL should I review?

BugSmash needs the deployed result to be reachable in the reviewer's browser. Source files and local-only addresses are not external review surfaces.

Your URL	Review by URL	What to do
Public Docusaurus site on a custom domain	Works	Paste the deployed documentation URL and start the review.
Public deployment supplied by a static host	Works	Use the host's browser-accessible URL after confirming the intended revision is deployed.
Docusaurus site below a base path	Works	Use the full deployed path and confirm url and baseUrl match that location.
Site protected by supported Basic Auth	Works	Use the browser-accessible Basic Auth URL; BugSmash lists Basic Auth-protected websites as supported.
Site behind application login or SSO	Use the Widget	Pasting a URL does not bypass application login or SSO. If the script can be installed on the rendered site, use the Feedback Widget inside the authenticated browser session.
Local docusaurus serve address	Not directly	Deploy the build directory to an accessible host before creating the external review.

Using the Feedback Widget on a gated Docusaurus site

Where the rendered site permits the BugSmash script to be installed, use it when authorized reviewers need to comment inside an authenticated or stateful frontend. Their existing access still controls which pages they can open.