Every developer portfolio I have made was accurate for about a month. After
that it showed what I had built last spring, and the projects I was actually
proud of lived only on GitHub. I'm a data engineer, and data that has to be
copied by hand into a second place goes stale. So I stopped copying it.
Forkfolio treats your GitHub account as
the source of truth. You sign in once, and it builds a portfolio from your
public repos, then keeps rebuilding it. Here is how that works and what
broke along the way.
Two ways a portfolio finds out you shipped something
There's a nightly job (a Vercel cron at 04:17 UTC) that re-reads every
user's public work: repos, pinned projects, languages, stars and the
contribution calendar. That alone keeps a page at most a day behind.
Pushes are faster. A GitHub webhook hits an endpoint that checks the HMAC
signature, answers 202 straight away and does the sync after the
response.…