Milan Dragway has been part of Midwest motorsports since 1963. In 2024 and 2025 we worked with its then-owners, Pam and Perry, introduced to us by Mickey York of Cruis'n Media. We came in as an on-call creative resource — flyers, social content, whatever was needed — but the work that mattered most wasn't a design problem at all.

It was a maintenance problem.

The Actual Problem

A racing venue runs a schedule that will not sit still. Events get added. Events get rained out. Start times shift, classes change, a national touring event moves a local race night. In a given week, the calendar might change three times.

Now consider what happens if updating that calendar requires emailing someone.

The change doesn't happen immediately. It happens when the person who can make it has time. In the meantime, the website says something that isn't true. Someone checks the schedule, sees an event that was cancelled or misses one that was added, and either shows up on the wrong day or doesn't show up at all.

That is not an inconvenience. For a venue that makes its money on ticket sales, every hour a schedule sits out of date is an hour that costs money.

When a website can only be updated by a developer, the real cost isn't the invoice. It's the delay. Content that requires a request ticket to change will always lag behind reality, and for any business with schedules, pricing, or availability, out-of-date information directly costs revenue.

There's a second, quieter cost. When updating the site is a hassle, people stop doing it. Not consciously — they just deprioritize it. The site slowly drifts from being the source of truth to being a brochure nobody trusts, and staff start telling customers to check Facebook instead. That's how a business ends up with a website it has effectively abandoned while still paying to host it.

How We Approached It

The goal was simple to state and easy to get wrong: the people who run the venue should be able to update the venue's website themselves, quickly, without asking anyone.

Structure the content as data, not as pages. An event isn't a page — it's a record with a date, a time, a class, a description, and a price. Once events are structured that way, adding one means filling out a short form rather than duplicating a page and hoping the formatting holds. Everything that displays them updates automatically.

Design the editing experience, not just the visitor experience. This is the part most website projects skip entirely. Field labels should say what a staff member would call the thing, not what a developer would. If a field is optional, that should be obvious. If a date is required in a particular format, the field should enforce it rather than let someone break the layout. The person editing the site is a user too, and their experience determines whether the site stays current.

Make it impossible to break the layout. A staff member updating an event at nine at night should not be able to accidentally destroy the page. Constraints — set field types, fixed layouts, controlled options — aren't limitations. They're what makes it safe to hand over the keys.

Reduce the steps. If changing a start time takes six clicks, it will happen late. If it takes two, it happens now.

Alongside the calendar work, we designed event flyers and social content, and worked through existing documents so everything read consistently and stayed on brand. But every decision came back to the same three questions: does this make it easier to find an event, easier to understand it, and easier to buy a ticket?

A website your team can maintain is a design decision, not a technical one. Structure recurring content as records rather than pages, label fields in the language your staff actually uses, and constrain the layout so no one can break it. If updating the site is easy, it stays current.

What Stayed

The track was sold in 2025 and now operates under new ownership as Darana Dragway. Our engagement ended with the sale.

The calendar and event page structure we built is still in use.

We'd rather have kept the client. But work that outlasts the engagement, under different ownership, with nobody left who was there when it was built, is its own kind of verdict on whether it was built right.

This Applies to More Than Racetracks

The same pattern turns up everywhere a business has content that changes faster than a development cycle:

• Breweries with rotating taps and event nights
• Restaurants with changing menus and specials
• Chambers of commerce and nonprofits with event calendars
• Churches with service times and programs
• Venues, theaters, and galleries with show schedules
• Contractors with changing service areas or seasonal offerings
• Any business with prices that move

If you've ever thought "I should update that but I don't want to deal with it," that's the signal. It isn't laziness. It's a design problem, and it has a fix.

Questions People Ask

Can I update my own website without knowing how to code?
Yes, if it's built for that. A content management system lets you edit text, images, and structured content like events or products through a simple interface. Whether it's actually pleasant to use depends on how carefully the editing experience was set up — that part is a design decision, not an automatic feature.

Why does my web developer have to make every change?
Usually because the site was built as fixed pages rather than editable content, or because the CMS was set up for the developer's convenience rather than yours. Both are fixable, though depending on how the site was built it may mean restructuring rather than a quick adjustment.

What's the best way to handle an event calendar on a website?
Structure events as individual records with defined fields — date, time, title, description, price — rather than as manually built pages. Everything that displays events then updates automatically when a record changes, so adding an event takes a minute instead of an hour.

How do I stop my website from going out of date?
Make updating it fast. Most stale websites aren't neglected on purpose; they're stale because updating them is annoying enough to postpone. Reduce the number of steps between "this changed" and "the site says so," and the problem tends to solve itself.

Is it risky to let staff edit the website?
Not if the site constrains what they can change. Well-built content fields let someone update the information without touching the layout, styling, or structure. The risk comes from giving broad editing access to a site with no guardrails, which is a setup problem rather than a staffing one.

What should I ask a web designer about updating my own site?
Ask them to show you the editing interface before the project ends — not a description, an actual walkthrough of adding a real item. Ask what you can change yourself and what requires them. Ask what happens if you make a mistake. The answers reveal whether the site was built for you or for them.

Tired of emailing someone every time something changes? Schedule a free consultation at jpetrous.com | contact@jpetrous.com | 586-563-6634.