---
title: "165 Lines Added, 145 Removed, and the Page Barely Changed"
canonical: https://dxdev.com/everyday-ai/four-things-at-the-top/
datePublished: 2026-03-02
---
The item page answered one question, "is something waiting on us?", only after we read through a status card, sliders, dates, related items, attached files, a history, and a footer of extra facts. Every one of those pieces was accurate. Nothing was wrong with the page except that the answer sat under everything else that was true about it. Fixing it took four saved changes, and the last one did not move a single fact. It only changed a thin line with a small arrow beside the word **Details**.

## Starting one level up

The work began in the list of items. Each [item carried a small pile of gray labels](/blog/badge-soup-to-one-human-sentence-state-aware-subtitle/): its types, a domain, sometimes a value badge, and a note about how long ago it changed. On a narrow screen those labels wrapped onto new lines. You could read it, but it made the eye work harder than it should.

We replaced the pile with one short sentence. If the item was waiting on us, it said "Waiting on you." If someone else had it, it said "Waiting on them." Otherwise it gave a simple age, such as "3 days ago."

Nothing was thrown away. The other facts moved to the item's own page, where they could still be found when they mattered. The same pans were still in the kitchen, just not all on the stove.

There is a technical name for this: **progressive disclosure**. It means showing the few things people need first, then making the rest available when they choose to go deeper.

## The status card

The next change was bigger. The status card at the top of the item page had been carrying nearly everything: the current state, who was waiting, a way to change the state, sliders, dates, related items, attached files, history, and extra facts. That one change added [165 lines and removed 145](/blog/progressive-disclosure-is-a-convergence-not-a-decision/) from a file of about 310 lines. It sounds large, but the page did not really grow or shrink. Most of the work was moving things from one place to another.

After it, four things stayed in view: a state icon, a state label, the waiting information, and the control for changing the state. They answered two immediate questions. What shape is this in? Is there something we can do right now?

Everything else went behind the **Details** line, closed by default. The sliders and dates were still important. So were the attached files and history. They just were not needed every time someone opened the page for a quick answer.

## The header we had missed

The top of the page still had extra labels beside the title. We had cleaned out the main card and left another pile of information in the header. So we cut the header back to the title, a back button, and a delete button. The types, domain, and intent joined the rest below Details.

That was uncomfortable for a moment, because intent can feel like a top-level fact. But making one exception invites another, and soon the page is crowded again. The first screen was for the question at hand. The rest was one deliberate step away.

## The thin line

Before the last change, Details was a little button beside a separator line. It worked, but it told the wrong story. A button suggests there are extra controls here. The new divider, with a small arrow and a line on both sides, says something else: this is where the first part of the page ends, and there is more below if you need it.

The hidden material did not change. The click did not change. What changed was the promise. That small visual difference made the page honest about what it had done with the information.

In the end, the four changes cost nearly two hours. The page went from making us read all of it to showing us the answer first, and it did so without adding a fact or removing one. If you run a business and your own screens have the same problem, check whether the first screen answers the one question people open it to ask. Put that answer and the next action in view, and keep everything else behind a clearly marked step that starts closed.