The drawer rebuild
"Puffy and incomplete" turned out to be measurable, and reading the file closely found a variable collision that had been dimming the homepage for weeks.
What we were doing. The drawer felt bloated and looked unfinished next to the homepage. Both complaints turned out to have specific, checkable causes rather than being matters of taste.
Why it felt puffy
.drawer-nav set gap: 20px between every child. Because the headings and dividers sat directly inside that <ul>, they collected the gap too. Each divider then added margin: 25px 0 on top, so one divider cost about 90px, and there were three.
Meanwhile the links had no padding at all: bare 19px text lines floating in large voids, with tap targets roughly half the recommended size. Puffy and flimsy simultaneously, which is a specific combination produced by putting the space between things instead of inside them.
| Before | After | |
|---|---|---|
| Row height | 37px | 32px |
| Gap between sections | 18px | 30px |
| Per link | ~80px | 63px |
| Total height | 1077px | 1041px |
Shorter overall while carrying four more entries and reading as four distinct blocks.
The bug nobody was looking for
drawer.css and style.css both defined --text-muted on :root. The drawer loads second, so its dimmer #565f89 silently overrode #9aa4ff for the entire document. Three rules in grid.css consume it, so the homepage card text had been rendering darker than designed.
Nothing was broken. Nothing errored. The page simply looked slightly wrong in a way that is almost impossible to notice without comparing to intent. Every drawer variable is now namespaced --dr-*.
Other things found by reading it
- A stray
>rendering as literal text. - An orphan
</span>with no opening tag. - A double slash in
/content//ai/. <h3>,<h4>and<div>as direct children of<ul>, which is invalid and breaks list semantics for screen readers.- An
xmlnsattribute containing a pasted markdown link. - SMIL
<animateTransform>and CSS keyframes both animating the same elements.
On the palette
The rebuild gave each category the homepage's accent color. The reaction was that it looked like a rainbow popsicle, and that was right for a reason worth keeping: the visual hierarchy was inverted. The loudest elements were the category labels, which are pure metadata, while the links people actually click sat in quiet gray.
Fixed by moving color into a 2px bar and dropping the labels to metadata weight. The coding survives, the links become the loudest text, which is what a navigation menu is for.
What would catch it sooner
Two stylesheets defining the same custom property on :root is a silent conflict. Namespace per-component variables from the start. The cost of a prefix is nothing; the cost of finding this by accident, weeks later, was this session.
And "it feels off" is usually measurable. Every complaint here resolved to a number or a specific line.