Two weeks ago, I decided to run an experiment: what happens if you treat GitHub like a content platform and publish aggressively?
I created 211 repositories in 13 days. Templates, tools, awesome-lists, API wrappers, tutorials, starter kits.
Here are the raw numbers and what I learned.
The Numbers
- 211 repos created (16+ per day average)
- Languages: Python (40%), JavaScript (30%), Misc/docs (30%)
- Types: Awesome lists (25), API wrappers (35), Templates (40), Tools (50), Tutorials (30), Starter kits (31)
- Stars: 0 (yes, zero — I'll explain why this is fine)
- Forks: 2 (both on scraping tools)
- Profile views: Increased 5x
What Actually Happened
Week 1: The Spray-and-Pray Phase
I created everything I could think of. Python templates, Node.js boilerplates, Docker starter kits, API wrappers for every free API I could find. 100 repos in 6 days.
Result: Basically nothing. GitHub doesn't reward volume. Zero stars.
Week 2: The Pattern-Recognition Phase
I noticed something: the repos with README files that told a story got more clicks. "SEC EDGAR API: How I Built a Free Stock Research Tool" got 10x more views than "python-sec-edgar-client."
So I shifted strategy. Every repo became a mini-tutorial with:
- A problem statement ("I was paying $50/month for this...")
- Working code you could copy-paste
- A comparison table (free vs paid alternatives)
- Cross-links to related repos
Result: Page views doubled. 2 forks appeared.
5 Things I Learned
1. GitHub SEO is real (and nobody talks about it)
Your repo description shows up in Google. "awesome-government-apis" now ranks for "free government APIs python." That's passive traffic that compounds.
2. Awesome-lists are the highest-leverage content
My awesome-financial-apis and awesome-government-apis lists took 30 minutes each to create but drive 60% of my GitHub traffic. They're link-bait by nature.
3. README quality matters more than code quality
Harsh truth: nobody reads your code until they've read your README. I spent 70% of my time on READMEs and 30% on code. Worth it.
4. Cross-linking creates a flywheel
Every repo links to 3-5 other repos. Every awesome-list links to my tools. Every tool README links to tutorials. Google sees all these internal links and starts ranking things higher.
5. Stars don't matter (at this stage)
Zero stars sounds bad, but:
- 211 repos = 211 searchable pages on GitHub and Google
- Each repo is a landing page for a specific keyword
- 2 people forked my scraping tools (signal of real demand)
- GitHub activity graph is solid green
The Actual Strategy
I'm not doing this for GitHub clout. Each repo serves a purpose in a funnel:
GitHub Repo (SEO) → README with CTA → Dev.to article (backlink) → Portfolio/Hire page
It's content marketing, but for developers, using code as the medium.
Would I Do It Again?
Yes, but I'd change the ratio. Instead of 211 repos at average quality, I'd do:
- 20 awesome-lists (highest leverage)
- 30 high-quality tutorials (API-focused)
- 10 real tools (solve actual problems)
- Skip the rest
60 repos > 211 repos if the quality is right.
What's Next
I'm now focused on the repos that showed signal (forks, views) and doubling down on the financial API niche — that's where developers actually have budget problems.
Has anyone else tried content marketing on GitHub? What worked for you?
I'm building financial tools and API integrations. Find me on GitHub or check my portfolio.
Top comments (0)