We've decided to make less money: We've slashed our pricing for session replay. They're now more than 50% cheaper for most customers.

How PostHog.com works

Last updated:

|Edit this page

PostHog.com is built and maintained in-house by the Website & Docs team.

GatsbyStatic site framework
GitHubSource code repository
Ashby (API)Applicant tracking system
Algolia (API)Site search
StrapiHeadless CMS
PostHogAnalytics, feature flags

Diagram of PostHog.com

Website content is stored in two places:

  1. Markdown/MDX files (in the GitHub repo) - most website content
    • Docs, handbook, most pages
  2. Strapi - user-generated content
    • Community forum posts, community profiles


Was this page useful?

Next article

MDX setup

What better way to document MDX than with MDX? Rationale There were a few moving parts involved with setting up MDX so it might make sense to have them written down. What's MDX? Not in scope here - but it's essentially React in Markdown. How do we make it work? Page creation Website pages are automatically created for all MD and MDX files using Gatsby's createPages API. Slugs are automatically generated based on the file title, and the design template for each page is determined based on the…

Read next article