BUILD PLAN · FOUR WORKSTREAMS
Four independent pieces. Two are quick and mechanical, two need decisions from you first. Nothing here is built yet.
{{ s.v }}
{{ s.l }}
Right now the page opens with "DEPLOY REDIS" and nothing else, then drops straight into a control-gradient axis and three dense option cards carrying eight data points each. A visitor who just wants to start cannot see where to click.
WHAT IS WRONG
PROPOSED TOP
NEW TOP, IN ORDER
Six layouts, each available in the brand palette, built as one Design Component with props so Qualified can activate any variant without new markup. Layouts are sized for both a page band and a chat-triggered overlay.
THE BRAND CONSTRAINT WORTH NAMING
The design system says one accent and one primary action per view (guide ยง1). A palette of colored CTAs is in tension with that, so the proposal is: Hyper red stays the only on-page primary, and the other colors are reserved for Qualified overlays, campaign landing pages, and offer bands where the CTA is the only action present. That keeps the rule intact and still gives you a full kit.
SIX LAYOUTS
COLOR VARIANTS · EACH LAYOUT TAKES ANY OF THESE
SWATCHES ABOVE ARE LIVE TOKENS, NOT MOCKUPS
Today the footer is five columns of chapter links and a legal line. It has no company section, no compliance row, no social, no region or language, and no newsletter. It is also the only shared component still template-only, so its links are hardcoded rather than read from content.js.
TODAY · 4 ROWS
PROPOSED · 7 ROWS
EXAMPLE · THE THREE NEW ROWS, RENDERED
Build's use-case rows already carry a 20px product glyph per pattern, masked to currentColor. The Build mega menu shows the same nine names with no icon. The mapping exists in BT_ROWS; it just is not in content.js, which is what the menu reads.
Icons and Deploy need nothing from you. The CTA kit and footer each need one answer.
{{ q.n }}
{{ q.q }}
{{ q.why }}