Three findings from an external review of the web UI, verified against v1.34.0.
- A signed-out phone has no route to the listing. Explore's rail square
is
.railopt, so it hides below 34rem, and the More menu that holds the dropped squares is rendered only for a signed-in viewer. The footer carries no link either, so the only way to/exploreis the landing page's button or typing the path. /register's "Make one" link leaves the page for the SSH-keys wiki page, on another origin, over a half-filled form and with no way back. It also hardcodeshttps://gitbay.org/..., so on any other instance it points at this one.- An empty
/searchsays the same thing twice:0 results for <q>in the head andno matches for <q>under the form, and offers no way on.
Reviewed and not taken:
- Labels on the rail at desktop width. Icon-only is the decision in
#226; every square carries an
aria-label, a visually hidden name and atitle. Reopen it against the newcomer walk, not this. - Descriptions under names on explore at desktop width. That reverses
rule 4 of
docs/specs/2026-09-19-desktop-layout-design.md. The case for an explore-only exception is that explore is the one list whose readers do not know the repositories, so the description is content rather than metadata; worth a decision, not a drive-by. - The landing picture's dark frame showing a closed !315. Both frames were reshot in 0d66697 and show !450 merged with its approval.
- Moving the builds page's "Status badge" box. It is a collapsed
32px
details.editbox, the same shape as "New release" and the account key boxes. - Labelling explore's topic chips as topic searches.
qis one field matching name, description and topics, so there is nothing to clobber; the mismatch is that a chip labelledgoalso returns repositories that merely mention "go". A real fix is atopicparameter.
closed by cmc in commit cf204d6198: web: an empty search says what to do next
2026-09-22 05:34 UTC