/web-development / portfolio

Recent work, and the stuff that's still being built

A showcase of the websites Pakkit builds for creators and small businesses — DJs and performers, an internet provider, a plumbing company, and a couple of personal brands. Every project here is real, and each card says plainly whether the site is live today or still a preview build waiting on a domain.

This portfolio fills in over time. If your project becomes one of these, you'll know exactly what kind of company it's keeping.

Live work

Sites you can visit right now

Finished builds serving real traffic on their own domains. Click through — this is the actual work, not a mockup of it.

DJ Broom

DJ / performer website

Live — first of the showcase

with Mike Broomfield

A clean, practical web presence for a Denver open-format DJ — the kind of simple, fast site that helps people understand the brand, find the right links, and get in touch without digging through a dozen rented profiles.

Goals

Give the brand a clear, professional home of its own.
Help people understand who DJ Broom is at a glance.
Make links and contact easy to find.

In the build

A static, mobile-friendly site that loads fast.
A clear landing page that sets the tone.
A simple path to links and contact.

DJ Performer Static site Creative brand

Visit DJ Broom

Dallas Pubby

DJ / rave host website

Live — custom build on its own domain

A focused creator site for Dallas Pubby, a Denver-based EDM rave host who throws high-energy dance parties at furry conventions. It's a home for show information, a gallery, and the links people go looking for after discovering the brand.

Goals

Introduce Dallas Pubby with a clear, energetic first impression.
Make shows and party details easy to find.
Bring scattered social and contact links into one owned web presence.

In the build

A fast static site with a brand-forward landing page.
Dedicated routes for shows, gallery, and links.
A small API layer alongside the static pages for the parts that need it.
A mobile-friendly structure built around quick discovery.

DJ Rave host Furry events Custom design

Visit Dallas Pubby

Duvall Wi-Fi

Infrastructure / services web presence

Live — the professional, infrastructure side

A web presence for Duvall Wi-Fi, representing the professional, infrastructure side of the work — networking, security, and the reliable systems thinking that sits behind connectivity and technology services. It gives the project a public home where visitors can understand the offerings and find a way to get in touch.

Goals

Give the project a clear, professional home of its own.
Help visitors understand the networking and technology services on offer.
Make service information and contact easy to find.

In the build

A web presence that introduces the work and its focus.
A clear structure for navigating services and information.
A straightforward path to contact.

Networking Infrastructure Security Web presence

Visit Duvall Wi-Fi

Pakkit.net

Personal / professional site

Live — the site you're reading

with Brandon Donaly

The site you're on right now, and the most honest sample available: a large static site with a long-running blog, project write-ups, service pages, and this portfolio — built, checked, and deployed exactly the way client work is. If you want to know what the build quality looks like, you're already looking at it.

Goals

Show the work in public rather than describing it in the abstract.
Keep a long-form blog and project archive that stays fast as it grows.
Give every service and project its own findable, well-structured page.

In the build

A static build with 60+ routes and a blog well past 250 posts, still served as plain pages.
Structured data on every page so search engines and link previews read it correctly.
Content kept in typed data files so pages stay consistent as they're edited.
An automated publishing pipeline that builds and deploys on every change.

Static site Blog Structured data Design system

You're already here

In flight

Preview builds

Complete, browsable sites hosted on a Pakkit preview domain while the client reviews them or plans the switch from their old site. Every Pakkit build lives here first, so nothing goes near a real domain until it's been seen and signed off.

DJ WinterLion

DJ / performer website

Preview build — awaiting a domain

A performer site for DJ WinterLion that centers the artist's mix of Y2K pop, dad rock, convention sets, club nights, and recorded mixes in a clean web presence people can actually navigate.

Goals

Give DJ WinterLion a clear artist home outside rented social profiles.
Make show information, sets, and music links simple to reach.
Present the performer brand in a polished, mobile-friendly format.

In the build

A static performer site with a clear homepage.
A show-focused structure for upcoming and past appearances.
External music and link paths surfaced without clutter.

DJ Performer Convention sets Preview site

Preview DJ WinterLion

EddyFoxNet

Personal site / link hub

Preview build — rebuild of an existing site

A rebuild of an existing hand-written personal site into a proper, maintainable static build: socials, fursonas, photos, an about page, and a Steam profile embed, all in one place instead of scattered across ten rented platforms. The live domain still serves the original site — this preview is what replaces it when Eddy's ready.

Goals

Turn a hand-maintained page into something that's easy to keep current.
Pull ten-plus social profiles into one owned front door.
Keep the personality of the original rather than flattening it into a template.

In the build

A static rebuild with dedicated about, fursonas, and photo routes.
A link hub covering every profile worth surfacing.
A downloadable contact card and a third-party gallery integration.
Content moved into structured files so future edits don't mean editing HTML.

Personal site Link hub Rebuild Preview site

Preview EddyFoxNet

KitsapWiFi

Internet provider / local business site

Preview build — replacing a WordPress site

A static rebuild for a locally owned internet provider in Poulsbo, WA offering fiber and wireless internet, VoIP, server hosting, and computer repair across Kitsap County. The current site runs on WordPress and a caching plugin stack; this build replaces all of that with plain, fast pages that can't break on a plugin update.

Goals

Replace a plugin-dependent WordPress site with something that stays fast on its own.
Make service plans and coverage genuinely easy to compare.
Give a local ISP a site that loads quickly even on the connections it's selling.

In the build

A static rebuild with per-service pages generated from structured content.
A coverage page, an FAQ, and terms of service.
A contact form with proper success and error handling.
No database, no plugins, and no admin login to keep patched.

ISP Local business WordPress replacement Preview site

Preview KitsapWiFi

Pacific Northwest Plumbing

Trade / home services website

Preview build — replacing a hosted site builder

A static rebuild for a family-owned plumbing company serving Auburn, WA — journeyman plumbers, 24/7 service, free onsite estimates. It replaces a rented site-builder page and an older custom web app with one fast site the business actually owns, including per-city service-area pages for the towns they cover.

Goals

Get the business off a rented page builder and onto a site it owns outright.
Make emergency service and free estimates impossible to miss.
Give each service and service area a real page that can be found on its own.

In the build

A static rebuild with generated per-service and per-city routes.
A blog with category and tag archives for ongoing content.
A contact flow built for people calling about an urgent problem.
Structured content files so services and service areas are added by editing data, not markup.

Home services Local SEO Rebuild Preview site

Preview Pacific Northwest Plumbing

The common thread

How every one of these gets built

These sites look different on purpose — a rave host and a plumbing company should not share a design. What they share is the machinery underneath, which is why a small project can get a serious build without a serious budget.

One factory, many sites

Every project is scaffolded from a shared, maintained set of templates and components. A fix or improvement made for one site is available to all of them, so later projects start further along than earlier ones did.

Content lives in data, not markup

Services, shows, plans, and service areas are structured files that generate pages. Adding a new service means adding an entry — not copying a page and hoping every piece of boilerplate got updated.

Built in a container, every time

Builds run inside a locked-down container rather than on whatever happens to be installed on a laptop. The build that gets checked is byte-for-byte the build that gets deployed.

Type and format checks before anything ships

Type checking, linting, formatting, and tests all run as one gate. Broken links to nonexistent pages and malformed content get caught before a human ever sees them.

Preview first, domain second

Every build gets a real, browsable preview URL long before it touches a live domain — that's what the preview builds above are. Nothing is switched over until the client has clicked through the actual thing.

Deployed on push, served from the edge

Sites deploy automatically on every change and are served as static files from a global network. There's no server to patch, no database to back up, and nothing to go down at 2am.

What's in the box

What these projects usually include

Every build is shaped to the project, but most land around the same practical core.

A static site build

A fast, owned website served as plain pages — no fragile stack of plugins waiting to break.

Mobile-friendly layout

Designed for the phone first, since that's where most people will actually find you.

A clear homepage

A landing page that says who you are and what you do in seconds, not after a scavenger hunt.

The sections you need

About, services, portfolio, and contact — added as the project calls for them, not by default.

A basic SEO foundation

Clean titles, metadata, and semantic markup so search engines and link previews behave.

Room to grow later

Analytics and conversion tracking can be added down the line if and when they make sense.

Basic post-launch updates

Small text, image, and link changes can be handled by Pakkit so the site stays current.

Good fit

What Pakkit looks for in a good fit

Selection is case-by-case. These are the things that make a project a natural match.

A simple, clear goal

A creative or small-business idea that fits a clean static site — not a sprawling custom app.

Willing to collaborate

You're up for sharing content and images and giving feedback as the site comes together.

Showable, respectfully

A project that can be featured here as portfolio work in a way you're comfortable with.

Scope that fits a static site

Clear enough that a fast, low-maintenance static build is genuinely the right tool.

Good vibe, direct talk

Friendly, straightforward communication beats a perfect brief every time.

The honest exchange

Why showcase permission matters

A portfolio is how Pakkit proves the work is real and worth your trust. Showing finished projects is the most honest way to say "here's the quality you can expect" — no stock screenshots, no borrowed credibility.

That's the heart of the selective free-build trade: when a project is a good fit, you get a polished site you fully own, in exchange for a small footer credit and backlink, plus permission to feature the finished project here.

The free-build trade, plainly

A small, tasteful footer credit and backlink to pakkit.net.
Permission to showcase the finished project as portfolio work.

Free builds stay selective and case-by-case — no guaranteed acceptance, no fixed number, and no promise of unlimited free maintenance.

Want to be next?

Think your project belongs here?

If you've got a simple business or creative project that'd make a clean, showable site, the intake form is the low-pressure first step.

Want the details on how the selective free-build program works first? The FAQ covers what's included and what isn't.

Start the intake Read the FAQ What's a static site?