Dock Layouts for multi-window dashboards: the benefits post, with the film

Context

The operator's release-day goals (2026-10-11) ask for a new blog post that carries the 13.2 film, explains what Dock Layouts give a multi-window dashboard, shows screenshots, and gives code examples, in two stages: benefits first, implementation details later. This ticket is stage 1. Stage 2 gets its own ticket when this one merges.

The 13.2 post learn/blog/a-workspace-that-can-leave-its-window.md (#9854, 2026-10-09) already tells why it works: one SharedWorker heap, one Group transaction, the real-window war story. It has no film and one code sample. This post answers a different reader's question: what does my dashboard's user get, and how little do I write to give it to them?

The Problem

• Angle: a dashboard user arranges the workspace the way their work is shaped, across screens, and nothing they arrange is lost. Panes tear out into real OS windows and come home as themselves, fold into edge rails, maximize, come back as a named perspective, and Undo walks all of it. The builder declares panes and zones; the dock owns the rest.
• Audience: cold readers who build data-dense dashboards (operations, monitoring, analytics, trading), developers and architects. No Neo knowledge assumed.
• Sources to mine (nothing invented): learn/guides/uibuildingblocks/DockLayoutsFeatures.md (what users can do, and what the dock refuses), DockLayoutsAdoption.md, DockLayoutsWindows.md, DockLayoutsStateAndPersistence.md, learn/tutorials/DockLayoutsFirstLayout.md, the Dock chapter of .github/RELEASE_NOTES/v13.2.0.md (#14800), the film (#15252), and the running dashboards: examples/dashboard/choreography (the portal's Dock Layouts card) and apps/workstation.

The Architectural Reality

Docs only. The post lives in learn/blog/<slug>.md and is registered by hand in apps/portal/resources/data/blog.json (2026 node). The SEO surfaces are generated by the data-sync pipeline and stay untouched. Images are hosted in neomjs/pages under resources_pub/website/blog/<slug>/ (precedent: website/blog/jsonblueprints/); release-note frames under website/release-notes/v13.2.0/ are reused where they fit. A YouTube video embeds as a cover image linked to the video (precedent: learn/blog/json-blueprints-and-shared-workers.md).

The Fix

One post: thesis, the dashboard user's problem, the film, what each dock feature gives that user (with screenshots of running dashboards), a short code taste copied from a live tutorial or example, honest bounds, one question and one next step. Deep code goes to stage 2.

Acceptance Criteria

• The post leads with its thesis and a cold-reader hook; its title passes the blog guide's mechanical title test. (#19607; title "Drag it to the other screen: …")
• The film is embedded as its cover image linked to YouTube (depends on the film's YouTube URL). (KESyjFmOz0k, public; the cover is served from neomjs/pages#29 once merged)
• At least three screenshots of running dashboards, each captioned with what the reader sees. (five new frames in neomjs/pages#27 plus the notes' d3 tear-out)
• At least one code example copied from a live tutorial or example, linked to where it runs. (the tutorial's second example; the dock example's perspectives)
• Every external claim is sourced; every internal claim links its PR, issue or guide. (Clio's design read and Sophie's review checked them)
• It links a-workspace-that-can-leave-its-window.md for the architecture and does not retell it.
• Registered in blog.json (parses) and render-verified at #/news/blog/blog/<slug>. (rendered locally; the live check follows the 13.2 deploy)
• At least two model reviews, one from a non-Claude family; the operator approves last. (Sophie, GPT: APPROVED; Clio, Claude: design read PASS; the operator merged last)
• No client names.

Out of Scope

• Stage 2, the implementation post (Workspace configs, pane policies, persistence and perspectives, popups and their render target, styling).
• The film itself (#15252), the README video swap and the release-notes embed.
• Engine changes.

Related

• Parent: #13383 (the blog stream)
• #14790 (launch playbook: the flagship and its story beats)
• #14800 (13.2 notes), #15252 (the film), #9854 (the architecture post)

Live latest-open sweep: latest 20 open issues read at 2026-10-11T15:23:43Z, no equivalent. A2A in-flight sweep: no claim on a dock or dashboard post since 07:27Z. Memory Core sweep: no prior decision found.

Retrieval Hint: "dock layouts multi-window dashboard blog post benefits film screenshots"