mcwumbly announced a biweekly informal community hangout to discuss Discourse features and community building. The initial session focused on bundle splitting for faster load times, with subsequent sessions planned for Events improvements and Docs. Key ground rules established were to keep interactions casual, avoid recordings (specifically AI note-takers), and ensure no FOMO for those who cannot attend.
Participants provided feedback on logistics and product direction. nathank suggested varying meeting times and inquiring why the Discourse Live Plugin wasnโt used instead of Zoom. mcwumbly explained that while Live is promising, Zoom currently offers better moderation controls for webinars, though future convergence between Events and Live is planned. Regarding scheduling, mcwumbly confirmed a shift to an evening time slot for upcoming sessions to accommodate different time zones.
A significant portion of the discussion centered on the introduction of built-in Blog features. philh expressed concern that integrating blogs might lead to โfeature bloat,โ reminiscent of vBulletin. In response, mcwumbly clarified that Discourse is intentionally integrating more features into core but maintaining a plugin-like boundary where features can be toggled on or off. This allows for deeper integration while still supporting external solutions. Vsekraski, mcwumbly, and Vsekraski discussed use cases for bloggers, with one user detailing a vision for personal master portfolios, project diaries, and subscriber feeds within the community.
putty questioned the decision to host multiple events in a single thread rather than separate topics. mcwumbly explained this structure supports the informal, ongoing nature of the hangouts, though separate topics might be used for more formal webinars. Minor technical issues were also addressed, such as RGJ missing the chat feature, which Falco identified as a profile setting issue. Looking ahead, Michelle_L proposed dedicated sessions on AI best practices in communities, which mcwumbly welcomed, noting the potential for multiple specialized topics.
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.