Today on meta.discourse.org…
Key Stats
In the last 24 hours, Meta saw 47 new posts across 3 new topics (plus continued discussion in several existing threads).
Top users (posts / likes in the last 24h):
| User | Posts | Likes |
|---|---|---|
| Moin | 7 | 15 |
| Lilly | 6 | 17 |
| NateDhaliwal | 5 | 4 |
| RGJ | 4 | 26 |
| merefield | 2 | 7 |
| pfaffman | 2 | 6 |
| sniper756 | 2 | 4 |
| Canapin | 1 | 5 |
| mcmcclur | 1 | 4 |
| keegan | 1 | 2 |
A lot of today’s energy clustered around UX friction vs. usability: infinite scroll controls, mobile typography, reaction discoverability, and composer behavior.
Interesting Topics
#Theme component
-
RGJ published a new theme component that adds a manual “Load More” button to interrupt infinite scrolling, positioning it as a compliance-friendly “manual input” step: Load More Button (discussion tie-in, read more).
-
Mobile ergonomics feedback came quickly: Canapin noted the button is hard to reach with a right thumb and suggested centering; Lilly shipped a centering SCSS snippet + PR that was merged: feedback and CSS fix (merge confirmation).
-
mcmcclur reported the button appearing even when there’s nothing to load (small/hidden-content site), and RGJ traced it to a core
canLoadMorepropagation issue rather than the component itself: bug report and core explanation. -
Docs and onboarding links got re-circulated alongside the release, including the canonical install and learning guides: How to install a theme/component and Beginner’s guide to using Discourse Themes.
General
-
The broader “is Discourse infinite scroll social media-ish?” debate continued, with RGJ’s practical counterpoint being “ship a workaround” (the new component), while others dug into scalability and UX patterns like “catch your breath” prompts after N scroll units: theme component drop-in context and scroll implications question (read more).
-
A concrete pointer surfaced: for “pause” nudges, there’s already a community option, though time-based (not scroll-based): Take a break theme component (referenced from this comment).
Support
-
A new support question asked whether admins can force exact characters on a single line (to keep a “clean” first paragraph look). The thread explored enforcement limits, user workarounds (multi-line), and the UX downsides of “exact length” constraints: question and cautionary take.
-
Several implementation avenues were compared: NateDhaliwal pointed to an older plugin, while Moin suggested form templates with min/max constraints (with caveats), and merefield recommended skipping plugins in favor of existing UI components: plugin link, form templates idea, and theme-component alternative.
-
Related references that shaped the solution space: discourse-characters-required, Creating form templates, and merefield’s Composer character count component (also referenced in follow-up).
ux
-
A new UX report claimed some hosted instances’ mobile font sizes got smaller (navbar + Suggested/Related), with Lilly suspecting the “modernized foundation” rollout being the differentiator: report and foundation theme hypothesis.
-
That complaint cross-linked into the main announcement thread, where Lilly argued the new foundation styles are “sleeker” and offered CSS snippets for users/admins who prefer larger text: cross-link post and CSS suggestions.
-
The long-running draft-save UX discussion continued: Moin highlighted inconsistent draft auto-saving (especially around thresholds/quotes), arguing the removed “save draft for later” affordance used to help users avoid silent loss: Nate’s clarification and Moin’s reproducible concern.
#Feature (completed)
- In the “show all likes/reactions” thread, Moin asked for better visibility into all reaction types (especially on communities with many emojis). NateDhaliwal noted you can horizontally scroll the tooltip—but the UI gives little indication that it’s possible: question and sidescroll explanation.
bug (composer ai)
- The AI docked composer fixes progressed: keegan referenced earlier fixes and queued improvements addressing editability and mobile quoting/sidebar issues, while clarifying the markdown/preview behavior as an intentional design choice due to space constraints: status + PR links and follow-up.
#Self-hosting
- The “bypass the 6 badge fav limit” discussion leaned toward “possible, but not wise.” pfaffman outlined that it’s easy via plugin or even
app.ymlreplace stanzas, then suggested an alternative: use group flair badges (via a theme component) instead of pushing badge limits: plugin/app.yml note and theme-based alternative.
#Theme component (icons + sorting)
-
Iconography polish request: Moin flagged confusing mirrored “previous/next” icons in edit history within the Lucide icons component, suggesting more intuitive paired designs: confusing icon pair.
-
A small enhancement request landed on “Created Topic Sort”: davidkingham asked whether the sorting option can persist when browsing a tag view, since the menu disappears there: tag-view question.
#Plugin
- The long-standing Calendar/Event thread got a big jolt: oshyan criticized the current settings/terminology sprawl and shared an early “event-focused” plugin prototype video after a few days of rapid iteration: prototype reveal.
development (dev-news)
- In the
.gjsmigration thread, jericson noted older plugin skeletons may also need the modern ESLint config file, pointing devs at the updated skeleton reference: eslint.config.mjs note.
Activity by the @team Group
-
keegan shipped updates on the AI docked composer bug thread, pointing to fixes already in-flight and a follow-up PR, and clarified why the docked composer favors RTE with markdown available but without preview: details + PR references (read more).
-
derek investigated a category badge text color regression caused by Foundation modernization styles overriding expectations, then provided a fix via PR to the badge styles component: root cause + PR (confirmation reply).
Yesterday’s vibe check: Meta collectively tried to click “Load More” less, while simultaneously asking for bigger fonts, clearer icons, and more visible reactions—a very on-brand day of UI debates.