Define homepage hierarchy inputs for interactive visual redesign #93

New issue

Open

opened 2026-08-04 17:42:32 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-04 17:42:32 +00:00

Collaborator

Design need

I am ready to reshape the homepage visual flow using Kai's design language, but the next visual decision depends on an unresolved portfolio hierarchy.

The current hero establishes one strong subject: Kai builds agentic engineering platforms. The portfolio then presents Infrastructure, Agent platform, and Product projects with nearly equal visual weight. I can improve styling and scanning without changing that model, but I should not use visual emphasis to invent a strategic priority.

Supplied facts

The homepage is intentionally project-first.
Its current sequence is platform thesis, then the active portfolio.
Projects are grouped into Infrastructure, Agent platform, and Product.
Repository descriptions and topics remain literal source content.
The site is static Eleventy and Sass with no browser JavaScript.
The visual direction should use disciplined focal control, modern cyberpunk identity, deliberate composition, and accessible states.
Interactive visual iteration will happen in a local live preview after these inputs are resolved.

Decisions I need

Please return a compact decision register covering:

Primary understanding - What should a first-time visitor understand about Kai after the hero and first portfolio group?
Primary next action - What should that visitor be drawn to inspect or do?
Portfolio story - How should the three project groups relate to the platform thesis?
Weighting model - Should projects remain equally weighted, or may one project dominate within each group?
Selection criteria - If emphasis is allowed, what evidence or rule selects the dominant projects?
Mobile priority - What must remain prominent when the catalogue becomes a single-column flow?
Content dependencies - Which existing title, tagline, group label, or project context needs a Content decision before design continues?
Unknowns - Name any remaining decision, its owner, and the evidence needed.

Design handoff

This input is complete when I can use it to produce focused visual-flow variants without guessing product strategy or writing unsourced portfolio claims. I will then compare the variants in the running site, keep gradient treatment unresolved until rendered comparison, and iterate on the selected direction with Kai.

## Design need I am ready to reshape the homepage visual flow using Kai's design language, but the next visual decision depends on an unresolved portfolio hierarchy. The current hero establishes one strong subject: Kai builds agentic engineering platforms. The portfolio then presents Infrastructure, Agent platform, and Product projects with nearly equal visual weight. I can improve styling and scanning without changing that model, but I should not use visual emphasis to invent a strategic priority. ## Supplied facts * The homepage is intentionally project-first. * Its current sequence is platform thesis, then the active portfolio. * Projects are grouped into Infrastructure, Agent platform, and Product. * Repository descriptions and topics remain literal source content. * The site is static Eleventy and Sass with no browser JavaScript. * The visual direction should use disciplined focal control, modern cyberpunk identity, deliberate composition, and accessible states. * Interactive visual iteration will happen in a local live preview after these inputs are resolved. ## Decisions I need Please return a compact decision register covering: * **Primary understanding** - What should a first-time visitor understand about Kai after the hero and first portfolio group? * **Primary next action** - What should that visitor be drawn to inspect or do? * **Portfolio story** - How should the three project groups relate to the platform thesis? * **Weighting model** - Should projects remain equally weighted, or may one project dominate within each group? * **Selection criteria** - If emphasis is allowed, what evidence or rule selects the dominant projects? * **Mobile priority** - What must remain prominent when the catalogue becomes a single-column flow? * **Content dependencies** - Which existing title, tagline, group label, or project context needs a Content decision before design continues? * **Unknowns** - Name any remaining decision, its owner, and the evidence needed. ## Design handoff This input is complete when I can use it to produce focused visual-flow variants without guessing product strategy or writing unsourced portfolio claims. I will then compare the variants in the running site, keep gradient treatment unresolved until rendered comparison, and iterate on the selected direction with Kai.

coilyco-ops added the

priority

autonomy

async-consult

labels

2026-08-05 10:26:30 +00:00

coilyco-ops referenced this issue

2026-08-10 20:08:02 +00:00

Surface /writing/ from the homepage #98

coilyco-ops added the

role/design

label