The sites card's header splits the disabled Create site button from its reason #322

New Issue

2026-11-02T07:40:31Z

cgalo5758 commented

2026-11-02 07:40:31 +00:00

What happens

When a workspace is at its site limit, or its allowance cannot be read, the FedWiki sites card's header row shows three items instead of two: the count at the left, the disabled "Create site" button in the middle, and its reason ("Site limit reached", or "Site creation is unavailable right now") at the far right. At 390px the reason touches the button with no space between them.

The header is a flex row that pushes its items to the two ends (d-flex justify-content-between, fedwiki_sites.html line 43). The disabled control part's visible variant (ui_disabled_control.html, the branch AsVisible selects) renders the button and its reason as two sibling elements, so the row treats them as two items. In a plan card, the variant's other caller, the card's body is a column, and the reason stacks under the button as intended.

What should happen

The disabled button and its reason stay together as one item wherever the part renders them, and the header keeps the count at the left and the control at the right, as it does when creation is allowed.

Where

The Visible branch of internal/embeds/templates/partials/ui_disabled_control.html; the header row of internal/integrations/fedwiki/templates/fedwiki_sites.html; SitesData.CreateControl in internal/integrations/fedwiki/web/partials.go.

Steps

A member whose workspace holds as many active FedWiki sites as its allowance opens the dashboard. The sites card's header shows the count, the disabled "Create site" in the middle of the row, and "Site limit reached" at the far right.

Why it matters

The reason is the one explanation a member gets for why they cannot create a site. Set apart from its button at the row's far end, it reads as an unrelated status rather than the reason the button is disabled.

### What happens When a workspace is at its site limit, or its allowance cannot be read, the FedWiki sites card's header row shows three items instead of two: the count at the left, the disabled "Create site" button in the middle, and its reason ("Site limit reached", or "Site creation is unavailable right now") at the far right. At 390px the reason touches the button with no space between them. The header is a flex row that pushes its items to the two ends (`d-flex justify-content-between`, `fedwiki_sites.html` line 43). The disabled control part's visible variant (`ui_disabled_control.html`, the branch `AsVisible` selects) renders the button and its reason as two sibling elements, so the row treats them as two items. In a plan card, the variant's other caller, the card's body is a column, and the reason stacks under the button as intended. ### What should happen The disabled button and its reason stay together as one item wherever the part renders them, and the header keeps the count at the left and the control at the right, as it does when creation is allowed. ### Where The `Visible` branch of `internal/embeds/templates/partials/ui_disabled_control.html`; the header row of `internal/integrations/fedwiki/templates/fedwiki_sites.html`; `SitesData.CreateControl` in `internal/integrations/fedwiki/web/partials.go`. ### Steps A member whose workspace holds as many active FedWiki sites as its allowance opens the dashboard. The sites card's header shows the count, the disabled "Create site" in the middle of the row, and "Site limit reached" at the far right. ### Why it matters The reason is the one explanation a member gets for why they cannot create a site. Set apart from its button at the row's far end, it reads as an unrelated status rather than the reason the button is disabled.

cgalo5758 added the

kind

bug

area/fedwiki area/member-ui labels 2026-11-02 07:40:31 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#322