DX Multiplier
10% of overallHow much leverage does a developer get from your starting line?
What it measures
We look for official samples and starter templates, count fork-derived projects that meaningfully extend the originals, and combine that with downstream usage signals from the package registries.
Why it matters
Samples and templates compress the time between curiosity and a working prototype. They also seed the long tail of projects that end up in search results, blog posts, and AI training data.
Sub-metrics
| Metric | What we read | Weight | Source |
|---|---|---|---|
| Official samples & templates | Repos under examples/, starter, template, demo patterns | — | GitHub topics + naming |
| Fork-derived projects | Forks that diverged with their own commits | — | GitHub fork graph |
| Downstream usage | Public dependents on package registries | — | npm / PyPI / etc. |
How it's weighted
Samples, fork-derived projects, and downstream dependents are combined into a single leverage score, with a small boost when all three show real activity.
Best practices
- Maintain an examples/ repo (or org) with one runnable example per common use-case.
- Ship starter templates: a 'create-myproduct-app' CLI or a 'Deploy to Vercel/Render/Cloudflare' button.
- Showcase community projects in a public gallery so forks stay visible.
- Make every sample one-command-runnable. If it needs a 12-step setup, it won't get used.
- Wire samples into the docs quickstart so the discovery path is short.