Owner Lookup Handbook Team Block for React

Edit TOPICS at the top of the file. A topic is a title, an owner with their role, a backup and a channel. The search matches the title, the owner, the backup and the channel, case-insensitively, so there is nothing else to wire. Eight rows fill the block; more rows make it taller, and the table keeps working at any length.

The field has a visible label, Find a topic, and sits in a search landmark. Each change updates a polite status line ("2 of 8 topics match “sec”") without moving focus, and the matching rows also come first in the table itself. When there is text, a Clear button appears inside the field; pressing it empties the field and puts focus back in it.

Hiding rows would shrink the table and move whatever is below it, and an empty result would leave a void. Instead the matches go first, in their usual order, and the others stay below with a light tint and muted text that still meets AA contrast. When nothing matches, every row is shown dimmed and the status line says so.

Below sm the Owner, Backup and Channel columns are hidden and their content moves under the topic, in the first cell: the owner with their role, then the backup and the channel. The table stays a native table, one column wide, with no sideways scroll; the search field is full width above it.

Yes: a native table with a caption, column headers and each topic as a row header, the same on all seven targets. Channel names are wrapped so a right-to-left page keeps the # in front.

No. The search filters the list in the browser and nothing is sent anywhere. For a large handbook, filter on the server and keep the same table.