PostHog / posthog.com
Official docs, website, and handbook for PostHog.
AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing PostHog/posthog.com in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Repository Overview (README excerpt)
Crawler viewPostHog.com - Website, docs, blog, and handbook Support - Roadmap - Open an issue - Style guide This is the repository for the PostHog website. We treat it like a product. It contains: • All of our written content and visuals including product features, manuals, docs, blogs, case studies, tutorials, and the handbook • Features like questions and answers (using Squeak!), job listings (using Ashby), pricing calculator, roadmap, API docs, and more • All the components, templates, logic, and styling to make this work, look pretty, and spark joy Table of contents • Quick start • Advanced setup • Contributing Quick start > is equipped with instructions for the most fundamental parts of running the app. > > If you find places where current documentation is lacking, email cory@posthog.com with the subject, "AGENTS.md". • **Pre-installation** Install Node (version 22) - if you installed Node using nvm, you can run to automatically switch to the correct version. Install . The easiest way to do this is via . • **Start developing** Clone the repo and navigate into your new site’s directory: If you're using an Apple Silicon Mac (M1 or later) you'll need to run the following commands: Then install the site dependencies, and start it up: > **Tip:** Seeing a discrepancy between local development and staging/production? Preview the production build locally by running • **Open the source code and start editing!** Your site is now running at ! > **Note:** You'll also see a second link: . This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby tutorial. See full instructions on developing PostHog.com locally in our manual. Advanced setup Debugging errors on start • Pull the latest changes from • Run or delete and • Make sure you're not in an activated flox environment for a different project • Check builds are passing in deployment to Vercel Working on ? The site will load the API schema from US Cloud by default. You can override this to use your local PostHog instance with an env var: Want Ashby job listings or GitHub contributors to load? You’ll need to set environment variables for these. See (private) instructions for this. Developing the posts section To see your local version of the posts section, needs to be visited directly ( ) Developing the merch store Additional environment variables are needed to develop the merch store: • • • Currently, these environment variables are excluded from Vercel preview builds to disable merch store node creation and speed up build times on non-merch related PRs. Dynamic open graph images To develop a dynamic open graph image: • Run with both the and set. • In , temporarily comment out the following: • Find the generated open graph image in Contributing We <3 contributions big and small. In priority order (although everything is appreciated) with the most helpful first: • Ask a question in our community • Submit bug reports and give us feedback in the app! • Vote on features or get early access to beta functionality in our roadmap • Open a PR • Read our instructions above on developing PostHog.com locally • Read more detailed instructions in our manual • For basic edits, go to the file in GitHub and click the edit button (pencil icon) • Open an issue or content idea