Growth idea action plan
Markdown file links for version-safe docs navigation
Link docs to each other with file-path references instead of hand-typed relative URLs so route changes do not quietly rot the graph.
Why this can grow a startup
Documentation links fail in boring ways. Someone changes a slug, moves a file, or updates a trailing-slash rule, and the help center still looks fine until users hit the stale path. Docusaurus recommends linking docs by relative file paths with `.md` extensions because those links survive file moves, respect per-version routing, and are far less likely to break when route settings change. The gain is partly technical, but it is mostly operational. Editors can rename or reorganize pages without turning the internal link graph into a scavenger hunt.
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. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. 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 markdown file links for version-safe docs navigation can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Documentation and SEO 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 says file-path links keep working across editors, follow the exact same version in versioned docs, and are less likely to break when the `trailingSlash` config changes.
Source: Docusaurus Docs: Markdown links (docusaurus.io)
GrowthDex source hub: Docusaurus Docs: Markdown links
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.
- Fail docs build on broken links before release 2 shared channels · 2 shared stages
- Regex redirect families before docs group migration 2 shared channels · 2 shared stages
- Promoted help articles for homepage first-click routing 2 shared channels · 1 shared stage
- Preview docs noindex before cutover 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