---
title: "A Crowded Item Page Made People Read Everything to Answer One Question"
canonical: https://dxdev.com/blog/2026-02-26_four-things-at-the-top/
datePublished: 2026-02-26
---
The item page answered one question, whether something was waiting on me, only after I 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, and that was the trouble: nothing was wrong with the page except that the answer was buried under everything true about it. Fixing that 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**.

The screen had started out as a busy page for one item. It had a status card, sliders, dates, related items, attached files, a history, and a footer full of extra facts. Every piece of it was accurate. That was part of the problem. When I opened the page to answer one question, whether something was waiting on me, I had to read through all of it to find the answer.

At first, I treated the page as a place to put every useful fact near the top. That did not work. It cost nearly two hours and four saved changes before the page finally matched the question it was supposed to answer. The fourth change was not even about moving information. It was about making the line between the main page and the extra material feel honest.

The work began one level up, in the list of items. Each item had been carrying a small pile of gray labels: 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. The result looked a little like the bottom of a crowded search result. You could read it, but it made the eye work harder than it should.

I replaced that pile with one short sentence. If the item was waiting on me, 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. That distinction turned out to be important. Making something simpler does not always mean deleting it. Often it means putting the frying pans back in the cabinet instead of leaving every pan on the stove.

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

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

After that change, 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 I can do right now?

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

The next pass exposed a problem I had missed. The top of the page still had extra labels beside the title. I had cleaned out the main card but left another pile of information in the header. So I 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. Intent can feel like a top-level fact. But making one exception invites another, and soon the page is crowded again. The boundary had to be clear enough to hold. The first screen was for the question at hand. The rest was one deliberate step away.

Then came the thin lines. Before the last change, Details was a little button beside a separator line. It worked, but it told the wrong story. A button suggests, “Here are some extra controls.” The new divider, with a small arrow and a line on both sides, says, “This is where the first part of the page ends. There is more below if you need it.”

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

The word **Details** now marks a promise more than a control: everything above the line is the four things that answer "what shape is this in, and can I act right now?", and everything below it is one closed-by-default click away. The proof is in the numbers. A change that added 165 lines and removed 145 from a file of about 310 lines did not add a single fact to the page or take one away, and yet the page went from making me read all of it to showing me the answer first. The thin line with the small arrow is where that answer ends and everything else begins.