# Events category as recurring programming home

> Give community events their own Discourse category with the calendar plugin turned on by default, rather than burying every meetup in general discussion.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/events-category-as-recurring-programming-home/
- Source: [meta.discourse.org](https://meta.discourse.org/t/easily-create-events-categories-using-the-events-and-calendar-plugin/401309?tl=en)
- GrowthDex source hub: [Discourse Meta: Easily create Events categories using the Events and Calendar plugin](/sources/discourse-meta-easily-create-events-categories-using-the-events-and-cale/)
- Last checked: 2026-05-30
- Rarity: rare
- Budget: medium
- Channels: Community, Lifecycle Messaging, Brand
- Stages: community engagement, retention loops, event programming, return visits


## Why this can grow

Communities say they run events, but members often cannot tell what is coming up, where to RSVP, or which threads are actual events instead of chatter. Discourse's newer Events category setup fixes that by giving the operator a category type that enables the right calendar settings automatically and keeps event controls in one place. The gain is not only convenience. A visible events lane gives the community a rhythm. It turns live programming into a repeating reason to return, and it gives newcomers an easy first reason to participate without needing a strong opinion yet.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For retention, I would watch the second and third use, not just the first click. A tactic is real when it changes a habit. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where events category as recurring programming home can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Lifecycle Messaging channel.
3. Use the evidence from meta.discourse.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Discourse announced in May 2026 that the Events category type now auto-enables the Calendar and Post Event settings, adds the category to the Events calendar categories setting, and exposes defaults for calendar view and event-creation permissions based on what has worked in other communities.

## Adjacent tactics in the same lane

- [Vote-to-watch prompt after idea upvote](/growth-ideas/vote-to-watch-prompt-after-idea-upvote/) - 2 shared channels, 1 shared stage
- [Gumroad customer-investor community round](/growth-ideas/gumroad-customer-investor-community-round/) - 2 shared channels
- [GitHub profile README as operator proof surface](/growth-ideas/github-profile-readme-as-operator-proof-surface/) - 2 shared channels
- [Discourse Upcoming Changes opt-in before community rollout](/growth-ideas/discourse-upcoming-changes-opt-in-before-community-rollout/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The community should teach the first contribution before it asks for loyalty](/blog/the-community-should-teach-the-first-contribution-before-it-asks-for-loyalty/) - community-led growth, brand trust, retention

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.