vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs: fix genuine passive-voice hits in docs/web-ui (small files)

Browse source 
agent.md, css-vars.md, design-guide.md, shape.md, terminal-rendering.md --
26 of 40 write-good.Passive hits rewritten to name the actor (hive-agent,
browsers, the harness, the client, lifecycle::{spawn,rebuild}, CSS, the
router, ...), reusing an actor already named nearby wherever one exists.
14 left alone: established config-state conditionals ("when X is
set/enabled/given/called"), negative-capability/state-descriptor idioms
("is gone", "is hidden", "is unchanged"), one false-positive
("typed slash commands" as a compound noun, not a passive action), a
backward-looking changelog fact with no actor worth naming, and two
deliberately-parallel rhetorical contrasts (sanitized vs XSS-safe;
cache-hit vs cache-miss) left symmetric on purpose.

dashboard.md (70 more hits) is the next docs/web-ui/ batch, not part of
this one -- big enough to deserve its own PR.
This commit is contained in:
iris 2026-09-08 14:58:43 +02:00 • committed by mara
commit e9d59f3d10
5 changed files with 43 additions and 43 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/web-ui/design-guide.md
View file

@ -89,7 +89,7 @@ needs a refresh story; a value that's silently gone stale with no way to
tell is worse than one that's visibly stale.
- **Relative-time labels must actually tick.** A label like "fresh (5s
ago)" is computed from a stored timestamp and re-renders itself on an
ago)" derives from a stored timestamp and re-renders itself on an
interval — never a value frozen at fetch time that quietly goes stale
while still reading as current. Pauses while its tab is hidden.
- **Pages that poll get a refresh-interval control, not silent
@ -143,8 +143,8 @@ just bare column headers floating over nothing.
## Component-first design
Build the `src/ui/` primitive before or alongside the first real page
that needs it, not after it's been styled inline and left for later —
a page reaching for a component that's already there has ready-made
that needs it, not after a contributor styles it inline and leaves it
for later — a page reaching for a component that's already there has ready-made
blocks to build with, instead of the next contributor duplicating
ad-hoc styling that someone then has to hunt down and consolidate.
`Panel`/`Badge`/`Table`/`TextField`/`SelectField`/`Button` are the