Unboxing Discourse 3.5

AI-generated summary

The Discourse 3.5 release introduces several key improvements, including the new Horizon theme, enhanced composer options, streamlined color management, automatic site translations, and updated moderation tools. Horizon, now the default theme, features a modern design, simplified color palettes, and improved dark mode support. The release also bundles popular plugins with core Discourse, which may affect self-hosted users needing to take action, while hosted users experience no changes. Community members discuss the update process, particularly regarding switching from the tests-passed to the stable branch, with guidance provided on how to update via app.yml. Additional topics include the removal of support for old browsers, the status of the Tactile Community (an internal test), and appreciation for the new theme. hugh leads the announcement, with contributions from NateDhaliwal, tobiaseigen, Dannii, Albert_Dessaint, RGJ, haydenjames, chapoi, and mcwumbly.

After six months of steady improvements in our beta releases, we’re excited to announce our latest release, Discourse 3.5. This release, we focused on improving both the member and community management experience. We’ve rolled out Horizon, our sleek modern theme; a new composer option that makes creating and responding to topics simpler; streamlined color management with updated dark mode settings; automatic site translations; and much more.


This is a companion discussion topic for the original entry at https://blog.discourse.org/2025/08/unboxing-discourse-3-5
21 likes

IMO this should be emphasized a bit more… it would surprise some admins to find that a bunch of plugins just appeared (not to mention console errors).

5 likes

Thanks for highlighting that here! It’s true that self-hosters who are only updating now will have to take action if they are using any of the affected plugins already. But for customers hosted by us no action is needed and there is no change.

The list of affected plugins and what to do is all explained in the topic the announcement links to so do recommend self-hosters review it. If you have any questions or concerns about it, please reply there: Bundling more popular plugins with Discourse core

6 likes

Dus is dit het moment om over te schakelen naar de stabiele branch als we de ondersteuning voor oude browsers willen blijven behouden?

Moeten we updaten naar 3.5 terwijl we op tests-passed zitten en dan overschakelen naar stable, of eerst overschakelen naar stable voordat we updaten?

Thanks for your work :folded_hands: The horizon theme is great! (Even if I would prefer to see tags directly in the topic card but I understand the trade-offs you made). I saw in the blogpost a screenshot about the tactile community, I searched online but I didn’t find it, is it a private community / a test community? I wanted to get some inspiration for my community :slight_smile:

3 likes

You should switch to stable before updating.

4 likes

How can we do this? (switch to stable) is it a simple task? I need to spend less time on updates and aftereffects of.

Is there a quick write-up or guide to this that you can link me to, please?

1 like

Richard answered this in another post. You want to wait for a stable release, then:

That said, tests-passed is strongly recommended. We use it on our own hosting.

3 likes

Yes, it’s an internal theme we’re working on atm. But glad you like the look :wink:

4 likes

Dus als ik vandaag version: stable instel in mijn app.yml en mijn site opnieuw bouw. Er gebeurt niets, toch? Hij blijft weken of maanden staan totdat 3.5.0 stable beschikbaar is, en pas dan wordt mij een upgrade aangeboden, correct?

1 like

Ja, we zullen ook beveiligingspatches uitbrengen voor de stabiele versie tussen nu en 6 maanden, dus je krijgt nog steeds enkele prompts om te upgraden, maar op die momenten, wanneer je upgradet, zal het je alleen vooruitspoelen in de stabiele branch naar de nieuwe patchversie.

2 likes