
Rebuilding AZSolo.com, a website built to be handed over
In 2021 I rebuilt the website for the Phoenix AZ Solo Region of the SCCA. It plugs into MotorsportReg for events, Printful for one-off club merch, and live timing software built by a fellow club member, and it was designed from day one to be handed on to the next volunteer.
Most months, a car park at Phoenix Raceway fills with cones, helmets and people who've spent the week thinking about tyre pressures. That's autocross, or "Solo" in SCCA terms: one car at a time on a course laid out with cones, racing the clock rather than each other. The Phoenix AZ Solo Region has been running these events for years, and in 2021 I rebuilt the club's online home at azsolo.com.


Where it started
I started autocrossing in 2020 and I've been out every month since, locally with AZ Solo and nationally at events across the country. I've worked my way through a few autocross cars along the way, starting with an Audi S3, then a Subaru BRZ, and now a Chevy Camaro.
The club is one of many SCCA regions in the Southern Pacific Division, and like every region it runs on volunteers. A steering committee, a registration chief, a timing and scoring chief, a membership chair: everyone has a day job, and everyone has a turn at the cones.
In 2021 the volunteer who had looked after the website moved out of state. The site was dated, it didn't connect to any of the modern services the club and its drivers relied on, and there was no club merch at all. Rather than just finding someone to keep the old site ticking over, there was a chance to fix all of that at once, and to build something with the next volunteer in mind.
Why WordPress?
As an engineering leader, I'd usually rather build something custom than wrestle a CMS. This time I deliberately didn't.
The most important requirement for the new site wasn't a feature. It was that the site had to outlive my involvement. Volunteer roles rotate. The person who looks after the website this year will hand it to someone else in a few years, and that person might be an engineer, or they might be the club member who's comfortable with a computer and said yes when nobody else would.
That ruled out anything that needed me to maintain it. WordPress ticked the boxes:
- Many hands. News posts, the Pylon Press newsletter, meeting minutes and documents are all published by different people on the committee. WordPress gives each of them a login and a role, without anyone touching code.
- Easy to hand over. WordPress runs a huge share of the web, so the next maintainer can find help, a tutorial or a freelancer for almost anything.
- Plugins over bespoke code. Wherever possible, the integrations use well-supported plugins and standard services, so there's very little custom code for the next person to inherit.
That's the same trade-off I help teams make at work, just at a smaller scale: the best solution isn't always the most technically interesting one. It's the one the people who'll own it can actually keep running.
Events, straight from MotorsportReg
In the motorsport world, MotorsportReg is the standard. Autocross, track days, HPDE and club racing across the country are run through it, so drivers already have an account, their car details and their membership on file.
There was no point making the club maintain a second list of events. The club creates each event once in MotorsportReg, and the site pulls it through into the AZ Solo event calendar, with the date, venue, location and type, and a link to register. Drivers see what's coming up on the home page, then register on the platform they already use.
The integration is a plugin, owned and maintained by MotorsportReg. That was the whole point: there's no custom code for the next volunteer to look after, and it improves over time as MotorsportReg updates it.

Club merch, made one at a time
Before the rebuild, the club had no merch at all. The traditional way to fix that is to guess sizes, order a box of shirts up front and hope they sell. That ties up money a small club doesn't have and leaves someone storing a box of mediums in their garage.
The site's shop is built on WooCommerce and connected to Printful, a print-on-demand service. When a member orders a shirt, a cap or a jacket, Printful prints that one item and ships it straight to them. The club holds no stock, pays nothing up front and never has to post a parcel. Today the shop carries hats, men's and women's shirts, jackets and sweaters, stickers, and special event designs.
That last category is my favourite part. Because nothing is made until it's ordered, the club can put up a design for a single event, like a National Tour, and it costs nothing if only a handful of people want one.

Live timing, built by a club member
Autocross is all about the clock. Every run is timed to the thousandth, cones cost you seconds, and between runs everyone is checking where they stand.
AZ Solo's timing and scoring chief, Jason Bucki, built the club's timing software himself. It's the backbone of every event day. It connects to the club's timing hardware, gives the timing workers the tools to edit times and add penalties for cones and off-courses, and shows the standings for each class and overall in real time as the runs come in.
My part was connecting the website to it. A Live Timing link sits at the top of every page, so drivers can pull up times on their phone in the grid. The results page embeds Jason's results view straight into the club site, so every event is there with its class standings, fastest times, PAX-adjusted times and points, and a dropdown to look back through past events. Jason's software stays the source of truth, and the website never has to copy or re-key a single time. Jason had already done the hard work, so embedding it was straightforward.


It's one of my favourite things about the project. The best software at a small club is often built by a member who saw a problem and solved it, and the website's job is to put that work in front of everyone.
Handing it over
In 2025 I handed the site over to the next volunteer. The handover was a short call to walk through the basics of WordPress, and that was it. I haven't needed to provide support since, which is exactly what I'd hoped for.
The real test of the project is that the site has carried on without me. The calendar still fills from MotorsportReg, the shop still prints shirts on demand, the committee still publishes news and minutes, and the timing link still lights up every event day.
What I learned
Design for the next maintainer, not for yourself
It's tempting to build the thing you'd enjoy maintaining. For a volunteer organisation, the better question is who will look after it in three years, and what they'll be comfortable with.
Integrate with what the community already uses
Drivers already lived in MotorsportReg. Rather than competing with it, the site points to it. Meeting people where they are beats asking them to learn something new.
Let services do the heavy lifting
Printful handles printing and shipping. MotorsportReg handles registration and payment. Jason's software handles timing. The website ties them together, which keeps it small enough for one volunteer to own.
Come out and drive
If you're in Phoenix and you've ever wondered what your car can really do, autocross is the safest, cheapest way to find out. All you need is a driver's licence, a helmet and a roadworthy car. Check the events calendar and come out to an event. Bring sunscreen.