richie/Parsons
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update registry + session log — FuneralFinderV3 final state

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Richie
2026-03-26 19:49:08 +11:00
parent 0a309a0240
commit c5bfeaee2f
2 changed files with 28 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
docs/memory/session-log.md
View File

@@ -23,46 +23,46 @@ Each entry follows this structure:
## Sessions
### Session 2026-03-26f — FuneralFinder v3 build
### Session 2026-03-26f — FuneralFinder v3 build + polish
**Agent(s):** Claude Opus 4.6 (1M context)
**Work completed:**
- Created FuneralFinderV3 — clean vertical form approach based on user's Figma mockup (5919:29445)
- Two side-by-side StatusCards (Immediate Need / Pre-planning) replace V2's dropdown + step circles
- Glassmorphism container (backdrop-blur, semi-transparent white, warm-tinted border, deep shadow)
- Overline section labels (uppercase, brand-800) for "Current Status", "Funeral Type", "Location"
- Warm tonal field backgrounds (brand-100) with no visible border, no focus ring (per user request)
- Location input with location pin icon (LocationOnOutlined)
- CTA always active — validates on click, scrolls to first missing field (status or location)
- Created FuneralFinderV3 — clean vertical form based on user's Figma layout (5919:29445), restyled to FA design system
- Two side-by-side StatusCards (Immediate Need default-selected / Pre-planning), stack on mobile
- Standard card container (surface.raised, card shadow) — initially built with glassmorphism, user redirected to standard palette
- Overline section labels (text.secondary) for "How Can We Help", "Funeral Type", "Location"
- Standard outlined fields (white bg, neutral border, brand border on focus, no focus ring per user request)
- Location input with LocationOnOutlined pin icon
- CTA "Find Funeral Directors →" always active — validates on click, scrolls to first missing field
- Dividers after header and before CTA for visual rhythm
- Funeral type options: same as V2 + "Show all options"
- WAI-ARIA roving tabindex on radiogroup (arrow-key navigation between status cards)
- aria-labelledby via React.useId() for all fields
- Semantic token usage: border-brand, surface-warm, text-brand, interactive-focus, text-disabled
- Error messages conditionally rendered in aria-live regions (copper/brand tone, not red — gentle validation)
- First pass scored Critique 33/40, Audit 13/20
- Iterated on all P1-P3 findings, re-audit scored 18/20
- WAI-ARIA roving tabindex on radiogroup, aria-labelledby via React.useId()
- Semantic tokens throughout (border-brand, surface-warm, text-brand, interactive-focus, text-disabled)
- Error messages conditionally rendered in aria-live regions (brand copper tone — gentle validation)
- First pass scored Critique 33/40, Audit 13/20 → iterated on all findings → re-audit 18/20
- Polish pass: revised copy, fixed spacing, defaults, label rename
**Decisions made:**
- Status cards replace V2's step-circle + dropdown pattern — simpler, more visual, side-by-side on desktop
- Glassmorphism is a V3 differentiator — works over hero images, degrades gracefully to opaque white
- No sequential unlock — all fields accessible immediately (V2 locked steps until previous was filled)
- CTA always active (V2 disabled CTA until location was filled) — validates on click, scrolls to missing field
- Form simplified to 3 fields (status, funeral type, location) vs V2's 4 (intent, planning-for, type, location)
- "Planning for" folded into StatusCard descriptions rather than separate field
- Status cards replace V2's step-circle + dropdown — simpler, more visual, side-by-side on desktop
- Standard design system styling (user clarified Figma was for structure only, not colour scheme)
- "Immediate Need" selected by default — most common use case, status error essentially unreachable
- Section renamed from "Current Status" (programmatic) to "How Can We Help" (warm, human)
- Copy: "A recent loss or one expected soon" — "expected soon" differentiates from pre-planning gently
- Copy: "Planning ahead for yourself or a loved one" — "planning ahead" reinforces non-urgency
- No sequential unlock — all fields accessible immediately
- CTA always active — validates on click, scrolls to missing field
- Form simplified to 3 fields (status, funeral type, location) vs V2's 4
- Focus ring suppressed on Select/Input per user requirement — status cards retain focus-visible
- Error colour uses text.brand (copper) not feedback.error (red) — intentional gentle tone for funeral context
- Warm brand-tinted CTA shadow (brand.600 at 20% opacity) — no token for coloured shadows, commented
- Error colour uses text.brand (copper) not feedback.error (red) — intentional for funeral context
**Open questions:**
- User to review V3 in Storybook — compare against V1 and V2
- Location autocomplete integration still pending across all versions
- Consider adding component tokens for the glassmorphism treatment if reused elsewhere
- Decision: V1 vs V2 vs V3 for production
**Next steps:**
- User review of V3 in Storybook
- Decision: V1 vs V2 vs V3 for production
- If V3 chosen: location autocomplete, possible mobile refinements
- User to review final V3 in Storybook
- If V3 chosen: location autocomplete, possible further refinements
---