Two Faces of One Person
Every developer has two professional faces: their personal site and their GitHub. The site shows the polished story — clean design, tidy descriptions, images. GitHub shows the raw truth — the code, the commits, the structure. Trouble starts when the two tell different stories.
When I reviewed my work, I found projects on my site with no link to the code, and repos on GitHub a visitor wouldn't know were tied to my site. Anyone looking to hire me had to guess the connection.
Two-Way Linking
The fix is simple in concept: every project should point to the other. On each project page on the site, I added a "Code" button opening the repo directly. And in each GitHub repo, I added the site URL in the Website field pointing to the detailed project page.
That way, whatever the entry point — a Google search, a LinkedIn share, or a direct link — the visitor reaches the full picture: the polished explanation and the real code together.
The Details That Make the Difference
While linking, I caught an important detail: one of my site projects linked to a repo I'd previously archived. A dead link leading to an "Archived" page. I fixed it to point to the active version. This kind of auditing is what separates a professional portfolio from a random collection.
The Takeaway
Consistency isn't decoration — it's credibility. When your site matches your account and each points to the other, you give one clear impression: this is an organized person who cares about detail. And in a world where a recruiter spends seconds per candidate, that first impression may be all you get.