Common Ground Sessions
One place for the next gathering.
- Sector / Year
- Community and culture
2025 - My role
- Content structure and website development
- Scope
- Programme, event pages, venue information, and past sessions
- Built with
- Statamic · Antlers · CSS
The brief
Common Ground Sessions brings together small talks, hands-on workshops, and conversations about making things locally. The website needs to answer a few immediate questions: what is happening, when it starts, where it takes place, and what someone needs to know before arriving.
I placed those details ahead of the longer event description. The programme works as a practical schedule, with enough character to reflect the people behind it.
Treat a date as useful information
Event dates have their own fields, alongside start and finish times. That makes the programme sortable and gives past sessions a clear place in the archive. A postponed session can carry a visible status instead of relying on a correction buried in its description.
The individual event page groups arrival information, access notes, and anything participants should bring. These details remain easy to scan on a phone.

Keep the programme readable
The visual language takes cues from a printed programme: clear headings, fine rules, and small blocks of practical information. A visitor can move from the overview to an event without learning a new layout.
Venue information is managed separately and linked to sessions. Where an event has different arrangements, its own notes explain the exception.
The editing experience
Adding a session means entering its name, short description, date, times, venue, and status. A longer body gives the organiser room to introduce the subject. Past events retain their descriptions and can receive a short recap.
Booking and payment processing sit outside the website’s scope. The programme concentrates on helping people decide whether an event is relevant and understand the next step.
What this project brings together
The useful work is in the details: a clear time, a visible change of status, and a venue description that does not need to be copied into every entry. A growing archive stays separate from the upcoming programme without discarding past activity.