Pakkit.net
← All services

/services / web

Static Site / Portfolio Build

Fast personal sites for builders, consultants, and weird technical people who need more than a resume page.

Built like this one: static-first Astro + TypeScript, owned by you, and boring to maintain in the best way.

Who this is for

More than a resume page

This is for people whose work deserves a real home base — not a slow template they're afraid to edit.

  • Engineers and technical founders who've outgrown a single resume page and want a real home base.
  • Consultants and independents who need credibility, a clear story, and a contact path that works.
  • Creators and weird-technical people who want a site they own — not a rented profile on someone else's platform.
  • Anyone tired of a slow, plugin-stuffed WordPress stack they're a little scared to touch.

What I help with

From architecture to deploy

The whole site as one system — how it's structured, how content flows in, and how it stays fast and yours over time.

Information architecture

Mapping what you actually do into a structure people can navigate in seconds — not a maze of clever menus nobody reads.

Content model

A typed content system using Astro content collections, so adding a project or post is filling in fields — not fighting a page builder.

Project / case-study pages

A repeatable structure for showing work: the problem, what you built, and what it proves — the same shape powering this site.

SEO foundations

The boring-but-right basics: clean titles and metadata, a sitemap, semantic markup, and fast pages that search engines actually like.

Deployment

Low-maintenance static hosting that deploys on push and costs almost nothing to run — no servers to patch at 2am.

Performance

Static-first by default: ship HTML and minimal JS so the site is quick even on a phone on bad hotel wifi.

Contact paths

Clear, working ways for the right people to reach you — without leaking your inbox to every bot on the internet.

Maintainability

A codebase you (or a future helper) can actually edit: typed, documented, and boring in the good way.

Example deliverables

What you walk away with

Concrete artifacts, not a vague 'we built a website' — everything you need to run and grow the site yourself.

  • A fast static site (Astro + TypeScript) deployed and live on your own domain.
  • A typed content model for projects, case studies, and a blog — ready to extend yourself.
  • Project / case-study pages with a consistent, reusable structure.
  • SEO foundations: metadata, sitemap, semantic markup, and social cards.
  • A documented repo and deploy pipeline, so future updates are a git push.
  • A short handoff doc so you're never locked out of your own site.

Why it's different

Not a generic agency build

Closer to how the work on the projects page gets made than to a templated agency package.

You can see the same approach in the projects here — and this very site is the reference build.

Static architecture, not a CMS to babysit

Fewer moving parts means fewer things to patch, break, or get hacked. The site is files, not a fragile stack of plugins.

You own the code and the content

No proprietary page builder, no monthly rent just to edit a sentence. It's your repo, your domain, your call.

Built by an engineer

Same systems mindset as the rest of the work here — clean structure, typed data, and decisions you can actually reason about.

AI-assisted, human-reviewed

AI speeds up scaffolding and first drafts; a human makes the architecture, copy, and security calls. Nothing ships unsupervised.

Performance and security are defaults

Fast pages and sane trust boundaries are how it's built from the start — not upsells bolted on at the end.

Engagement shape

How a build usually goes

Small, reviewable steps with something live early — no month-long silence, no big-bang reveal.

  1. 01

    Scope the site

    We map your sections, content types, and the one action you most want a visitor to take.

  2. 02

    Build the spine

    Layout, content model, and the core pages — typed and deployed early, so you can see it live instead of in a mockup.

  3. 03

    Fill and refine

    Real content, project pages, an SEO pass, and performance tuning — in small, reviewable steps.

  4. 04

    Hand off

    You get the repo, the deploy pipeline, and the docs to run it yourself. No black box, no lock-in.

More on the thinking behind it lives in the blog, and reusable starting points are in resources.

Want a site that's fast, clean, and yours?

Tell me what you're building and who needs to find it. We'll scope a first version that actually ships — and that you can run without me.

Looking for the creator/small-business version of this? For DJs, artists, makers, and simple business sites, start with the Web Development intake — that path also covers the selective free-site opportunity when it's a good fit. Or explore the Web Development section first.