Spacing between the console's parts follows no stated rule, and some gaps, like the trail's above the page title, read too tight #327
Open
opened 2026-11-06 19:39:51 +00:00 by cgalo5758
·
0 comments
Labels
Clear labels
accessibility
area/billing
area/catalog
area/discourse
area/domains
area/entitlements
area/fedwiki
area/identity
area/integrations
area/licensing
area/member-ui
area/meta
area/operator-ui
area/ops
area/testing
duplicate
good-first-issue
invalid
privacy
security
upstream
wontfix
A barrier for people using assistive technology or a keyboard alone.
The Stripe mirror, checkout, subscriptions, invoices, fulfillment.
Products, prices, plan ladders, purchasability.
The Discourse integration.
The domains registry, claims, placements, the certificate ask.
Entitlement sets, rules, grants, pools, provisioning.
The Federated Wiki integration and farm sync.
Sign-in, sessions, persons, organizations, workspaces, roles.
The provider registry, outbox and webhooks in general.
Licenses, the contributor agreement, SPDX headers.
Member pages.
The repository itself, its contributing guide, CI, the tracker and the workflow.
Operator pages, forms, lists, the design system.
Deployment, configuration, migrations, workflows, instance settings.
The test stack, screens, lint, walkthroughs.
Closed because another issue already covers it.
Small, self-contained, and explained enough to be a first contribution.
Closed because it is not a ticket for this repository.
Touches what a person's data reveals.
Touches authentication, authorization, secrets or data exposure.
Waits on another repository or project before it can move.
Closed because it will not be done, with the reason in the last comment.
kind
bug
The software does something other than what it promises; closed when it again does what it promises.
kind
debt
Code, tests or tooling to clean up with nothing visible changing; closed when they are cleaner.
kind
design
A question to settle before work can be defined; closed when the decision is written down.
kind
docs
Documentation that is wrong or missing; closed when it says the right thing.
kind
enhancement
Something the software does not do yet; closed when it does.
priority
critical
Blocks the active milestone or harms members now.
priority
high
Next in line inside the active milestone.
priority
low
Inside the active milestone, when nothing else is left.
priority
medium
Inside the active milestone, after the high ones.
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#327
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The question
What spacing system governs the console's layout: which grid or base unit, which step of Bootstrap's spacer scale goes between which parts, and how the system shows on both surfaces at desktop and mobile width?
docs/design-system.mdsays spacing comes from Bootstrap, with no token layer of its own. It does not say which spacer belongs between which parts, so each part and page picked its own margins. One gap already reads too tight: the location trail sitsmb-1(a quarter rem) above the page title inui_page_header.html, so the title crowds the trail. Other gaps are likely uneven in the same way: header to lead, lead to the row of views, a section header to its content, a list's controls to its table, a card's padding against the page gutter, and the stacked form families.What depends on the answer
pageHeader,sectionHeader,viewNav, notice and list-scaffold parts, whose margins every page inherits.mb-*,mt-*,gap-*andp-*in the templates. A rule lets a lint or a review decide whether a margin is right instead of judging it page by page.Options known so far
Decided when
docs/design-system.mdstates the spacing system: the base unit, which spacer goes between which kinds of parts, and the reason. The shared parts carry it. Every captured screen has been audited against it, at both widths, with each difference fixed or filed. The gap between the trail and the page title is part of that decision, not a one-off fix.