mcwumbly announced a fortnightly, informal “Discourse Community Hangout” to discuss product features and community building. The sessions are intentionally casual, unrecorded, and open to all participation styles, with the goal of avoiding FOMO for those who cannot attend live. The initial series includes a session on splitting bundles for faster load times and another on Events features, led by team members like @david and @martin.
Community feedback sparked several logistical discussions. nathank questioned the fixed time zone and why the Zoom integration wasn’t replaced by the newer Discourse Live plugin. mcwumbly explained that Zoom currently offers superior webinar moderation controls but acknowledged the need for variable times to accommodate global users, subsequently adjusting the next session to 16:00 America/New_York to better suit different time zones.
A significant portion of the discussion focused on the potential introduction of built-in blog features. philh expressed concern about “feature bloat” and the shift from a community forum to a blogosphere. In response, mcwumbly clarified that these features would be implemented as toggleable core plugins, allowing sites to opt-in only if desired. This aligns with Discourse’s strategy to offer more integrated experiences for users who prefer not to rely on external platforms, while still supporting existing integrations.
Vsekraski, a user from a decorative plaster community, shared a detailed Russian-language proposal outlining blog needs such as personal master pages, project diaries, and subscription features. mcwumbly welcomed the feedback and encouraged community self-promotion where relevant. putty raised UX concerns regarding RSVPs in a single persistent topic, which mcwumbly defended as a choice to maintain informality.
Other topics included the use of AI in community management. Michelle_L suggested dedicated sessions on AI best practices, moderation, and search enhancement, which mcwumbly welcomed as a potential multi-part series. Additionally, RGJ reported missing chat access during the Zoom event, which was resolved by Falco noting a disabled profile setting.
Every other week, we’ll make space to get together live for some informal discussion.
Come hang out with some of the Discourse team, take a closer look at some new and upcoming Discourse features, and chat about current topics related to the product or community building.
At least a few members of the Discourse team will be there, and often we’ll start with a short demo of something we’re working on.
How we roll
keep it casual
we want folks to feel welcome to participate in any way they choose. if you have a question, feel free to jump in to the conversation. if you prefer to drop a note in chat first or instead though, that’s fine
no recording
we won’t be recording these. please don’t bring or send your AI note taker. again we want to keep it casual
no fomo
if you can’t make it, or have to drop early, don’t worry. you can join the next one and we can keep the discussion going here in between
Upcoming
2026-11-19T21:00:00Z: Let’s talk about Events @martin will share more about some of the work we’ve been doing recently to improve the Events features in Discourse, and then we’ll see where the conversation takes us. Hope to see you there!
Past
2026-11-05T14:00:00Z: Splitting the bundle for faster load times @david will walk through some of the work we’ve been doing to make Discourse load faster, even as we add more features to the product, by splitting the JavaScript application into bundles that aren’t loaded until they are needed, followed by open discussion about this topic or anything else on people’s minds.
2026-10-22T13:00:00Z: Meta community design @manuel will give us a quick tour of the recent updates we have been making to the design of meta, and a behind the scenes look at how the pieces are put together.
Can’t make this first one, but love the spirit of this!
PS: events functionality is looking great with the addition of integrated chat channels & livestream Join Zoom button! We’re considering moving our events to Streamyard, and this UX is compelling!
look forward to you joining another one in the future!
hopefully this (and other events we do here) will give us all more collective experience together with the events features of Discourse as well, and drive further improvements there too.
We aren’t planning on recording these, but we may explore doing it at different times in future sessions. If there are other time windows that you think we should consider in the future, let us know!
Thanks for the reply, no worries on time, there is no perfect time. Too bad about not recording. Perhaps that will change depending on how the Zooms go.
Yes, we’ll certainly consider it in the future. But want to get a few more of them under our belt first.
Both of these features are pretty new. For now, we’ll continue to use Zoom as the backed for the streaming for these Events. Longer term, I think we’ll aim for more convergence between Events and Live, and the distinction will probably seem less important.
I am thinking about what kinds of things we might chat about this coming week (2026-11-05T14:00:00Z)
A few possibilities I have in mind at the moment:
walk through of how we build custom themes
a look at a new “personalized feed” prototype
recent and upcoming improvements to Events features
a look at upcoming changes to Docs
a look at upcoming built-in Blog features
More ideas welcome!
We will likely only have time to really dig in to one of them, but it’ll be good to start collecting things here that people might want to touch on in the future as well.
Thanks for the info, it does seem to be an undertaking that deserves exposure and one that a number of folks will like.
For me reviewing the README I get some flashbacks to the feature bloating of vBulletin and others.
5. Configure:
discourse_blog_url: e.g. https://blog.example.com, no trailing slash/path.
discourse_blog_category: the single public category.
discourse_blog_drafts_category: the private editorial category.
discourse_blog_title, discourse_blog_description, discourse_blog_about.
discourse_blog_enabled: enable after configuration.
The notion of moving Discourse into the blogosphere is not appealing to me but I certainly see how others would like the move.
You mention embedding and by inference the challenges to a successful integration… for me a better integration with common platforms is a better long term solution.
Discourse has a long history of including ancillary features in the product, particularly as plugins.
For a long time, that core vs. plugin boundary was the way that we defined the boundary and kept bloat at bay.
In the past couple years, we have integrated many plugins into core, blurring that boundary. But it still exists. Core plugins can be easily toggled on or off, allowing sites to control which of these feature sets to include.
That has laid the foundation for including more features within Discourse in this way.
It is not exclusive with integrating with other independent solutions. Many have their preferred solutions for these adjacent problems, and we support that too. But where people don’t have those preferences, or where they prefer something even more deeply integrated, we’re more prepared to offer that now.
So I think you’re right to point out this is a bit of a change in direction, or perhaps an acceleration in the direction we were already headed.
There are risks to this approach, but we are being very intentional about it, for example, by continuing to define a plugin boundary with toggles. Another risk is dividing our attention as a small team.
But we think we are in a different world now, where we can include more of these features at a level of quality we can be proud of and people will appreciate.