Self-initiated · Engineering Portfolio System
A portfolio template that earns its pixels.
We got tired of seeing engineers ship the same generic portfolio template, then watch it convert badly because it tried to be a marketing site. So we built our own. Static HTML, type-driven, no client-side JavaScript, ships in days. The team uses it for their own sites. We stand it up for clients on request.
Principles
Four constraints we stuck to.
Sub-100ms TTFB
Pre-rendered HTML on the edge. No client-side framework boot, no waterfalls. The browser starts painting before most sites have even fetched their JS bundle.
Type-driven hierarchy
Three font sizes, two weights, one accent color. Every page works as a wireframe first. If the type structure doesn't carry the page, more decoration won't save it.
Dev-first authoring
Content lives in the repo. Markdown for prose, frontmatter for structure, no CMS round-trip. Engineers ship updates in the same PR as their code changes.
Static by default
No server runtime. No edge functions. Deploys to any static host in under 30 seconds. The whole site is portable as a tarball.
The page, in five blocks
Every section earns its place.
Positioning hero
One sentence on what you build. One on who you do it for. Nothing else above the fold.
Service areas
Four to six surfaces of expertise, each with two to three keywords. No icons, no fluff.
Selected work
Real projects with the problem, the constraint, the choice that mattered, and the outcome. No screenshots required.
Process & writing
Three-step methodology and a long-form blog. Both signal that the engineer thinks before they type.
Quiet credentials
Footer-level only. Social, email, copyright. The work above the footer should have already done the persuasion.
See it running
fahad.fivitech.com
A live deployment of the system. Inspect the source — there is no source. Just the page.
Open in new tabWhat it runs on
Boring stack on purpose.
- Static HTML output (no React on the client)
- Markdown content with frontmatter
- Edge-deployed (Vercel / Cloudflare Pages / S3 / anywhere)
- Optional: Sanity / Notion / Airtable for the writing section
- Type system: Inter / Geist for body, ui-monospace for accents
- Dark-mode-first; light-mode optional
Built for
Senior engineers who hate building their own portfolio.
Three to five days from brief to live, including content workshop, design review, and deployment. You get the source repo, the deploy pipeline, and a markdown authoring flow. After launch you ship updates in the same PR-and-deploy loop you already use for your day job.
Talk to us about one