Toby's Milkbar is a sandwich bar in an industrial pocket of Prestons, on a road you only drive down if you meant to. Toby's 2.0, the trailer, is the half of the business that travels. On any given weekend it might be at a bike meet in Artarmon or an after-dark festival out at Bella Vista Farm. The list of dates on the site is how people know where to go.
Five dates, five posters, five addresses. Nobody at Toby's opened the website to put any of it there.
Showing Saturday the 29th for an event on the page is only true up until the 30th. After that, someone has to update the website, or a customer is driving out to Prestons on a night the trailer is parked in Artarmon.
But a date for the next event gets agreed to on the phone, and opening the website is not what happens next. The shop gets busy, the day carries on, and by the time there's a quiet moment the date has been forgotten. Nobody decided not to update the site. It just never got done.
That's how an events page ends up months out of date, or gets quietly deleted by whoever got sick of it being wrong.
The dates were already written down, just not on the website. They go into a shared Google Calendar the moment they're agreed, because that's how you avoid promising the trailer to two people on the same Saturday. Asking for them again, in a system with its own login, only gives you two versions that can disagree. So we pointed the website at the calendar. Here's one of the events above, and where each part of it came from.
The heading, exactly as typed. That includes the truck emoji Toby's started putting on the dates away from Prestons. Nobody handed them a list of categories to pick from.
Written out in Sydney time. A single night gets a start and a finish on one line; a run like this one gets a date range. Nobody types a date twice or formats anything.
The address on the page, with a link straight into Google Maps directions, which is what the person reading it actually wants.
The couple of lines under the heading. Whoever booked the gig wrote them once, in the calendar entry.
The poster beside the listing. Organisers send a flyer for nearly every event, and dragging it onto the calendar entry is now where it goes.
Adding events is the easy part. Getting rid of them afterwards is what keeps the page worth looking at, because nobody comes back to a list of nights that have already been and gone. And nobody at Toby's does any of it.
We could have built an admin screen. Those are quick to build and they look good in a demo. A login, a form, a list of events, a publish button. What it actually gives you is another password, another screen someone has to be shown how to use, and one more place a date can be wrong.
Toby's already had a place where the dates live, and it's open on their phone all day. Nothing about it needed replacing. It just needed reading.
If someone has to remember to do it, it doesn't get done.
To put an event on the website
Put it in the calendar.
There is no step two.
Reading a calendar, keeping an API key somewhere it can't leak, working out what the page should say when there's nothing in the calendar at all. That's software. It just happens to look like a web page by the time it's finished.
It's also why we don't hand the website to one company and the clever bits to another, with a third looking after the domain, the email and the hosting. When something's wrong with the events page there's one number to ring, and whoever answers wrote it.
Tell us what someone has to remember to change every week. The dates, the prices, the roster, or the list that's already a bit out of date.