Visual design and theme #16

Closed
opened 2026-11-01 16:19:39 +01:00 by miko · 0 comments
Owner

Part of #1

Blocked by: #10

What

Own visual identity; look and layout like ifixit.com (clean, white, light-blue accent, image tiles), with no iFixit/Dozuki branding or assets. See ADR-0010.

Decisions (grilling 2026-11-01)

  • UI chrome stays neutral; photos and palette colours are the only strong colours. The accent appears only on buttons, links (always underlined), focus rings and active navigation — never as a dot/rectangle/circle near step lines.
  • Default accent blue (light blue like iFixit), applied via data-accent="blue" on <html>. Making it selectable is #17.
  • Light and dark mode: system by default, plus a Light/Dark/System switch stored in a cookie so the server renders the right class (no flash). Tailwind dark variant on a class/attribute selector.
  • One hex value per palette colour in both modes (annotations sit on photos). Annotations get a thin light/dark outline. Step-line bullets ≥ 3:1 against both backgrounds; if yellow/light-blue fail on white, add a ring rather than a second hex. black step lines render as the foreground colour in dark mode.
  • Typography: Inter via next/font (self-hosted at build).
  • Icons: Lucide (lucide-react). Caution triangle-alert, note info, reminder bell.
  • Accessibility target: WCAG 2.2 AA.
  • No component library; own lean Tailwind components. Headless primitives (Base UI / Radix) only when a later issue needs them.
  • Tiles for categories and guides: uploaded image (category image from #6, cover image from #18), otherwise a coloured tile — colour derived deterministically from the ID into a muted tile palette distinct from palette colours, with the title's initial and a category/guide icon. No fallback to step images.

Acceptance criteria

  • Semantic tokens in Tailwind 4 @theme (surface, surface-raised, fg, fg-muted, border, accent, accent-fg, danger, …) plus palette-red … palette-black, mapped from the stored names by a static table
  • Curated accent list (~6–8, default blue), each with checked light and dark values, defined per data-accent in the stylesheet
  • Muted tile palette for imageless tiles
  • Hex values (palette, accents, tile palette, neutrals) approved via a review page showing contrast ratios and a preview on a sample photo, a step-line list and a tile grid
  • Light and dark mode with cookie-backed switch; all colours legible on both
  • Inter and Lucide wired in
  • Category, guide and step reading views and the editor existing at that time styled consistently; later issues only consume tokens
  • Logo for kataba designed in review rounds (4–6 SVG drafts per round, shown light/dark, in header, as 16 px favicon and app icon; 2–3 rounds); final monochrome currentColor SVG (does not follow the accent), src/app/icon.svg, apple-icon.png

Vocabulary: GLOSSARY.md. Decisions: docs/adr/.

Part of #1 Blocked by: #10 ## What Own visual identity; look and layout like ifixit.com (clean, white, light-blue accent, image tiles), with no iFixit/Dozuki branding or assets. See ADR-0010. ## Decisions (grilling 2026-11-01) - UI chrome stays neutral; photos and palette colours are the only strong colours. The accent appears only on buttons, links (always underlined), focus rings and active navigation — never as a dot/rectangle/circle near step lines. - Default accent `blue` (light blue like iFixit), applied via `data-accent="blue"` on `<html>`. Making it selectable is #17. - Light and dark mode: system by default, plus a Light/Dark/System switch stored in a cookie so the server renders the right class (no flash). Tailwind `dark` variant on a class/attribute selector. - One hex value per palette colour in both modes (annotations sit on photos). Annotations get a thin light/dark outline. Step-line bullets ≥ 3:1 against both backgrounds; if yellow/light-blue fail on white, add a ring rather than a second hex. `black` step lines render as the foreground colour in dark mode. - Typography: Inter via `next/font` (self-hosted at build). - Icons: Lucide (`lucide-react`). Caution `triangle-alert`, note `info`, reminder `bell`. - Accessibility target: WCAG 2.2 AA. - No component library; own lean Tailwind components. Headless primitives (Base UI / Radix) only when a later issue needs them. - Tiles for categories and guides: uploaded image (category image from #6, cover image from #18), otherwise a coloured tile — colour derived deterministically from the ID into a muted tile palette distinct from palette colours, with the title's initial and a category/guide icon. No fallback to step images. ## Acceptance criteria - [ ] Semantic tokens in Tailwind 4 `@theme` (`surface`, `surface-raised`, `fg`, `fg-muted`, `border`, `accent`, `accent-fg`, `danger`, …) plus `palette-red` … `palette-black`, mapped from the stored names by a static table - [ ] Curated accent list (~6–8, default `blue`), each with checked light and dark values, defined per `data-accent` in the stylesheet - [ ] Muted tile palette for imageless tiles - [ ] Hex values (palette, accents, tile palette, neutrals) approved via a review page showing contrast ratios and a preview on a sample photo, a step-line list and a tile grid - [ ] Light and dark mode with cookie-backed switch; all colours legible on both - [ ] Inter and Lucide wired in - [ ] Category, guide and step reading views and the editor existing at that time styled consistently; later issues only consume tokens - [ ] Logo for kataba designed in review rounds (4–6 SVG drafts per round, shown light/dark, in header, as 16 px favicon and app icon; 2–3 rounds); final monochrome `currentColor` SVG (does not follow the accent), `src/app/icon.svg`, `apple-icon.png` Vocabulary: GLOSSARY.md. Decisions: docs/adr/.
miko closed this issue 2026-11-01 17:44:47 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
MassiveDynamic/kataba#16
No description provided.