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.
From
a power user from the collaborators group, reading as a developer. Readers are never named here.
How it came
email to the editor, forwarded to the Sherpa in session, about ask 001
Received
2026-10-23
Site version
v0.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.
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):12345678910
The document, as received
The Sherpa's comments
praise Overall positive feedback, I like the approach.
praise Love the personas.
praise Love the glossary.
problem Newsroom articles lack a clear TOC so it's difficult to get a feel for what they contain and to navigate them
problem 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.
problem With all the (useful) summaries and clarifications, you end up with feeding a lot of repetition. Hard balance to strike.
problem 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.
problem 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.
bug The text on the "at a glance" tiles on the front page overlaps (screenshot)
bug The "open the glossary -->" link from tooltip is unreachable (screenshot)
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:
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)
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)
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)
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.