0f9d12c3cf
Adds docs/tasks/ (16 epics + 102 stories converted to task/subtask files with statuses.md as the new status source of truth) and docs/ux-design.md (retrospective design-system reference), and points CLAUDE.md at them. docs/prd.md and docs/architecture.md are kept as BMAD wrote them; the legacy docs/stories/, docs/epics/, docs/qa/gates/ and .bmad-core/ stay in place as historical/traceability records, superseded but not deleted. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2.1 KiB
2.1 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 10-5 | 10-5 Logo and SVG Assets Update | QA Review | 2026-09-27 | 10 |
Description
As a developer I want to update all logo files and SVG assets to match the new brand So that the application displays the correct LIBRA for Rights logo everywhere. Logo Files: - public/images/logo.svg - Primary full-color logo - public/images/logo-reversed.svg - For dark backgrounds - public/images/logo-mono.svg - Single-color version - public/images/logo.png - PNG fallback. Full implementation history: docs/stories/story-10.5-logo-assets-update.md
Acceptance Criteria
- AC1: Primary Logo Updated: Given
public/images/logo.svgcontains the old Scales of Justice logo with gold colors; When I update or replace the logo; Then the new botanical/wheat logo is displayed with correct colors: - AC2: Reversed Logo Updated: Given
public/images/logo-reversed.svgis for dark backgrounds; When I update or replace the logo; Then the logo displays correctly on Charcoal backgrounds: - AC3: Monochrome Logo Updated: Given
public/images/logo-mono.svgexists for single-color applications; When I update or replace the logo; Then the logo uses appropriate single color from new palette - AC4: PNG Logo Updated: Given
public/images/logo.pngis used in some contexts; When I update or replace the logo; Then the PNG matches the new SVG logo - AC5: Favicon Updated: Given the application has a favicon; When I review favicon files; Then they are updated to match new brand (if applicable)
- AC6: Logo Component References Correct Files: Given
resources/views/components/logo.blade.phpreferences logo files; When I review the component; Then it uses the correct logo variant based on context (light/dark background) - AC7: Logo Displays Correctly Throughout App: Given the logo appears in multiple locations; When logos are updated; Then they display correctly in:
- AC8: Logo Clear Space Maintained: Given brand guidelines specify clear space around logo; When logo is displayed; Then minimum padding/margin is maintained as per
docs/brand.md