⚑
Content Studio Β· Planning Β· July 2026

Start here

The engine works. What's left is the wrapper. This is the front door to that work: why we're redesigning the UI, what we decided, and every screen it touches. Every other page in this folder hangs off this one.

154
observations from Jill's walk-through
β†’
7
design rules (decide once)
8
module cleanups (design once)
11
real bugs (fix regardless)
1 of 8
modules already designed (Blog)
How to read this folder. There are two tracks, and they answer different questions. The direction (Redesign Map, Blog Brief) says what we're changing and why. The system (Site Map plus nine module pages) says what the thing actually is, screen by screen. The direction sets the rules. The system is where they land. Start with the direction, then walk the system.

The whole picture

Two tracks, one destination. Every box below is a page in this folder, and every box is clickable.

THE DIRECTION β€” why it changes THE SYSTEM β€” what changes 154 observations Jill's walk-through of the live app regrouped into the shape of the work UI Redesign Map the 154, sorted into three tracks 7 RULES 8 MODULES 11 BUGS module 1, designed first Blog Automation Brief Jill's card pipeline, adopted as the spec Site Map three layers: admin Β· app Β· systems opens into Planner Blog βœ“ Social Newsletter Landing CRM Intake Media Admin Seven modules to go same rules, same shapes, one at a time the 7 rules apply to every one the shape the other seven copy Left: the thinking. Right: the surfaces. The dashed lines are the whole argument.

Click any box to open that page. The nav bar at the top of every page brings you back here.

Track 1 Β· The direction

Two documents. The first says what we're changing across the whole app. The second is the first module, already designed.

The plan

UI Redesign Map

Jill's 154 observations weren't a to-do list. They were the same few decisions showing up over and over. This regroups them into the shape of the work.

  • The 7 rules β€” decide once, apply everywhere. Most of the board disappears here.
  • The 8 module cleanups β€” what's actually left per module once the rules are assumed.
  • The 11 real bugs β€” separate track, fixed no matter what the UI looks like.
  • How we work it β€” rules first, then module by module, bugs in parallel.
Read this one first
The proof

Blog Automation Brief

Module 1 of 8, designed by Jill from live use of the platform. It independently landed on rules 1, 2, 3 and 4, which is the strongest signal the rules are right.

  • Card home replaces the filter-and-table dashboard.
  • Create β†’ Draft β†’ Review β†’ Schedule β†’ Post, one stage per post, one button forward.
  • Screen by screen spec, including the reopen-a-scheduled-post behavior.
  • 5 open questions that need Erick's answer before build.
βœ“ Adopted β€” design credit: Jilly, Sage Coast Realty

Track 2 Β· The system

What the product actually is, from a UI perspective. These pages are the ground the redesign stands on, and the reference for every module conversation. These pages show the real mechanics for the team (WordPress, GoHighLevel, Gemini). The customer never sees those names in the product. That is Rule 1.

Start of the track

Site Map

The whole product on one page, top to bottom: who can see it, what the team works in, what it runs on and talks to.

  • Layer 1 β€” Admin. The control plane.
  • Layer 2 β€” The App. The daily workflow surface.
  • Layer 3 β€” Systems. Docker, the AI path, and every integration.
The module pages

Nine screens, nine pages

One page per module, each showing how that surface works today and what it's for. This is what a module design conversation opens with.

What this meeting is for

Four things, in this order. The first one is the whole meeting; the rest follow from it.

1

Lock the 7 rules

Agree them once, together, on the Redesign Map. They cut across every module, so deciding them up front stops each redesign from re-arguing the same point. Everything else waits on this.

2

Confirm Blog as the template

Jill's brief is adopted. Walk it once, answer the five open questions, and it becomes the shape the other seven modules copy. One module designed, seven to go.

3

Walk the system

Site Map first for the three layers, then the module pages as we need them. Each module gets a short design chat, one decision, one focused build session. Not all in this meeting.

!

The bug track runs in parallel

Eleven real bugs, led by CS-100 (Clear Week permanently deletes a pending post). They get fixed regardless of what the new UI looks like, so they never sit waiting on a design decision.

  1. Decisions needed from Erick. Status mapping (how today's statuses land on the new cards), whether a real review workflow exists today, and the Blog editor sidebar fields. All three are in the Blog Brief, section 7.
  2. Help chatbot: build or embed? Jill asked for it in the Blog spec, but it spans the whole app. Parked as a cross-cutting roadmap item pending that call.
  3. Scope check. The redesign's "8 module cleanups" and the Site Map's app modules are two different lists (the cleanups include Settings and fold Intake in elsewhere). Worth reconciling out loud so the count means one thing.
Nothing Jill did is lost. Every line in the direction track came from her walk-through. These pages just regroup her 154 observations into the shape of the work: a few rules, a few module redesigns, a short bug list. Her notes stop being a backlog and become the spec.