Official docs, website, and handbook for PostHog.
1.1k
Stars
851
Forks
1.3k
Open issues
30
Contributors
AI Analysis
PostHog.com is the official website, documentation, and handbook repository for PostHog, a product analytics platform. It serves as a comprehensive content hub containing product docs, blog posts, case studies, tutorials, and internal handbook—designed for both end users seeking product information and internal team coordination. This repository is primarily valuable for PostHog users, contributors, and those interested in how a successful open-source company structures its public-facing cont...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
PostHog's official website, docs, and handbook repository—maintained as a product for community contribution and self-service discovery
posthog.com is the public-facing website, comprehensive documentation, blog, tutorials, and internal handbook for PostHog, the open-source product analytics platform. It is built with Gatsby and TypeScript and functions as a centralized hub for users seeking product guidance, API references, case studies, and hiring information. Adoption is implicit in PostHog's user base (35k+ stars on the main PostHog repo) rather than direct; the site itself is maintained actively by PostHog's engineering team and community contributors, with regular updates tied to product releases and content strategy.
Created in May 2020 alongside PostHog's public launch, posthog.com evolved from a simple marketing site into a comprehensive knowledge base and community hub. It now mirrors how mature open-source companies (Hugo, TypeScript, etc.) treat documentation as a product requiring versioning, testing, and quality gates.
Growth has been steady rather than explosive—1,068 stars, 838 forks as of June 2026. The repository gains ~18 stars per week, reflecting that it is primarily a content and infrastructure asset rather than a standalone tool. Activity is driven by product releases, documentation expansions, and community contribution workflows. The site integrates features like Squeak (Q&A), Ashby (jobs), pricing calculators, and API documentation, suggesting it serves strategic business functions beyond documentation.
This is a production website—posthog.com receives traffic from all PostHog users, prospects, and the open-source community seeking product docs and API references. Real-world adoption is verified via the site's role as the canonical documentation source for a mature open-source platform. However, adoption of the *repository itself* for contributions appears modest: 838 forks, monthly contributor badges, and a 'PRs welcome' posture suggest community engagement is present but not massive.
Likely a Gatsby-based SSG (static site generation) with TypeScript components. README indicates GraphQL data layer, templating systems, and integration with external services (Shopify for merch, Ashby for jobs, Squeak for Q&A). Build pipeline includes Cloudflare Pages for PR previews and Vercel for production. Architecture appears modular, supporting docs, blog, handbook, and e-commerce sections within one codebase.
Not documented in README. No reference to testing frameworks, CI pipelines for tests, or coverage metrics. Build errors and debugging instructions focus on dependency management and caching issues rather than test failures.
Last push: 2026-06-30 15:53:09 (same date as evaluation). Repository is actively maintained. README references recent tooling (Node 22, pnpm@latest-10). Regular commit activity implied by mention of GitHub closed PRs and monthly commit badges. Deployment to Vercel and Cloudflare suggests continuous integration. No signs of abandonment; appears to follow a scheduled maintenance cadence tied to product releases.
ADOPT IF: you are a PostHog user seeking product documentation, API references, tutorials, or community Q&A—this is the canonical resource and is well-maintained. You are an open-source contributor wanting to improve PostHog's documentation or handbook—the repository welcomes contributions with clear processes. AVOID IF: you are looking for a reusable documentation framework or Gatsby template to apply to your own project; this is PostHog-specific and tightly coupled to its ecosystem. You need real-time support or bug fixes; this repo is for docs and marketing, not the product itself (report product bugs in PostHog/posthog). MONITOR IF: you contribute to PostHog.com regularly—watch for breaking changes in Gatsby, Node version requirements, or build processes; the README is detailed but environment-specific issues (Apple Silicon, Flox environments, env var misconfigurations) are common pain points.
Independent dimensions
Mainstream potential
2/10
Technical importance
4/10
Adoption evidence
7/10
- Tight coupling to Gatsby and TypeScript ecosystem versions (Node 22, pnpm@latest-10, specific Vips library for Apple Silicon). Build failures can occur with version drift; README documents workarounds but suggests frequent environmental issues.
- Preview deployments (Cloudflare Pages) use GATSBY_MINIMAL=true, which disables post listing generation, creating a gap between PR preview and production reality. This may lead to merged documentation with broken links on listing pages.
- External service dependencies (Ashby, Shopify, Squeak, GitHub API) require environment variables and API keys, creating friction for local development and reproducibility. Not all keys are public; private instructions are in a separate repo.
- Adoption of contributions may be bottlenecked by PostHog's internal review process. The README notes a style guide and cites AGENTS.md for fundamental setup, but no explicit SLA for PR merges or contributor responsiveness is documented.
- Search and listing pages are regenerated only on master merge, not in PR previews, creating potential for stale or inconsistent content discovery during review cycles.
PostHog.com will likely continue as a well-maintained, steady asset tied to PostHog's product roadmap. Growth will remain incremental unless PostHog itself undergoes major adoption surges. The site will consolidate features (Q&A, jobs, handbook, API docs) into a single platform and may eventually become a reference for how SaaS companies structure documentation. Unlikely to become an independent tool or framework; remains a PostHog-specific asset.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://posthog.com
- Language
- TypeScript
- License
- NOASSERTION
- Last updated
- 11h ago
- Created
- 75mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
No open issues — clean slate.
Top contributors
Recent releases
No releases published yet.
Similar repos
microsoft/TypeScript-Website
This is the official TypeScript language learning website and infrastructure,...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
PostHog/posthog.com
this
|
1.1k | +16 | TypeScript | 7/10 | 11h ago |
|
PostHog/posthog
|
35.4k | — | Python | 8/10 | 10h ago |
|
microsoft/TypeScript-Website
|
2.5k | — | TypeScript | 8/10 | 12h ago |
 pgsty/pigsty
|
5.2k | — | Shell | 8/10 | 21h ago |
 gohugoio/hugo
|
88.9k | — | Go | 9/10 | 1d ago |
|
gohugoio/hugoDocs
|
1.2k | — | HTML | 7/10 | 3w ago |
Similar scale (1,155 stars) and similar use case (official docs for a popular open-source tool). Hugo Docs uses HTML rather than Gatsby/TypeScript, reflecting a different content strategy. PostHog.com is more feature-rich (Q&A, merch, jobs integration) and targets a SaaS product, not a CLI tool.
Larger (2,535 stars), also TypeScript-based. Serves a larger and more established ecosystem. PostHog.com appears more oriented toward business functions (hiring, case studies, handbook) alongside technical docs; TypeScript's site is more narrowly focused on language documentation.
Hugo is the main project (88k stars); its docs repo is ancillary. PostHog.com, by contrast, is tightly coupled to PostHog's core repo (35k stars), indicating docs-as-product maturity but not independence.
Smaller ecosystem (5,197 stars), but similar TypeScript/docs infrastructure philosophy. PostHog.com is more actively maintained and has deeper integration with business functions.
PostHog.com is a mature, well-resourced example of this pattern. Likely outperforms average Gatsby-based docs sites in feature completeness and team backing, but is not unique in technology choice or approach.
