Most developer portfolios die in the drafting stage. You pick a template, start customizing, get stuck on copy or layout decisions, and the tab stays open for three weeks before you close it forever.
I wanted to see what actually happens when you remove that friction. So I tracked the numbers from
You pick one, optionally drag sections around, and hit publish. 95% of published portfolios also opted into the Explore directory, which makes them discoverable.
4. (Optional) Custom domain and analytics
Pro tier unlocks custom domains and privacy-first analytics. One person has upgraded so far out of 20 onboarded users. Zero churn. Custom domain usage is still at zero though, which tells me the default getfolio.dev/username URL is good enough for most people at this stage.
What's actually working
The 75% end-to-end activation rate (signup to discoverable portfolio) is high for a tool with no onboarding flow beyond the product itself. I think the reason is simple: connecting GitHub does 80% of the work for you. There's almost no blank-page problem.
The biggest drop happens between signup and GitHub connection (25% drop). Some of those accounts might be people who signed up to look around. Some might come back later. I don't have session replay data, so I'm guessing.
What surprised me
Terminal theme being the second most popular. I built it partly as a novelty, figured maybe one or two people would use it. Five out of nineteen is more than I expected.
Also, nobody picked Minimal. That's the cleanest, most traditional layout. Developers apparently want something with more personality than a white page with Helvetica.
If you want to try the same thing
The whole process:
- Sign up at .↗ Original-Artikel auf dev.to lesenVollständiger Original-BerichtAusführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
SOCIAL SHARE CARD GENERATOR