Growth idea action plan
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.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where hide unreleased docs until the version is real can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Documentation and Product channel.
- Use the evidence from docusaurus.io to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
Docusaurus recommends turning off `includeCurrentVersion` when the current docs version is a work in progress and not ready to be published.
Source: Docusaurus Docs: Versioning (docusaurus.io)
GrowthDex source hub: Docusaurus Docs: Versioning
Last checked: 2026-05-29
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Help center setup mode before public activation 2 shared channels · 1 shared stage
- Multi-level help-center collections with breadcrumbs 3 shared channels
- Explicit answer pages to improve GitBook AI search 1 shared channel · 2 shared stages
- Status embed on help center and app shell 2 shared channels · 1 shared stage
Related GrowthDex essays
- The docs route should feel boring even when the product is moving docs strategy, technical seo, support-led growth
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory