docs: give the documents table its own section in the 0.8.6 blog post

[nicoloboschi]

The 0.8.6 blog post under-sold #3049. It mentioned only "tag filtering on documents" in passing, when that PR also reworked the documents table itself and unified how tags, entities, and metadata render across the control plane.

Changed

The documents list now gets its own section — ## A Documents Table Built for Scanning, after the entity timeline section — led by a screencast of the tag filter in use, with four bullets:

• Filter by tag — autocomplete plus an any/all toggle, on a list that previously offered only document-ID search.
• A table organized around what you scan for — last-updated under the document ID, tags and metadata sharing a column, size and memory-unit counts in their own aligned columns, and long IDs no longer pushing the rest of the row out.
• A filter you can always clear — the toolbar used to vanish when a filter matched nothing, leaving an empty list and no way back.
• Consistent chips for tags, entities, and metadata — one rendering everywhere instead of per-view styling, told apart by shape rather than color, with the accent color reserved for an active filter.

The section summary list at the top of the post was updated to match.

GIFs replaced with video

Both visuals on this post are now MP4 rather than GIF, following the <video> pattern already used by the v0.8.4 release post.

	before (GIF)	after (MP4)
Entity timeline	3.3 MB, 10 fps, 64 colors, 1000px	1.2 MB, 30 fps, full color, 1432px
Documents table	4.2 MB, 6 fps, 48 colors, 900px	1.6 MB, 30 fps, full color, 1432px

Page weight drops from 7.5 MB to 2.8 MB while the frame rate triples — GIF has no interframe compression, so frame rate was the only lever for size. Sources are 60 fps retina (2864×2160) H.264 exports, re-encoded to 1432px / 30 fps / CRF 24, audio stripped, +faststart.

Attributes are autoPlay controls loop muted playsInline — autoplay+loop so these short silent screencasts behave like the GIFs they replace, muted because iOS Safari blocks autoplay otherwise, and controls kept for anyone who wants to pause or scrub. playsInline is JSX camelCase here (the 0.8.4 post uses lowercase playsinline, which React does not recognize as a DOM property).

The documents recording is cropped to the browser window — the raw capture included the desktop wallpaper. The entity recording is not cropped: it has an editor zoom that pans the window inside the frame, so no fixed crop rectangle applies. That means the wallpaper is visible at its start and end while the documents clip has none. Say the word and I'll drop the crop on the documents clip so the two match.