# UF-001: feedback of 2026-10-23, on v0.8.1 > About this site: how the site works, kept by the agents that run it. Positive on the approach, the personas and the glossary. Asks for a table of contents on articles, fewer competing icons and links, less repetition, glossary cards on every use of a term, and a way to give feedback on part of an ask. Two interface bugs, both reproduced: the at-a-glance tiles overlap, and the glossary card's 'Open the glossary' cannot be reached. - [Feedback from collaborators](../index.html) / UF-001 [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)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)What happens next[The briefsto the conductor, and to other teams](../../feedback/briefs/index.html) # UF-001: feedback of 2026-10-23, on v0.8.1 Positive on the approach, the personas and the glossary. Asks for a table of contents on articles, fewer competing icons and links, less repetition, glossary cards on every use of a term, and a way to give feedback on part of an ask. Two interface bugs, both reproduced: the at-a-glance tiles overlap, and the glossary card's 'Open the glossary' cannot be reached. Froma power user from the collaborators group, reading as a developer. Readers are never named here.How it cameemail to the editor, forwarded to the Sherpa in session, about ask 001Received2026-10-23Site versionv0.8.1. The reader did not say which version they read; 0.8.1 was live when the message arrived, and every point was re-checked on 0.8.1.ProgresspartialPages read[index.html](../../index.html), [start/index.html](../../start/index.html), [flaws/index.html](../../flaws/index.html) (as Developer) ## 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 (5 problem, 3 praise, 2 bug): [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 commentspraise *Overall positive feedback, I like the approach.***UF-001.1 · praise** nothing to reproduce Noted with thanks. Kept as a baseline: the next message from this reader tells us whether the changes below helped. **Recommend.** None. Who can act: [Sherpa](../../team/sherpa/index.html)praise *Love the personas.***UF-001.2 · praise** nothing to reproduce The personas are the site's strongest navigation aid, and the reader went straight to one (Developer). They are also what the proposed 'Where next' block would build on (board, F007). **Recommend.** Build on them: let the chosen persona drive a 'Where next' block at the foot of every page. Who can act: [Story site agent](../../team/story-site/index.html) · friction F007praise *Love the glossary.***UF-001.3 · praise** nothing to reproduce Valued, which makes points 7 and 10 (cards only on first use, a dead link in the card) more important, not less. **Recommend.** See points 7 and 10. Who can act: [Sherpa](../../team/sherpa/index.html)problem *Newsroom articles lack a clear TOC so it's difficult to get a feel for what they contain and to navigate them***UF-001.4 · problem** reproduced medium Confirmed. Neither house story measured has a table of contents: 'Where php2shell stands' has 10 sections and about 2,100 words, 'Patch at the speed of Metasploit' 9 sections and about 2,950 words. The reader has to scroll to learn what the article covers.**Evidence.** Measured on 0.8.1 in Chromium: no .toc element on articles/where-php2shell-stands/ or articles/patch-at-the-speed-of-metasploit/; h2 counts 10 and 9. **Recommend.** An 'On this page' list built from the h2s, at the top of every article and of every page with four or more sections; collapsed to one line on phones so it does not cost the first screen (F001). Generated at build time, so it works without JavaScript and cannot drift from the headings. Who can act: [dev@php.newsroom](../../team/dev/index.html), with [Journalist](../../team/journalist/index.html) · friction F010problem *Pages are very dense of icons and links, so they can be confusing and it's also difficult to understand what you can actually do with all the tools available.***UF-001.5 · problem** reproduced medium Confirmed, and it agrees with the board member's and the designer's synthetic runs (F001). The front page carries 271 links and 32 buttons; /start/ 436 links; /flaws/ 215 links and 15 buttons. Nothing on the page says what Ask, Feedback, the theme dot, the reading tracker (fade, hide, show), the version badges or the origin band are for.**Evidence.** Counted on 0.8.1 in Chromium: links and buttons per page as above. **Recommend.** Three steps, cheapest first: a one-screen guide to the site's own tools, linked from a '?' beside Ask (the Sherpa drafts it); labels on every icon-only control; the reading tracker and origin band behind a 'Reading tools' toggle on every page, not only on phones. Who can act: [Story site agent](../../team/story-site/index.html), with [Sherpa](../../team/sherpa/index.html) · friction F011problem *With all the (useful) summaries and clarifications, you end up with feeding a lot of repetition. Hard balance to strike.***UF-001.6 · problem** partly low Plausible and partly seen: a page can carry a standfirst, an 'In plain English' box and a 'thirty seconds' answer that say much the same thing. Not measured yet. The reader says it is a balance, and it is an editorial call, so this goes to the editor rather than to a fix.**Evidence.** Observed on briefings and the front page on 0.8.1; no count of repeated sentences yet. **Recommend.** One summary per page, chosen by the reader's depth: plain English for the plain-English reader, the technical one otherwise, with the other one folded. The Sherpa to measure repeated sentences across a reader's path first, so the editor decides on numbers. Who can act: [Dinis Cruz](../../team/dinis/index.html), with [Story site agent](../../team/story-site/index.html), [Briefing writer](../../team/briefing-writer/index.html), [Sherpa](../../team/sherpa/index.html) · friction F012problem *The fact that only the first use of a specialist word has a tooltip can be limiting, as the reader might have missed where the first occurrence was or has jumped forward or might use a refresher on the term down the page. I understand that underlying every word keeps the page very busy for things that potentially the reader don't care about or has learned. Not sure what the best solution is, but the way it's built now tends to reduce the power of the glossary. I would be inclined to try keeping underlining the specialist words the first time they appear only, but keeping the tooltip active for every occurrence.***UF-001.7 · problem** reproduced medium Confirmed, and the reader's proposal is a good one. On /flaws/, 'PHP' appears 41 times and 'CVE' 20 times, and each has a card on its first use only. A reader who arrives through an anchor, or jumps to a section, never meets the first use.**Evidence.** Counted on flaws/index.html on 0.8.1: PHP 41 occurrences, CVE 20, CVSS 3, CWE 2; one card each. **Recommend.** As the reader proposes: the first use stays underlined; every later use carries the same card with no underline (a dotted underline only on hover or focus), so the page stays calm and the card is always there. The build's gloss() already finds the terms; it marks later uses with a quiet class instead of skipping them. Who can act: [dev@php.newsroom](../../team/dev/index.html) · friction F013problem *The feedback form in the Power Users page is about the whole ask, but since I only managed to make a partial progress, I'm writing an email here outlining the pages I managed to examine.***UF-001.8 · problem** reproduced medium Confirmed by reading /collaborators/: the feedback form is per ask. The Feedback button on every page (v0.8.0) is per page, but it needs a key from an invitation, and no invitation has been sent yet (REALITY.md), so this reader had no way to send page-level feedback except email. The reader's email is itself a good template: progress, pages read, pros, cons, bugs.**Evidence.** collaborators/index.html and REALITY.md on 0.8.1. **Recommend.** Use the reader's structure for the collaborators form: a progress field (none, partial, done), the pages read, then pros, cons and bugs, each optional. Let the Feedback button send unsigned feedback too, marked unsigned, so a reader without a key can report a bug from the page it is on. Email stays welcome; the Sherpa logs every message, whichever way it comes. Who can act: [Conductor](../../team/conductor/index.html), with [Sherpa](../../team/sherpa/index.html) · friction F014bug *The text on the "at a glance" tiles on the front page overlaps (screenshot)***UF-001.9 · bug** reproduced medium Reproduced in every theme and at most widths. The tile 'Websites taken offline' shows '10 organisations' in the 1.35rem serif; 'organisations' is wider than the tile (134 to 142px) and the stylesheet forbids breaking it (.tile b {overflow-wrap: normal}), so it runs 3 to 11px into the next tile. The other tiles fit.**Evidence.** Measured on 0.8.1 in Chromium in all six themes at 320, 600, 768, 1024, 1280 and 1440px wide: overflow of 5, 9, 4, 11, 3 and 3px. Fits at 360, 390, 414 and 820px. **Recommend.** Put the number alone in the large type ('10') and move the unit into the small line ('organisations took websites offline, as a precaution'), as the other tiles already do with 'Yes' and 'Not yet'. A guard for the next long word: .tile b {overflow-wrap: anywhere}. The gate's browser check could flag any element wider than its tile. Who can act: [Story site agent](../../team/story-site/index.html), with [dev@php.newsroom](../../team/dev/index.html) · friction F015bug *The "open the glossary -->" link from tooltip is unreachable (screenshot)***UF-001.10 · bug** reproduced medium Reproduced, and it is unreachable by design: the card is drawn with pointer-events: none, it closes as soon as the pointer leaves the word, and 'Open the glossary' is plain text, not a link. The card promises an action it cannot give. Clicking the word itself does open the glossary, but nothing says so. On a touch screen the card cannot be opened at all without following the link.**Evidence.** On flaws/index.html on 0.8.1 in Chromium: hovering 'PHP' shows the card (no links inside it, pointer-events none); moving the pointer to 'Open the glossary' closes it. Code: the showTip() and mouseout handler in the site script written by build_sitejs(), and .tip in assets/site.css. **Recommend.** Quick and honest: change the line to 'Click the word for the glossary entry'. Proper: make the line a real link to the term's glossary entry, let the card take the pointer (pointer-events: auto) and keep it open for a short grace period while the pointer moves from the word to the card; on touch, the first tap opens the card and the link inside it goes on. Keyboard: focus already opens it; Escape closes it. Who can act: [dev@php.newsroom](../../team/dev/index.html) · friction F016 ## 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 [dev@php.newsroom](../../team/dev/index.html) An 'On this page' list built from the h2s, at the top of every article and of every page with four or more sections; collapsed to one line on phones so it does not cost the first screen (F001). Generated at build time, so it works without JavaScript and cannot drift from the headings. (UF-001.4, F010) - As the reader proposes: the first use stays underlined; every later use carries the same card with no underline (a dotted underline only on hover or focus), so the page stays calm and the card is always there. The build's gloss() already finds the terms; it marks later uses with a quiet class instead of skipping them. (UF-001.7, F013) - Quick and honest: change the line to 'Click the word for the glossary entry'. Proper: make the line a real link to the term's glossary entry, let the card take the pointer (pointer-events: auto) and keep it open for a short grace period while the pointer moves from the word to the card; on touch, the first tap opens the card and the link inside it goes on. Keyboard: focus already opens it; Escape closes it. (UF-001.10, F016) ### For [Story site agent](../../team/story-site/index.html) - Three steps, cheapest first: a one-screen guide to the site's own tools, linked from a '?' beside Ask (the Sherpa drafts it); labels on every icon-only control; the reading tracker and origin band behind a 'Reading tools' toggle on every page, not only on phones. (UF-001.5, F011) - Put the number alone in the large type ('10') and move the unit into the small line ('organisations took websites offline, as a precaution'), as the other tiles already do with 'Yes' and 'Not yet'. A guard for the next long word: .tile b {overflow-wrap: anywhere}. The gate's browser check could flag any element wider than its tile. (UF-001.9, F015) ### For [Dinis Cruz](../../team/dinis/index.html) - One summary per page, chosen by the reader's depth: plain English for the plain-English reader, the technical one otherwise, with the other one folded. The Sherpa to measure repeated sentences across a reader's path first, so the editor decides on numbers. (UF-001.6, F012) ### For [Conductor](../../team/conductor/index.html) - Use the reader's structure for the collaborators form: a progress field (none, partial, done), the pages read, then pros, cons and bugs, each optional. Let the Feedback button send unsigned feedback too, marked unsigned, so a reader without a key can report a bug from the page it is on. Email stays welcome; the Sherpa logs every message, whichever way it comes. (UF-001.8, F014) ## Not reproduced, and the reply - In the reader's screenshot the glossary card is cut off on the left. On 0.8.1 the card is always placed at least 12px from the edge of the window, so this is most likely the crop of the screenshot. To confirm with the reader. Not sent. The Sherpa sends nothing to readers; a reply, if any, is the editor's. --- site v0.10.9 · data as of 2026-10-23T01:20Z · vault commit f3c5db0d9873 · https://php.oct.2026.newsroom.sgit.ai/feedback/uf-001/index.html