SERVICES
How I work with clients
Three engagement types. Each one is shaped around shipping something concrete on a calendar a client can actually plan against, not an open-ended retainer.
01 — WORDPRESS & WOOCOMMERCE BUILDS
Custom block themes, real stores, no page-builder lock-in
Marketing sites, content sites, and WooCommerce stores built on Full Site Editing block themes. Your team gets a real editor experience, not a maze of nested shortcodes. The hub you’re reading right now is built this way; the two case studies on this site show what production output looks like.
- Full Site Editing themes with custom
theme.jsondesign systems - WooCommerce stores on the block-based cart + checkout (Additional Checkout Fields, custom blocks)
- Custom Gutenberg blocks authored with
@wordpress/scripts+block.json - Headless WordPress via WPGraphQL or REST, paired with a Next.js front-end
- Performance-first builds: dequeue what isn’t used, dynamic
filemtimecache-busting, Lighthouse 95+ targets
02 — PLATFORM & DEV INFRASTRUCTURE
Lift your team’s shipping velocity
The most common reason a small team ships slowly isn’t the code — it’s the friction around the code. Multi-environment deploys that nobody trusts. Local setup that takes two days. A staging server that drifts. The platform that hosts the demos on this hub is a worked example of what “everything reproducible from a script” looks like.
- EC2 + Apache provisioning, per-subdomain Let’s Encrypt, automated certbot renewals
- Multi-site WordPress platforms with shared chassis + per-site customization (symlink architecture)
- Node-based deploy pipelines:
rsync+node-ssh+ safe SSH key staging for WSL - Cron-driven backups, weekly content resets, Lighthouse score tracking
- Local dev environments via
@wordpress/env(Docker) with one-command spin-up
03 — FULL-STACK WEB APPS
Beyond WordPress when the project calls for it
Plenty of work doesn’t fit a CMS. Custom admin tools, client portals, multi-tenant SaaS, internal dashboards. Fifteen years of full-stack work across Laravel, Node, React, and Next.js — the kind of build where the data model and the workflow matter more than the marketing surface.
- React + Next.js front-ends, including Next.js standalone-output self-hosted deployments
- Laravel + PostgreSQL/MySQL back-ends, queue workers, scheduled jobs
- TypeScript end-to-end, including shared types across HTTP boundaries
- Authentication flows (OAuth, magic links, JWT, session-based) — including the migration from legacy to modern
- API design (REST + webhook orchestration) for third-party integrations
How engagements start
Every project begins with a short conversation about scope, deadlines, and what “done” actually means. I write fixed-scope proposals when the work is well-defined and discovery-then-build proposals when it isn’t. The development business runs through scopeforged.com — that’s where contracts get signed and invoices get sent. This hub is the portfolio side of the same operation.