30-Day Launch Scorecard
Use this scorecard to measure whether public launch activity creates real developer value and repository growth.
Do not optimize for impressions alone. The primary signals are qualified handbook traffic, GitHub actions, and contributor participation.
The operational snapshot for this launch is recorded in Launch Day Execution — 2026-08-09.
Baseline
Day-0 repository/community values were captured on 2026-08-09 against launch commit 0bb1fc1fb5b08b9531fc4f0e35944d46e369f111.
| Metric | Baseline | Day 7 | Day 14 | Day 30 |
|---|---|---|---|---|
| GitHub stars | 0 | |||
| GitHub forks | 0 | |||
| Open issues | 13 curated issues | |||
Open good first issue items |
6 | |||
Open help wanted items |
7 | |||
| Contributors returned by GitHub contributors API | 2 | |||
| First-time contributor PRs | 0 for launch window | |||
| Merged community PRs | 0 for launch window | |||
| GitHub Pages visits | No Day-0 analytics value captured yet | |||
| Repository click-throughs | 0 launch-attributed results recorded yet | |||
| Search clicks | No fresh Day-0 Search Console snapshot captured yet | |||
| Search impressions | No fresh Day-0 Search Console snapshot captured yet | |||
| Referring domains/backlinks | No Day-0 launch snapshot captured yet |
Repository stars, forks, contributor count, metadata, topics, and release state were captured from the GitHub REST API by a GitHub-hosted Actions runner. Do not substitute older growth-review values for analytics that were not captured on Day 0.
Flagship Page Scorecard
Record traffic and downstream repository actions by page where analytics support it.
| Page | Visits | GitHub clicks | Shares/backlinks | Notes |
|---|---|---|---|---|
| Comparison Matrix | ||||
| Claude Code | ||||
| OpenAI Codex | ||||
| Cursor | ||||
| GitHub Copilot | ||||
| Gemini CLI | ||||
| AGENTS.md | ||||
| MCP Overview | ||||
| Prompt Library |
Channel Scorecard
| Channel | Asset/angle | Visits | GitHub clicks | Stars/forks attributable | Contributions | Keep / change / stop |
|---|---|---|---|---|---|---|
| X / short-form | ||||||
| Hacker News | ||||||
| Dev.to / Hashnode | ||||||
| GitHub Discussions | ||||||
| Organic search | ||||||
| Referrals/backlinks |
Recommended 30-Day Targets
Treat these as experiment targets, not promises.
Minimum successful launch
- at least 3 distribution channels produce qualified traffic
- at least 2 flagship pages show repeatable interest
- at least 1 first-time external contribution or substantive issue interaction
- the issue backlog remains curated rather than growing through placeholders
- at least 1 meaningful backlink, community mention, or search-query signal emerges
Strong launch
A strong outcome would additionally show:
- clear week-over-week star/fork growth
- one flagship page becoming the dominant discovery asset
- multiple first-time contributor interactions
- organic search impressions increasing on tool/comparison queries
- a repeatable distribution channel that can be used without spam
Do not set an arbitrary star count as the sole definition of success.
Conversion Ratios
Where the data is available, calculate:
Page to repository
repository click-through rate = GitHub clicks / flagship page visits
Repository to star
star conversion = new stars / repository visitors
If repository visitor counts are unavailable, use UTM click counts as a directional denominator and label the limitation.
Contributor conversion
contributor conversion = first-time contributor PRs / good-first-issue visitors
Only use this if issue-link analytics are available. Otherwise track first-time PRs as a raw count.
Weekly Review Questions
Every seven days answer:
- Which page generated the strongest qualified traffic?
- Which channel generated the strongest GitHub click-through?
- Which content angle produced useful technical discussion?
- Did any starter issue attract an external contributor?
- Are new visitors landing on deep pages or only the homepage?
- Which search queries are appearing or growing?
- Which activity created impressions but no downstream action?
- What should be doubled down on next week?
Attribution Rules
- Use UTMs for external campaign links where possible.
- Do not add UTMs to canonical internal handbook links.
- Do not claim a star/fork was caused by a channel when attribution is unclear.
- Separate organic search from social/community referrals.
- Keep screenshots or exported summaries when platform analytics are ephemeral.
Data Sources
Preferred sources:
- GitHub repository Insights
- GitHub issue/PR/contributor history
- GitHub Pages analytics if configured
- Google Search Console
- platform-native social analytics
- sanitized growth-review inputs already supported by the repository
Day 30 Retrospective Template
Launch window: 2026-08-09 to 2026-09-08
Biggest win:
Strongest page:
Strongest channel:
Stars/forks change:
Contributor change:
Search/backlink signal:
What we should stop:
What we should repeat:
Next three content priorities:
1.
2.
3.