# External docs PR path for community knowledge growth

> Make docs and website pages easy for outsiders to improve so community fixes become visible product proof and long-tail knowledge assets.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/external-docs-pr-path-for-community-knowledge-growth/
- Source: [newsletter.posthog.com](https://newsletter.posthog.com/p/the-hidden-benefits-of-being-an-open)
- GrowthDex source hub: [PostHog: The hidden benefits of being an open-source startup](/sources/posthog-the-hidden-benefits-of-being-an-open-source-startup-newsletter-p/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Community, Content, SEO
- Stages: docs operations, community-led growth, search footprint, trust proof
- Key metric: PostHog says roughly 10% of pull requests on its website repo come from external contributors.

## Why this can grow

A contribution path widens the knowledge surface without forcing every correction through the core team. When users can improve docs, add examples, or clarify confusing pages, the product gets better and the site gets denser with real language from real users. That helps future prospects, gives search engines more useful material to index, and shows the company can absorb outside input without drama.

## 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

1. Define one narrow startup segment where external docs pr path for community knowledge growth can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Content channel.
3. Use the evidence from newsletter.posthog.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

PostHog says roughly 10% of pull requests on its posthog.com repo come from contributors outside the company, including people who write entirely new docs pages.

## Adjacent tactics in the same lane

- [Public decision log for technical trust](/growth-ideas/public-decision-log-for-technical-trust/) - same source, 2 shared channels
- [Doc category index for community knowledge base](/growth-ideas/doc-category-index-for-community-knowledge-base/) - 3 shared channels, 2 shared stages
- [Open roadmap comments for beta-tester recruiting](/growth-ideas/open-roadmap-comments-for-beta-tester-recruiting/) - same source, 1 shared channel, 1 shared stage
- [Open-source alternative positioning for switcher search](/growth-ideas/open-source-alternative-positioning-for-switcher-search/) - same source, 1 shared channel

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The trust surface should show the work](/blog/the-trust-surface-should-show-the-work/) - brand trust, community-led growth, SEO

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.