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.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: Discourse Meta: Easily create Events categories using the Events and Calendar plugin
Discourse says the Events category type auto-configures Calendar enabled, Discourse post event enabled, and Events calendar categories, with hosted availability on Business plans and above.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 30, 2026
When to use it
Use this when Community, Lifecycle Messaging, Brand is relevant to community engagement, retention loops, event programming and you can run a bounded test with a medium budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Community and Lifecycle Messaging, using evidence from Discourse Meta: Easily create Events categories using the Events and Calendar plugin as context—not as a promised result.
- Record a baseline for: Share of the target cohort repeating the core action within the chosen period. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.