Visual re-skin (navy / copper / mono) - page-by-page token restyle¶
| Stage | Building |
|---|---|
| Status | Partial |
| Design status | In progress |
| Estimate | 3w (M-L) |
| Confidence | Medium |
| Linear | PIN-687 ↗ |
| Linear status | QA |
| Design | Design ↗ |
| Linear epic | Platform Foundation |
| Module | Settings & Admin ↗ |
Priority: Medium
Scope¶
Page-by-page visual restyle across every module (Bids, Projects, Estimate Sheet, Vendor/Client/BMS lists, etc.) to the new navy/copper/mono token set, driven by Conor's design review of each page's MkDocs walkthrough before Mateo implements it. Rolled out in order: Daily Log, BMS directory, Analytics, then the rest. (Source: PIN-687.)
Acceptance criteria¶
- Each page restyled only after Conor has reviewed and signed off on its design doc
- Rollout order: Daily Log to BMS directory to Analytics, then remaining modules
- Includes bid detail, project handoff, form-consistency pass, font-size consistency, and estimate-sheet toolbar restyles
- Vendor/client list restyle already shipped as the reference pattern
- No restyle build starts on a page until its full design file is delivered
Conor's comments¶
I would like the design UI as its own tracking table for each page with my final sign off and build date.
Notes¶
Rec post-pilot; Mateo out ~3 weeks in August
Open question for Conor¶
Pilot requirement or post-pilot?