I have a strong opinion on this: your GitHub activity is a better signal of your skills than any resume bullet point. Contribution graphs, language breakdowns, the repos you actually maintain versus the ones you abandoned two years ago. It's all there, in public, timestamped.

But almost nobody treats it that way.

The signal is there. The presentation isn't.

Recruiter lands on your GitHub. They see a grid of green squares, a list of pinned repos (last updated 8 months ago), and maybe a README you wrote during a weekend of motivation.

That's not a portfolio. That's raw data without context.

The stuff that actually matters, your most active languages over the last 6 months, which projects got stars from other developers, your contribution consistency, none of that is readable at a glance. GitHub is built for collaboration, not for selling yourself. There's no summary, no narrative, no design. Just facts scattered across tabs.

Developers know this. They just don't fix it.

Because fixing it means building a portfolio site. And building a portfolio site means picking a template, writing copy about yourself (brutal), deploying it, and then manually updating it every time you ship something new.

So it doesn't happen. Or it happens once, gets stale within three months, and becomes a liability instead of an asset.

I tracked this while building getfolio.dev. Of the first 24 users who signed up, 19 had an existing portfolio link somewhere on their socials. I checked a sample of those links. More than half hadn't been touched in over 6 months. Old tech stacks listed, missing recent projects, broken deploy previews.

What if the portfolio just read from GitHub directly?

That was the core idea behind getfolio. Connect your GitHub, and the portfolio assembles itself. Languages weighted by actual usage. Repos sorted by recent activity and stars. Contribution graph pulled in live.

No writing "about me" paragraphs. No dragging boxes around. You can customize later if you want, there's a drag-drop editor and five themes, but the default state is already an accurate snapshot of what you build.

Some real numbers from the first month

I've been tracking activation closely because it's the metric that tells you if the product actually works, not just if people are curious.

That last one is interesting. It suggests the auto-generated content feels close enough to "done" that people move straight to aesthetics. The GitHub data is doing the heavy lifting.

The identity layer GitHub doesn't provide

GitHub gives you the facts. What's missing is the frame around them.

A portfolio built from your GitHub activity becomes a living document. Push a new project, it shows up. Get stars on a repo, the count updates. Switch from JavaScript to Rust over six months, your language breakdown shifts.

You stop maintaining a portfolio and start just doing your work. The portfolio maintains itself.

There's also a practical angle for job searches. Custom domains mean you can put yourname.dev on your resume and have it always reflect your current output. Privacy-first analytics let you see who's visiting without creepy tracking. Blog sync from DEV.to or Hashnode means your writing shows up alongside your code.

Who this works best for

Not everyone needs this. If you're a designer-developer who wants a bespoke handcrafted site, go build one. Seriously.

But if you're a developer who writes code every week, has a GitHub profile that tells a real story, and keeps putting off the portfolio because you'd rather ship features than fiddle with a Figma mockup of yourself. This is what getfolio was built for.

The free plan covers everything except custom domains and analytics. Setup takes about 60 seconds if your GitHub is connected.

The uncomfortable question

If someone looked at your GitHub profile right now, today, would it accurately represent your current skill set? And if it does, why isn't that the thing you show recruiters instead of a PDF from last year?

Originally published on getfolio.dev.