- rename Go module, binary, systemd unit, PG_DATABASE default, frontend package and docs from shared-album to galo - add theme-aware halo emblem and favicon (new ui-branding capability) - add make build-release (versioned, stripped, static binary) and run the binary from the repo root
1.7 KiB
1.7 KiB
Tasks
1. Brand assets
- 1.1 Create
frontend/static/favicon.svgwith the halo mark (sun disc + separated ring) and embeddedprefers-color-schemedark/light variants, and verify it opens as valid SVG and renders legibly at 16px - 1.2 Create
frontend/static/favicon.png(fallback) andfrontend/static/apple-touch-icon.pngrendered from the same emblem, and verify both files exist at their intended pixel sizes (32x32 and 180x180) - 1.3 Update
frontend/src/app.htmlto referencefavicon.svgwith the PNG as fallback, and verifymake frontendcopies both intofrontend/build/
2. UI emblem
- 2.1 Add an inline SVG emblem component (disc in
--primary, ring in--primaryat reduced opacity, monochromecurrentColorfallback), and verify it renders at 16-24px with the ring and disc still distinct - 2.2 Verify the emblem changes color with the theme by switching light/dark/neutral and confirming the disc and ring follow the active theme
3. Placement
- 3.1 Show the emblem in the
AppShellheader next to the "Galo" wordmark and verify it appears in the main interface - 3.2 Show the emblem in the public/login layout and on the share page header and verify it appears on both
4. Accessibility
- 4.1 Verify every decorative emblem (next to the wordmark) is hidden from assistive technologies and any standalone emblem element has an accessible name
5. Integration verification
- 5.1 Run
make buildand verify the served favicon responds as an SVG image (curl -Ishows the SVG content type) and that no brand asset request returns 404 - 5.2 Validate the change and verify
openspec validate add-halo-brandingpasses