Spec: Wholesale Coffee Sample Request UX

0

Spec: Route-Ready Coach Quote UX

0

Cover image for A clean-looking spreadsheet can still

A clean-looking spreadsheet can still hide a broken record trail. For this synthetic cleanup concept, I used four small rows so every correction could be traced: — 2026-07-03 and Jul 03 2026 resolve to one duplicate — Excel serial 46208 resolves to 2026-07-05 — the formula error is repaired without changing the valid rows — source count, removed duplicate, and normalized output reconcile in the QA ledger The signature element is the checksum seam. It keeps the raw rows visibly connected to the normalized table, because cleanup should preserve provenance rather than replace messy data with an unexplained polished sheet. This is self-initiated concept work built with plausible synthetic data, not a client result. It demonstrates a small, reviewable before/after workflow for spreadsheet cleanup and data-quality checks. Case study: https://contra.com/p/E7q7lFF3-concept-traceable-spreadsheet-cleanup

1

78

Cover image for Design-to-code handoff becomes fragile when

Design-to-code handoff becomes fragile when the mapping disappears between the component and the browser. For this concept workflow, I kept the implementation evidence connected from source to output: — the component anatomy stays tied to semantic HTML — the 24 px spacing token becomes --space-6: 24px — the primary CTA remains a real <a href="#scope"> link — the same structure is checked at 1440, 1024, and 390 px The signature element is the mapping spine. It links each Figma decision to its DOM, CSS, and responsive proof, making the handoff inspectable instead of presenting a generic “design turns into code” montage. This is self-initiated concept work using synthetic content, not a client result. It demonstrates the evidence trail I use when translating a supplied Figma landing page into responsive HTML and CSS. Case study: https://contra.com/p/YA6oNr7l-concept-component-mapping-to-responsive-htmlcss

1

23

Cover image for Responsive bugs rarely announce themselves

Responsive bugs rarely announce themselves at the desktop breakpoint.For this concept audit, I treated the landing page as an evidence trail rather than a cosmetic before-and-after:— breakpoint defects marked with redlines— overflow and contrast issues separated from layout noise— keyboard focus checked alongside visual hierarchy— every finding recorded in a compact QA ledger with a clear statusThe signature element is the red inspection trace. It connects each finding to the viewport and interface detail where the defect appears, so the recommended fix is reproducible rather than subjective.This is self-initiated concept work built with synthetic content, not a client result. It demonstrates the process I use for focused landing-page audits and responsive fixes.Case study: https://contra.com/p/sUb7M6oY-concept-breakpoint-evidence-and-landing-page-qa

1

26

Daniel

Web & Visual Design · HTML/CSS · Documents