Customer Zero & Product Adoption
Being customer zero — actively using Pantheon tools and features before our customers do.
A primary role of Developer Relations is being Customer Zero — so we can guide customers 1–10 and let engineering worry about customers 10–∞. To do that we need to be actively using the tools and Pantheon features our customers will use, before they use them: Cloudflare GCDN, ElasticPress, Next.js, the GitHub App/Action, and the Pantheon API.
Repositories
Adoption from GitHub — forks (cumulative) + unique cloners (usage momentum)
| Repository | Stars | Forks | Clones 14d | Views 14d | Issues |
|---|---|---|---|---|---|
| pantheon-systems/documentation | 207 | 825 | 3,151 | 2,300 | 130 |
| pantheon-systems/quicksilver-examples | 138 | 113 | 72 | 62 | 25 |
| pantheon-systems/push-to-pantheon | 18 | 7 | 154 | 288 | 13 |
| jazzsequence/terminus-skill | 3 | 0 | 8 | 4 | 0 |
| jazzsequence/claude-skill-pantheon-docs-writer | 2 | 0 | 11 | 2 | 0 |
| jazzsequence/pantheon-api-helper | 0 | 0 | 5 | 0 | 0 |
| pantheon-systems/wporg-phpunit-test-runner | 0 | 1 | 682 | 7 | 0 |
| jazzsequence/pantheon-wait-for-build | 0 | 0 | 9 | 0 | 0 |
| pantheon-systems-ps/wp2shell-version-audit | 0 | 0 | — | — | 0 |
Stars & forks are cumulative (2026 to date, from the backfill). Open issues, clones & views (14-day) are point-in-time per collector run and accumulate weekly.
These are the Pantheon-facing tools we build and dogfood. Unique cloners are the signal to watch — clone counts include CI and scanners, so the clones-per-cloner ratio tells you whether you're looking at people or machines. Forks are cumulative adoption, stars are vanity. Traffic metrics (clones/views) are 14-day windows from GitHub and accumulate per collector run.