Cleanup posthog implementation

[oredavids]

Summary by CodeRabbit

• Chores
  • Removed Posthog analytics tracking from the site.
  • Stopped loading the Posthog plugin and related configuration.
  • Removed Posthog-related environment variables from configuration and build scripts.
  • Deleted the Posthog dependency from the project.
  • No changes to Google Analytics; it remains active.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Oct 6, 2025 8:34pm

[coderabbitai]

Walkthrough

Removed Posthog analytics across configuration, documentation site config, dependencies, and deployment script. Specifically: deleted Posthog env var mappings, Docusaurus Posthog plugin/config, the posthog-docusaurus dependency, and the build-time export of CONFIG_POSTHOG_API_KEY. Other analytics (e.g., Google Analytics) and build/deploy commands remain unchanged.

Changes

Cohort / File(s)	Summary
Config: Remove Posthog env overrides config/custom-environment-variables.yaml	Deleted Posthog block, including posthog.apiKey and posthog.appUrl mappings.
Docs site: Remove Posthog integration docusaurus.config.js	Removed Posthog plugin usage and related flags/config; stopped injecting Posthog metadata. Google Analytics left intact.
Dependencies: Cleanup package.json	Removed posthog-docusaurus from dependencies.
Build/Deploy script: Env var removal scripts/push-to-s3-prod.sh	Removed export of CONFIG_POSTHOG_API_KEY before build; rest of flow unchanged.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Dev as Developer
  participant Script as push-to-s3-prod.sh
  participant Build as Docusaurus Build
  participant Plugins as Docusaurus Plugins
  participant S3 as S3 Bucket

  Dev->>Script: Run deploy script
  Note over Script: Posthog env export removed
  Script->>Build: yarn build
  Build->>Plugins: Load configured plugins\n(Posthog removed)
  Plugins-->>Build: Initialize remaining analytics (e.g., GA)
  Build-->>Script: Static site artifacts
  Script->>S3: aws s3 sync
  S3-->>Dev: Site deployed

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

Posthog packed its tiny bags, waved bye with a log,

The configs cleared, no more analytics fog.

Docusaurus hums, a lighter tune today,

Scripts march on—straight, no extra sway.

Dependencies trimmed—snip, snip, hooray!

Clean paths ahead; ship it on its way.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title “Cleanup posthog implementation” clearly and concisely summarizes the primary change, which is the removal of the Posthog analytics integration across configuration, dependencies, and deployment scripts, making it easy for reviewers to understand the main purpose of the pull request.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch cleanup-posthog

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 138b271 and 917729f.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (4)

• config/custom-environment-variables.yaml (0 hunks)
• docusaurus.config.js (0 hunks)
• package.json (0 hunks)
• scripts/push-to-s3-prod.sh (0 hunks)

💤 Files with no reviewable changes (4)

• config/custom-environment-variables.yaml
• docusaurus.config.js
• package.json
• scripts/push-to-s3-prod.sh

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Validate generated content
• GitHub Check: validate_build

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}