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
Owner

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.md says 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 sits mb-1 (a quarter rem) above the page title in ui_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

  • The pageHeader, sectionHeader, viewNav, notice and list-scaffold parts, whose margins every page inherits.
  • Every hand-set mb-*, mt-*, gap-* and p-* in the templates. A rule lets a lint or a review decide whether a margin is right instead of judging it page by page.
  • The screens baseline: an audit changes most captured screens at once, so it lands as one reviewed change.

Options known so far

  • A base unit mapped onto Bootstrap's spacer scale: a 4-point or 8-point grid, as most published design systems use (Material, Carbon, Atlassian), with Bootstrap's spacers (0.25, 0.5, 1, 1.5 and 3 rem) named by the relationship they express. No new token layer.
  • Rules by relationship rather than by part: related things close, separate groups further apart (proximity), one step of the scale per level of grouping. The trail and the title are one group, the header and the page's content another, sections a third.
  • Audit first: measure the gaps on every captured screen at both widths, list where the same relationship gets different spacing, then pick the rule that removes the most differences.
  • Research before choosing: the literature on layout grids and vertical rhythm, read for what fits a dense, Bootstrap-based console rather than a marketing page. Candidates: Müller-Brockmann's Grid Systems in Graphic Design, Refactoring UI's spacing chapter, Every Layout's modular scale, and the spacing pages of Material, Carbon and Atlassian.

Decided when

docs/design-system.md states 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.

## 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.md` says 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 sits `mb-1` (a quarter rem) above the page title in `ui_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 - The `pageHeader`, `sectionHeader`, `viewNav`, notice and list-scaffold parts, whose margins every page inherits. - Every hand-set `mb-*`, `mt-*`, `gap-*` and `p-*` in the templates. A rule lets a lint or a review decide whether a margin is right instead of judging it page by page. - The screens baseline: an audit changes most captured screens at once, so it lands as one reviewed change. ## Options known so far - **A base unit mapped onto Bootstrap's spacer scale:** a 4-point or 8-point grid, as most published design systems use (Material, Carbon, Atlassian), with Bootstrap's spacers (0.25, 0.5, 1, 1.5 and 3 rem) named by the relationship they express. No new token layer. - **Rules by relationship rather than by part:** related things close, separate groups further apart (proximity), one step of the scale per level of grouping. The trail and the title are one group, the header and the page's content another, sections a third. - **Audit first:** measure the gaps on every captured screen at both widths, list where the same relationship gets different spacing, then pick the rule that removes the most differences. - **Research before choosing:** the literature on layout grids and vertical rhythm, read for what fits a dense, Bootstrap-based console rather than a marketing page. Candidates: Müller-Brockmann's *Grid Systems in Graphic Design*, Refactoring UI's spacing chapter, Every Layout's modular scale, and the spacing pages of Material, Carbon and Atlassian. ## Decided when `docs/design-system.md` states 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.
cgalo5758 added the
kind
design
area/operator-uiarea/member-ui
labels 2026-11-06 19:39:51 +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#327