Description
Define breakpoints tied to Vite / CSS usage; document in design-system README.
Requirements and context
-
Main max width behavior (960 today)
-
When to stack vault columns
-
Deliverables must be reviewable in Figma (or equivalent) and traceable to Disciplr-Frontend / design-system/
-
Should respect WCAG 2.1 AA targets for default theme unless explicitly scoped otherwise
Suggested execution
- Fork Disciplr-Org/Disciplr-Frontend and branch:
git checkout -b design/responsive-breakpoints
- Produce frames + specs (spacing, type, color, motion) before deep UI code changes
- Share a short Loom or PR description with before/after for stakeholder review
Design deliverables
- Breakpoint table
- Example layouts per breakpoint
Handoff
- Link Figma file + node IDs in the PR (or attach exports if Figma is not used)
- Note any updates needed in
design-system/tokens/*.json
Test and review
- Run a design critique (internal) with eng + design
- Validate keyboard + screen reader on affected flows (smoke level)
- Capture screenshots for light mode; note dark mode gaps if applicable
Example commit message
design: responsive breakpoints documentation
Guidelines
| Item |
Target |
| Figma / specs |
Named layers, intent documented |
| Accessibility |
Focus order, contrast, touch targets (min 44×44 px where applicable) |
| Timeframe |
96 hours from assignment |
Description
Define breakpoints tied to Vite / CSS usage; document in design-system README.
Requirements and context
Main max width behavior (960 today)
When to stack vault columns
Deliverables must be reviewable in Figma (or equivalent) and traceable to
Disciplr-Frontend/design-system/Should respect WCAG 2.1 AA targets for default theme unless explicitly scoped otherwise
Suggested execution
git checkout -b design/responsive-breakpointsDesign deliverables
Handoff
design-system/tokens/*.jsonTest and review
Example commit message
Guidelines