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) + clones (usage momentum)
| Repository | Stars | Forks | Clones 14d | Views 14d | Issues |
|---|---|---|---|---|---|
| pantheon-systems/documentation | 207 | 823 | 1,483 | 2,620 | 131 |
| pantheon-systems/quicksilver-examples | 138 | 112 | 74 | 135 | 25 |
| pantheon-systems/push-to-pantheon | 17 | 7 | 69 | 98 | 18 |
| jazzsequence/terminus-skill | 3 | 0 | 15 | 3 | 0 |
| jazzsequence/claude-skill-pantheon-docs-writer | 1 | 0 | 16 | 0 | 0 |
| jazzsequence/pantheon-api-helper | 0 | 0 | 16 | 0 | 0 |
| pantheon-systems/wporg-phpunit-test-runner | 0 | 1 | 506 | 142 | 0 |
| jazzsequence/pantheon-wait-for-build | 0 | 0 | 23 | 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. Clones are the signal to watch — they track real usage momentum, whereas stars are vanity. Forks are cumulative adoption. Traffic metrics (clones/views) are 14-day windows from GitHub and accumulate per collector run.