Issue with Bespoke

ernestdefoe · 2026-06-06T14:56:08+00:00

@Claude_Bot this was reported by a user. body:has(.BespokeEditor) .AlertManager .Alert { margin-left: 350px; if(window.hljsLoader && !d...

Subarist

Claude_Bot

Attached screenshot for reference (3-tag case showing incorrect middle tag border-radius behavior):

Screenshot (3 tags CSS issue)

This shows the middle tag incorrectly retaining the full pill-style border-radius, breaking the grouped tag visual continuity.

Claude_Bot

Thanks for the detailed feedback, @Subarist — this is a thorough set of suggestions across Admin copy, BespokeEditor layout/UX, Palette/Type spacing and scaling, and Hero behavior. These are design and feature decisions rather than something I can action or commit to, so I'll flag this for the team to confirm and prioritize.

A few notes to help triage:

Quick wins (copy/labels): "Default preset for new installs" → "Default preset"; evaluating whether the "Apply the Bespoke theme to the forum" toggle is redundant given the extension can be disabled.
Behavioral/feature requests: editor occupying DiscussionListPane-style space, presets moved to the top, real-time preview + active preset indicator for Starter themes, Type base size affecting .Post-body, Hero height separated for DiscussionHero, and "follow tag color"/native fallback for Hero colors.
Possible bugs to verify: Type scale having no visible effect when adjusted.

Two things that would help the team review faster:

Confirm the Bespoke version and Flarum version these were observed on.
A quick screenshot for the layout/spacing items (editor layout, Palette spacing, Type scale) where visuals make the intent clearer.

I can't promise any of these will be implemented or estimate timelines — the team will weigh in on what's feasible.

Subarist

@Claude_Bot

Quick question on workflow:

Would it be better if I split each issue / suggestion into separate threads (one topic per post), so it’s easier for you and the team to manage, track, and prioritize them individually?

Or is it fine to keep related feedback grouped together as I’ve been doing so far?

Just want to align with the most efficient way for your triage process.

Claude_Bot

Thanks for the thorough rundown, @Subarist — here's a quick triage so the team can prioritize:

Quick copy wins:

"Default preset for new installs" → "Default preset"

Design/feature calls (for the team to evaluate):

Whether the "Apply the Bespoke theme to the forum" toggle is redundant since the extension can be disabled
Editor layout occupying DiscussionListPane-style space so the right-side view stays visible
Moving Presets above other options
Real-time preview + active selection indicator for Starter themes/presets
Palette spacing: .Bespoke-seg margin-bottom: 15px, button.Button.Button--block margin-top: 20px
Type base size affecting .Post-body
Hero: separating height to also support DiscussionHero; "follow tag color" / disable-to-native color options

Possible bugs (not preferences) — worth verifying:

"Type scale currently has no visible effect when adjusted" — reads like a defect
Hero height only applying to WelcomeHero

For those two, it'd help to confirm whether they're on Bespoke 2.0.22 / Flarum 2 RC2 (as in the earlier report) and note exact steps to reproduce, so the team can tell intended behavior from a defect.

These are design and feature decisions I can't action or commit to, so I'll flag all of it for the team to confirm and prioritize.

ernestdefoe

@Subarist I'll have these looked into this weekend.

Claude_Bot

Thanks @Subarist — noted. To recap for the team's triage:

Quick copy tweaks: "Default preset for new installs" → "Default preset."
Toggle review: whether "Apply the Bespoke theme to the forum" is needed given the extension can be disabled.
BespokeEditor: editor layout occupying DiscussionListPane-style space, moving Presets to the top, real-time preview + active preset indicator for Starter themes.
Palette: .Bespoke-seg margin-bottom: 15px; button.Button.Button--block margin-top: 20px.
Type: base size affecting .Post-body; type scale having no visible effect when adjusted.
Hero: separating Hero height to also support DiscussionHero; adding a "follow tag color" / native-fallback option for Hero colors.

These are design and feature decisions I can't action or commit to, so I'll flag all of it for the team to confirm and prioritize. One thing worth confirming for the team: the type scale having no visible effect sounds less like a preference and more like a possible defect — could you note whether that's expected behavior or something that should be working?

« Previous Page