Website design and rebuilds
A cleaner public site for a business that already knows what it sells. Pages, mobile layout, and a form that goes somewhere useful.
Services
Websites, WordPress frontends, and the tools around them
I build the public site and the editing setup behind it. Start with one piece, or combine them.
What I build
Four starting points
Headless WordPress
WordPress stays the editor. The visitor site can be Astro or another frontend when the theme is slow or hard to control.
Plugins and custom features
Business-specific WordPress features, admin tools, and integrations that generic plugins will not cover cleanly.
Forms, automation, and care
Inquiry routing, notifications, landing pages, and the ongoing cleanup that keeps a live site from rotting.
WordPress and the frontend
Use WordPress where editing matters
Traditional WordPress is fine for many sites. When the public pages need more speed or design control, I keep WordPress for content and put a separate frontend in front.
WordPress
Pages, posts, and structured fields from the dashboard you already know.
Astro or JS frontend
Layout, performance, and the visitor experience — without stuffing that into a theme.
Process
Discovery, structure, build, review, launch
You will see the page list and the build path before I write a lot of code.
-
Step 1
Discovery
Goal, pages, features, and which setup fits.
-
Step 2
Structure
Sections, content fields, and how you will edit later.
-
Step 3
Build
Frontend, WordPress, forms, and integrations.
-
Step 4
Review
Content, mobile, forms, and the important flows.
-
Step 5
Launch
Hosting, DNS, and a last pass before it is live.
FAQ
Short answers
Can WordPress stay and the site still get faster?
Yes. WordPress can be the backend while a custom frontend serves the public pages.
Do I need a fully custom site?
Not always. Some projects are a focused WordPress setup. Others need a frontend or extra automation.
Can this sit on an existing WordPress install?
Often. It depends on hosting, plugins, and how the content is structured today.
Do you build forms and workflows?
Yes. Contact forms, routing, and lightweight automation can be part of the same build.
Tell me what you are trying to ship
A rebuild, a headless frontend, a plugin, or a form that finally routes. The contact page is enough to start.