Naser Mansour
7f35297025
Naser confirmed all remaining QA Review / Draft rows (97 subtasks, 16
parent rollups) are done in substance: the site has been in production
for roughly a year. Overrides the conservative QA-Review/Draft mapping
from the prior takeover commit (0f9d12c) at his explicit instruction.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 10-1 | 10-1 Core CSS Theme Update | Done | 2026-09-27 | 10 |
Description
As a developer I want to update the Tailwind CSS theme color variables So that the application uses the new LIBRA for Rights brand palette. - resources/css/app.css - Main theme file. Full implementation history: docs/stories/story-10.1-core-css-theme-update.md
Acceptance Criteria
- AC1: Update Color Variables in
resources/css/app.css: Given the current theme uses Navy Blue + Gold palette; When I update the@themeblock; Then the following color mappings are applied: - AC2: Maintain Backward Compatibility Aliases: Given existing components use
navy,gold,creamclass names; When the theme is updated; Then aliases are created so existing classes continue to work: - AC3: Update Semantic Aliases: Given semantic aliases exist for components; When theme is updated; Then these mappings are correct:
- AC4: Update Button Styles: Given button classes use gold/navy colors; When theme is updated; Then
.btn-primaryand.btn-secondaryuse new palette: - AC5: Update Form Focus States: Given form inputs have gold focus rings; When theme is updated; Then focus states use Warm Gray:
- AC6: Update Prose Class: Given
.prose-navyclass exists for blog content; When theme is updated; Then rename to.prose-brandor update colors: - AC7: Status Colors Unchanged: Given status colors serve functional purposes; When theme is updated; Then these remain unchanged:
- AC8: WCAG AA Contrast Compliance: Given accessibility requirements; When new colors are applied; Then all text/background combinations meet WCAG AA: