A page for the date, and a place for the replies.
A workshop, a supper, a meetup, a launch. One page with the date, the place and what happens, and every reply in one list instead of four.
The date is the whole headline.
Everything else on an event page is detail. Somebody has to know when, where and whether there is room, in that order, before a single word about why it is worth going.
Six courses from whatever the market has that week, at one table of sixteen. Doors at seven, in the old print works on Sofielundsvägen.
Late. A page nobody can find until the week before is a page that sold half the seats, so the date and the address go up the day you decide them and the rest of the page catches up afterwards. Saying what is different is how it catches up.
Replies first, because that is what you came for.
The other two come with it, and the second event is when you notice.
Get booked
Somebody asks for a place and the request arrives with the name and how many, in one list you can count.
Get messages
The question that is not a booking still reaches you, in the same place.
Take orders
A ticket, a deposit, a book of the recipes afterwards. Somebody asks for one and you find out which.
A form in a caption is not a guest list.
Almost every small event is organised in four places at once. The date is in a story that expires, the address is in a reply to somebody who asked, the replies themselves are spread across two apps and a group chat, and the person running it is the only index.
That holds for sixteen people once. It stops holding the second time, and it never held for anybody who wanted to come and could not find out when it was.
A page fixes the smaller half of that: one address you can put anywhere, with the date and the place on it, and every reply arriving in one list you can count. You still cook, still talk to people, still change the menu on the Thursday. You stop being the only place the information lives.
The three we get every time.
Not yet, and it is the honest answer rather than a soon. The request reaches you complete and you take the money the way you already do. Paying on the site is being built.
Then the page is about the next one, and you say what is different when the date moves. Nothing here assumes a calendar of forty events or a ticketing system you have to learn.
It stays up and becomes the page about the last one, which is what somebody reads before they decide about the next one. You are not starting from nothing every time.
Put the date somewhere people can find it.
Free to build, and live for seven days.