Bluehost & Zapier
The server-side intake was built to validate required fields before forwarding a signed request to Zapier. Routine and urgent requests take separate routes. Spam and duplicate checks are part of the intake design.
Featured Web Project / Moab, Utah
I built a retro off-road website for a shop that handles everything from planned upgrades to trail breakdowns. The design gets customers to the right next step and gives the shop a clearer picture of the work before the vehicle arrives.



Brand & Website
The owner wanted an ’80s look. I carried the original arch, sunset, gear, and tire-track details into a circular badge, a compact wordmark, and a pixel-art desert scene.
Repairs, fabrication, and recovery each have a clear entry point. Real shop projects link back to their original Instagram posts, and a scrolling dealer-logo bar shows the brands the shop works with. On a phone, the call link and service request are easy to reach.
Customer Workflows
A trail breakdown, a scheduled drop-off, and a question about a new noise each need a different next step.
The bottom-right Zapier AI chat helps customers turn observations into a useful description for the shop. It asks about the vehicle, what changed, and when the symptom happens. Chris handles diagnosis and scheduling.
The routine-service workflow uses the shop’s Google Calendar to check availability for 30-minute drop-off windows, then routes the request details to Gmail. Chris manages blocked time and schedule changes in the calendar. The window is for handing over the vehicle. Repair timing is agreed with the shop.
The live website puts a click-to-call link in front of drivers who need recovery help. The separate urgent intake workflow uses SMS by Zapier for a compact callback and location summary, with the full request routed to Gmail. Chris decides how to respond.
Behind The Scenes
The integration gives the shop the details it needs and keeps calendar control in the owner’s hands.
The server-side intake was built to validate required fields before forwarding a signed request to Zapier. Routine and urgent requests take separate routes. Spam and duplicate checks are part of the intake design.
Google Calendar provides the availability and blocked-time checks for drop-offs. Gmail gives the shop a place to review full vehicle and request details. The live service form also lets customers open a prefilled email and attach photos.
The public chat asks visitors to keep personal details out of the conversation. Contact details belong in the shop’s intake. The site includes cookie preferences and Google Analytics for measuring how visitors use it.
We verified the live mobile chat with a vehicle-symptom example and tested a signed Bluehost-to-Zapier handoff. The site’s direct call and email paths are available while calendar booking and urgent text delivery complete their launch checks.
The Result
MOAB 4x4 gets a site that looks like its own shop, gives customers a way to explain the job, and connects that first conversation to the tools Chris uses to run the day.
Social Listener
Put shop updates where customers can find them.
The workshop section turns social posts into examples of the shop’s work. Each card includes a photo, the type of work, and a short description, with a link to the original post.
The social listener loads Instagram updates from a server-side feed when the workshop section comes into view and rechecks it every 15 minutes while the page is open and visible. If there are no usable updates, the site keeps its featured posts in place. Examples include a Bronco differential mount, Jeep suspension links, and a buggy steering mount.