Organize events with categories

Categories are the short list of buckets your events fall into — Concert, Workshop, Community gathering, Volunteer days. Visitors use them to filter your public page down to what they're looking for, and other calendars use them as the basis for matching when they repost your events alongside their own.

Your category list should be short. A small, durable category vocabulary is one of the highest-leverage decisions you'll make as a calendar owner. This guide is about designing that vocabulary so it serves you over time.

What categories do

Three jobs:

Filter the public page. Visitors browsing your calendar see a row of category buttons above the events. Clicking Concerts hides everything that isn't a concert. Categories are the main way visitors narrow down a busy calendar.

Jump from one event to related events. On every event's detail page, the categories it carries appear as clickable links. A visitor reading about Tuesday's concert can click Concert and land back on the calendar filtered to every other concert you've published. It's the "more like this" path. This is where consistent category names are valuable: if last month's Live Music and this month's Concerts are technically the same kind of event under different labels, the jump from one to the other doesn't work.

Give other calendars something to match against. When another calendar reposts an event from yours, their categories rarely line up with yours one-to-one — your Concerts might be their Live Music, your Workshops might be their Classes. Category names are the signal each calendar uses to translate between vocabularies. Stable, recognizable category names mean other organizers can route your events to the right place on their calendars without you (or them) doing it by hand every time.

Categories aren't strictly required; an event with no categories will still publish. But it won't show up when visitors filter, won't appear under "more like this" on a related event, and won't have anything for other calendars to match against — which is enough reason to tag every event.

Create a category

Open Manage Calendar from your calendar page and find the Categories tab. The first time you visit, the list is empty.

Click + Add category. A small editor opens with one field: a name. Type the category name — Concert, Workshop, Volunteer days — and click Create. The new category appears in the list with an event count of zero.

If your calendar publishes in more than one language, the editor lets you provide the category name in each — click + Add language, pick the language, and fill in the translation. A Workshop category in English becomes Atelier for visitors browsing the page in French. The category itself is one thing with multiple labels, not multiple categories.

Once a category exists, it shows up in three places:

• In the Categories section of the event editor, where you check the categories that apply to the event you're creating or editing.
• On your public calendar page, as a button in the filter row — but only once at least one event uses it. Empty categories don't clutter the filter.
• On the detail page of every event that uses it, as a clickable badge that takes the visitor back to the calendar filtered to similar events.

To rename or retranslate a category, click the pencil icon on its row in the list. To delete one, click the trash icon — the dialog asks whether to remove the category from its events (the events stay, they just lose that category) or migrate those events to a different category in one move. (For collapsing several categories into one or splitting one into two, see The cost of churning category names later below.)

Designing the list

A short, durable list works better than a long, descriptive one, for two reasons:

Visitors scan the filter row. A list of six categories is a row people read in a glance. A list of thirty is a wall of text — and most filter rows on most pages get scrolled, so the categories at the end might as well not be there.

Tagging shouldn't be a fresh decision every time. Each event you publish, you pick its categories from your list. If the list is too granular ("Acoustic Folk Concert," "Indie Rock Concert," "Open Mic Night") that pick becomes a small decision every time — and different editors will make those calls differently, so the same kind of event ends up under different labels. A coarser category ("Music") absorbs all four, makes the choice simple, and keeps tagging consistent across the calendar.

A useful starting point is five to ten categories that cover the general shape of what you publish. Music, Workshop, Community gathering, Volunteer, Talk, Family-friendly, Online — you'll know your community's actual buckets better than any generic list.

When you're tempted to add a category

A new event arrives that doesn't quite fit any existing category, and the impulse is to add a new one. Before you do, ask whether what you're trying to flag really is a category at all — most of the time the impulse is pointing at something that belongs in a different tool.

Is this a detail of this one event? The name of the band, the topic of the talk, the cuisine at the potluck — those are details of this event. They belong in the event's title or description, where they're searchable and where visitors actually read them. A category is for the kind of thing the event is, not for the specifics of what's happening at it.

Is this a program of distinct events? A summer concert series with a different artist each week, a fall lecture series with rotating speakers, a recurring book club where the topic changes each session — these are programs with several distinct events under them. The right tool is a series, which groups related events under one program name. Adding Summer Concert Series as a category just to find this year's events again creates a label that goes stale by definition.

Could the event carry two existing categories instead of one new one? Events can carry more than one category. A workshop that's also a fundraiser doesn't need a Workshop fundraisers category — tag it Workshop and Fundraiser both. When you find yourself wanting to combine two existing categories into a compound one, the answer is usually to use them both, separately.

If the event genuinely belongs in none of those, a new category may be the right move. One last practical check: will it have at least three or four events on it within the next year, and will visitors filter for it? A category with one event does no work for visitors and drifts toward becoming dead weight; a category nobody filters for ("Tuesday-evening events," "2026 season") uses up filter-row space without earning it.

The bias should be toward fewer categories rather than more. It's easier to split a busy Workshop category into Workshop and Class later than to consolidate ten thin ones back down.

The cost of churning category names later

Renaming a category looks free from inside the editor — the change saves immediately, the events update, the public page reflects the new name on the next reload. It doesn't feel like a big deal.

It is more of a deal than it looks, for two reasons.

Other calendars have rules matching your category names. If another calendar is reposting your events onto theirs, they may have set up a rule that says "events from your-calendar tagged Concert go on our Live Music category." Renaming your Concert category to Concerts & DJ Sets breaks that rule until they notice and update it. Several reposting calendars means several broken rules. Your events still propagate (the underlying connection isn't broken), but they may land in the wrong category on the other end, or fall into a "needs review" pile that the other owner has to triage.

Visitors and editors have built up muscle memory. Regulars know your filters. Co-editors know which category to pick for a given event. Renaming or splitting a category invalidates that knowledge — every editor relearns the list, every visitor wonders where Music went and why everything is now under Sound.

Pick category names that age well. Names tied to the kind of event ("Concert," "Workshop") age better than names tied to a moment ("Summer 2026 series"). Names that other communities would also recognize ("Volunteer day") age better than insider terminology ("Stewardship hours"). Names short enough to fit in a filter button on a phone screen age better than long ones that will get truncated.

When you do need to change a name, the editor's pencil icon updates the label without disturbing the events on it. That's the right tool for a small fix — correcting a typo, adjusting capitalization, refining a translation. For bigger restructurings — collapsing two categories into one, splitting one into two — the merge and migrate tools in the category list are designed for exactly that work, and they'll handle the event reassignments in one move rather than one event at a time.

A note on the first month.

The category list you set up in the first weeks of a new calendar is a draft, not a commitment. Watch what kinds of events you actually publish for a month or two before treating the list as fixed. The categories you'll use most are usually obvious by then — and the ones you'll never use again are obvious too.