Hand-coding it
The most flexible option and the best learning project. The catch is survivorship: most hand-built portfolios ship once, then go stale because updating them is friction nobody budgets for. Worth it if the portfolio isthe demo (you're a front-end or design engineer). Otherwise it's a lot of yak-shaving to restate what your GitHub already proves.
Site builders & link-in-bio
Fast to stand up, but you still write all the content, and a link-in-bio page is a list of links — it carries no evidence of what you actually built. Fine as a hub, weak as a portfolio for an engineering hire.
Resume builders
Great for the document you attach to an application. But a resume is self-reported and episodic — you rebuild it every job hunt. It isn't a living, linkable artifact.
Where gitshow fits
gitshow is the right tool when your GitHub history already contains the proof and you don't want to spend a weekend restating it. It reads your repos, commits, PRs, and source, drafts the write-ups, and publishes — and on Pro it refreshes from GitHub so it never goes stale, the failure mode of every other option here. It is not the right tool if you want a fully bespoke, pixel-controlled site — hand-code that.
See real portfolio examples or read how the generator works. Publishing is free.