Hide unreleased docs until the version is real
Keep the work-in-progress docs version out of the public site when the release is not ready for customer traffic yet.
Why this can grow a startup
A lot of docs teams publish the next version too early because the draft exists and the versioning system makes it easy to expose. The result is a help center that quietly teaches buyers, customers, and answer engines about features that are not actually shippable. Docusaurus calls this out directly: if the current version is still a work in progress, do not include it in the public docs set. That restraint keeps launch promises cleaner, reduces support confusion, and stops AI or search citations from drifting onto a page the team still plans to rewrite.
Company example
Docusaurus recommends turning off `includeCurrentVersion` when the current docs version is a work in progress and not ready to be published.
Source and metric
Source: Docusaurus Docs: Versioning
Docusaurus explicitly suggests disabling `includeCurrentVersion` if the current version is a work in progress.
Source discovered: May 29, 2026
When to use it
Use this when Documentation, Product, Support is relevant to launch hygiene, docs strategy, support deflection and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Docusaurus Docs: Versioning and identify what is directly supported.
- Choose one channel context: Documentation, Product, Support.
- Define the test around Docusaurus explicitly suggests disabling `includeCurrentVersion` if the current version is a work in progress..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.