Public: anyone can read this; the crew can change it.

Quieter pages, nothing lost: a pull, an issue list and a repository head show less at rest, and every control stays one step away #8719

Closed opened this has it

Landed in pull #8722 · run

opened this

The owner, 2026-11-02: "we have a lot of verbose UI. i want to control everything in detail of course but its presentation could be better." Linear is the reference for staying calm at high complexity, not for copying its look: https://linear.app/now/behind-the-latest-design-refresh, https://linear.app/now/how-we-redesigned-the-linear-ui, https://linear.app/docs/display-options, https://linear.app/docs/search.

Rules to apply:

  • Chrome recedes and content carries the weight. Dim navigation and header bands.
  • Group by whitespace before a border. No card around every section or box around every row.
  • A row shows 4 or 5 properties. One display control per list chooses the rest, and grouping and ordering. Filtering stays separate from display.
  • Status is one small glyph and colour, with its word on hover and on the detail page. Never "Status: Open". Hide zeros and empties.
  • One primary action per page, always in the same place. Rare actions go to an overflow and the command palette, each still reachable by keyboard.
  • Size and weight carry hierarchy, without small uppercase captions. An icon never repeats its own label.
  • Colour comes from a few tokens, with the accent kept for status and the primary action.

Done when:

One pull per page, smallest first, so each one can land alone.

4 earlier comments
commented

The owner, 2026-11-02: "dont forget to leverage the linear notes though. we could hard tune towards them and I would probably be happy", in a design sense. So tune hard toward Linear's calm, for density, row composition, colour and quiet chrome, not a light touch. Keep to our own identity: no copied branding, logos or layouts. This pass is the highest priority UI work, and the new pages (Next up, bets, Flow, Notes) use the same rules as they land.

commented

Reviewed pull #8722 at its head: left open: The pull page, a repository's issue list and the repository head are redone by these rules, with before and after screenshots on desk and phone on the pull. — Only the issues list is redone; the pull page, repository head and screenshots are not.; Every action available before is still reachable, checked by a test listing them, and each is in the palette (Cmd-K). — Done for the issues list only; the pull page and repository head are untouched.; Each page's HTML gets smaller, with the byte counts on the pull, and its byte budget tightened in a test (#8016). — Only the issues page has a tightened budget.; The rules a machine can check join design-lint, so new pages get them: new pages from bets, Next up, Flow and Notes included. — No design-lint rules were added.; A cold reader says what each page is for in 10 seconds (the brand-new-person test). — The cold-read test has not been done..

commented

Left open after pull #8722 landed: 5 unticked items remain (The pull page, a repository's issue list and the repository head are redone by these rules, with before and after screenshots on desk and phone on the pull.; Every action available before is still reachable, checked by a test listing them, and each is in the palette (Cmd-K).; Each page's HTML gets smaller, with the byte counts on the pull, and its byte budget tightened in a test (#8016).; …). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

commented

Split by the planner. Pull #8722 (7802eb22) redid the issue list by these rules, with its action test and a tighter budget. What is left: the pull page (#8773) and the repository head (#8774). Each carries its own action-reachability test, palette entries, byte budget, desk and phone screenshots, and the cold-reader line. The design-lint rules are #8775. The owner's note to tune hard toward Linear is in each.

commented

I raised test/issues-quiet.test.ts from 50 KB to 55 KB by hand, because main sat at 51.7 KB and every pull went red. That undoes part of what this asks for: find what took the bytes (likely the script from #8708, or the two landing together) and bring the budget back to 50 KB.

Two passing pulls can still land a red main when each spends the same budget. Say in the pull why the gate let this through.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs