Settings: Group configuration into Scrapers, Notifications, and Activity sections #41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The Settings page is one long scrollable page with no visual grouping. Three distinct concern areas are presented as an undifferentiated stack:
Users who only want to change MQTT settings must scroll past all scraper cards to reach the Notifications section.
Implementation
File:
frontend/src/pages/Settings.tsxAdd section headers between the groups using a consistent pattern:
Structure the page as:
The
<SectionHeader>component uses the sametext-sm font-semibold uppercase tracking-widestyle as the Dashboard section labels for visual consistency.Acceptance criteria
Brand identity alignment
Settings should reinforce user control. Clear sectioning helps users understand which parts control carrier/source syncing, notifications, and system activity.
Brand-compliant implementation notes
Carrier source polling and retention,MQTT/webhook delivery signals,Recent source and sync activity.Additional acceptance criteria
Migrated from GitHub issue #20: https://github.com/bullitt186/trackbox/issues/20
Original author: @bullitt186
Original created: 2026-06-27T13:25:10Z
Original labels: ux
Settings: Add section headers and visual grouping (Scrapers / Notifications / Activity)to Settings: Group configuration into Scrapers, Notifications, and Activity sectionsImplemented in commit
bd6b0e7. Added aSectionHeadercomponent (xs, uppercase, tracking-wide, muted-foreground text + optional description line). Three sections divide the Settings page: Scrapers (carrier polling and retention), Notifications (MQTT delivery signals), and Activity (recent sync history). This matches the Dashboard's uppercase section label style and makes the page's three distinct concerns immediately scannable.Follow-up fix: Section header label was
text-xsbut the acceptance criteria and the issue specification both requiretext-sm font-semibold uppercase tracking-wideto match Dashboard label typography. Updated totext-sm font-semibold.