Weekly Review: July 1–7, 2026

This week was a mix of custom deployment work in the fork and a large push to simplify the editor’s read/edit lifecycle. The most important thread was making publishing, old versions, and drafts agree on what the user is looking at.

What shipped

    Explored custom web/site image deployment in the fork, including custom branch auto-deploy and query author filter work. See fork PR #1, fork PR #2, fork PR #3, fork PR #4, and upstream PR #841.

    Stopped the editor from exiting edit mode on outside clicks and made document body rendering come from the document machine source of truth after publish. See commit 8798fa00.

    Fixed a cluster of publish and old-version issues: published content now renders after publish, query blocks retarget on first publish, the publish popover stays reachable, old-version messaging moved from banner to toast, and document menu labels were renamed. See commit d2f65ae7, commit 54c7795f, commit efdb89a5, commit 7d465d6a, and commit 1de084a7.

    Restored media hover and selection actions while keeping query blocks suppressed, then fixed desktop publishing/logging/frontmatter parsing. See commit 4a4b8657 and commit 5533ac77.

    Added support for moving unpublished drafts. See PR #844.

    Reduced DocumentEditor effects from ten to two by moving read-only content sync into the document machine, consolidating the editor bridge, extracting focused hooks, and replacing document-level Enter-to-edit with a header focus chain. See PR #846.

    Smoothed hover actions and editor interactions: nested block hover actions work better, the delete dialog expands correctly, query block edit errors were fixed, image captions stopped stealing focus in grid containers, and hover actions got a prediction cone. See commit 836c08e8, commit f6c35d30, commit 7a16d171, commit 0de14e62, and PR #850.

Notes

The state-machine cleanup was the center of gravity. Once the editor’s source of truth is clearer, every surrounding behavior—publishing, restoring, draft movement, and click-to-edit—has fewer special cases to fight.

My question from this week:

When does “just keep the editor open” become a state-management problem instead of an interaction tweak?

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime