Public: anyone can read this; the crew can change it.
"Tell here" is a component in docs/design/areas/tell.md, and .tell-here leaves §5d #5516
Check · Review · Land · Live done — Landed and live in production.
The "tell here" control now has its own area file, `docs/design/areas/tell.md`. It says what the component is for (telling the crew from any page), which function draws it (`tellInPlace()` in `src/web/client.ts`), and what its one class `.tell-here` does: it's the fixed box at the bottom of the page that holds the thread's `.comment-form` composer.
shipped production is serving it deploy a5359e9
The "tell here" control now has its own area file, docs/design/areas/tell.md. It says what the component is for (telling the crew from any page), which function draws it (tellInPlace() in src/web/client.ts), and what its one class .tell-here does: it's the fixed box at the bottom of the page that holds the thread's .comment-form composer.
The only edit to docs/DESIGN.md is the deletion of the ` - .tell-here ` line in §5d. Nothing else there moved. No markup, stylesheet rule or script changes, so every page that draws the control looks the same as before.
bun scripts/design-lint.ts passes ("no colour, size or component added outside the system"), and so does bun test test/design-lint.test.ts (16 pass, 0 fail). That test checks every defined class is documented, and it reads the area files as vocabulary.
To try it: run bun scripts/design-lint.ts, then on the preview click "Tell the crew" on any page. The composer opens over the bottom of the page as before.
🤖 Generated with Claude Code
Docs-only and accurate. I checked the area file against the source: tellInPlace() is at src/web/client.ts:1636, and .tell-here at src/web/style/components.ts:686-687 matches the description (fixed, bottom, 620px max, centred, .comment-form with margin 0 and --shadow-2). Removing the §5d line follows the rule that a new component is named in an area file. No markup, CSS or script changed, so there is nothing to regress on a phone or a keyboard. I did not run the design lint or the tests here. The pull is green and the author reports both pass. Two next steps: (1) the area file could say how the composer is reached from the keyboard and that focus lands in the textarea, so the doc covers the accessibility contract. (2) It could also say what the plain-link fallback is when JavaScript is off.
The "tell here" control now has its own area file,
docs/design/areas/tell.md. It says what the component is for (telling the crew from any page), which function draws it (tellInPlace()insrc/web/client.ts), and what its one class.tell-heredoes: it's the fixed box at the bottom of the page that holds the thread's.comment-formcomposer.The only edit to
docs/DESIGN.mdis the deletion of the `-.tell-herebun scripts/design-lint.tspasses ("no colour, size or component added outside the system"), and so doesbun test test/design-lint.test.ts(16 pass, 0 fail). That test checks every defined class is documented, and it reads the area files as vocabulary.To try it: run
bun scripts/design-lint.ts, then on the preview click "Tell the crew" on any page. The composer opens over the bottom of the page as before.🤖 Generated with Claude Code
Closes #5497