OSS Story Profile
A personal-site generator that turns your OSS activity into a public, recruiter-shareable profile page — already-formatted case studies, contribution heatmap, and skill tags — so the candidate doesn't have to assemble it by hand.
Self-taught devs and open-source maintainers without a polished portfolio
- Auto-generated case studies from your merged PRs (problem, approach, result)
- Static portfolio site you can deploy to a custom domain in one click
- Skill tag inference plus a 'what I worked on this quarter' digest
- Public profile URL that's recruiter-friendly and lets the user gate private details
The Dev.to article's commenters are exactly the people who'd want a 'set it and forget me' portfolio page instead of hand-crafting one — and the article made the case for why this matters.
Real recurring demand validated by the Dev.to source article framing the pain and by the fact that competitors (GitScoreAI, rahuldkjain's gh-profile-readme-generator) have built audiences around exactly this workflow.GitScoreAI - Analyze Your GitHub Profile, Generate README & Build Portfolio ↗GitHub Profile Readme Generator ↗
Market is crowded with near-identical offerings: GitScoreAI, Gitfolio, gitdevtool.com/profile, rahuldkjain's generator, and dozens of portfolio-website templates already solve the 'OSS activity → public profile' workflow, leaving little differentiated whitespace.GitScoreAI - Analyze Your GitHub Profile, Generate README & Build Portfolio ↗Gitfolio - AI-Powered Developer Portfolio Generator ↗GitHub Profile README Generator - Create Professional Profile | Free AI ↗
GitScoreAI's freemium pricing page confirms a paid model is viable, but most direct competitors (rahuldkjain's generator, Gitfolio) are free, and the target audience of self-taught devs is famously price-sensitive — willingness to pay is mixed.GitScoreAI - Analyze Your GitHub Profile, Generate README & Build Portfolio ↗
Developer self-presentation is evergreen, but GitHub itself could ship native profile/portfolio features (profile READMEs already exist), and the core 'assemble contributions' use case is at risk of being absorbed by the platform.Managing your profile README - GitHub Docs ↗
Highly feasible: GitHub's public REST/GraphQL API exposes contributions, repos, languages, and stats, and rendering a static profile page (e.g., Next.js or Hugo) with those data is a weekend-scale build — no ML or proprietary data required.Managing your profile README - GitHub Docs ↗