Driving a Website Redesign From Notion: A Brief-to-Component Workflow

Iterating on a live marketing site usually means a messy loop of screenshots, comments, and "the bit below the pricing table". For one product site, that loop was replaced with a single Notion board where every row is a real section of the site, already wired to the component that renders it.

One row per section, mapped to code

The board has a row for the hero, a row for pricing, a row for the footer, and so on. Each row carries the name of the actual component file in the repository, a short note describing the current state of that section, and an empty field for the new direction. There is no ambiguity about which part of the site a brief refers to, because the row is the part of the site.

The brief is free-form on purpose

The direction field takes whatever the owner wants to put in it: a copy change, a layout change, "make this feel more premium", a link to another site as a reference, or a completely different idea. Precision is welcome but not required. A loose prompt with a clear target section beats a precise prompt about an unclear one.

Status drives the work

Each row has a status. When it is set to ready, that row is in scope. The build step reads every ready row at once and works them in parallel where they touch different files, in sequence where they would collide. When a section is done, its status flips to done, or to needs review with a note, and its component file field is filled in if it was a new section.

Why this beats a comment thread

• Scope is explicit: only ready rows get touched, so a half-filled board is safe to leave.
• Nothing gets lost, because feedback lives on the section it concerns, not in a scroll of chat.
• Parallel work is safe, because the file mapping shows what can run together.
• History is per section: you can see how the hero has evolved without reading the whole project’s history.

It also makes priority the owner’s lever, not a negotiation. Rows have a priority field, and that is the running order.

The baseline it works against

The board assumes a known starting point: on this site, a shipped motion system, a social proof section, an accessibility pass, and a voice and copy pass. Every current-state note describes that baseline, so a brief is always understood as a change from a known thing, not from a guess.

Related