How to redesign a personal website without rebuilding it twice in the same month

Ivy is a fictional 28-year-old designer updating a personal site in Kamloops, British Columbia. Ivy’s current site is five years old. A new stack is tempting. The work samples that get her hired are buried. A talk next month needs a URL that does not 404. She keeps choosing typefaces instead of moving the case studies.

A Figma file, a repo, and a speaker URL all think they are the site.

Rebuilding on a new stack feels like craft and would miss the talk.

In You.one's Superboard view, Ivy can give “Ship a site that puts three case studies on the first screen before the talk, without requiring a new stack unless it fits the date” a Board of its own. That Board connects the project's purpose, materials, experiments, and the maker's judgment; opening “Choose restyle, one-migrate, or one-page” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Ship a site that puts three case studies on the first screen before the talk, without requiring a new stack unless it fits the date.

The consequential choice is not something a board or an AI should quietly make: Whether to restyle the current site, migrate one case study to the new stack, or ship a one-page site and postpone the rebuild.

You.one can keep the work, evidence, live dependency, and “Choose restyle, one-migrate, or one-page” decision visible through its Superboard view. The Owner boundary stays explicit: Ivy chooses the stack, writes the pages, and owns the deploy.

The Site before the talk Board gives this mission one durable operating picture. Ivy can use familiar language instead of translating the situation into project-management jargon. Its five Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Ivy's situation: “Choose restyle, one-migrate, or one-page” is the live choice, “Buried case study: library wayfinding” holds evidence, and “Talk listing URL next month” names something genuinely in motion outside Ivy's control. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Ship-path brief: Place talk date, buried case studies, and restyle / one-migrate / one-page options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Ivy will choose a ship path that hits the talk.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Ship-path brief and this Card Room's visible notes and left “Choose restyle, one-migrate, or one-page” with Ivy.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare restyling the current site, migrating one case study, and shipping a one-pager. Do not deploy or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.

Ivy's call remains explicit: Ivy chooses the stack, writes the pages, and owns the deploy.

These requests use the visible supported context inside the “Choose restyle, one-migrate, or one-page” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Ivy must provide the relevant facts and check the result.

Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Ivy, watch other Lists, or act outside this Card Room.

Ivy owns design, content, and deploys. Ava does not publish the site or write the case studies in her place.

A URL that works: three case studies are findable, a new stack is a chosen extra, and typefaces are not the project.

• Request idea: using only the context visible in this Card Room, compare restyling the current site, migrating one case study, and shipping a one-pager. Do not deploy or choose for me.
• Request idea: use only the Ship-path brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
• Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously

A Figma file plus a half-started new repo is enough when the work is already on the first screen.

It starts to break when a talk URL, buried case studies, and a new stack all claim the month.

The Site before the talk Board earns its place only when the familiar tool—a Figma file plus a half-started new repo—can no longer keep the reason, Ship-path brief, conversation, current state, decision, and history connected.

Ivy should rename every List or Card that feels artificial. This recipe succeeds when “Choose restyle, one-migrate, or one-page” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Later, Ava may help this Board notice when a talk Card is close and no case-study Card is on the first screen, still leaving every deploy with Ivy.

A future unified You.one experience could carry relevant context from “Choose restyle, one-migrate, or one-page” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.

• Ivy is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not a hiring, SEO, or traffic claim.
• It does not show Ava deploying a site or writing case studies.
• It is not a measured career result.