Released October 24, 2026.
This release gives you control over the code languages your writers can pick, lets AI tools connected over MCP delete pages safely, and fixes several things that got in the way: a documentation sidebar that lost your place, a menu search that hid everything, deployments stuck as Queued, and large schedules that timed out partway.
New features
Choose which code block languages the editor offers
Settings has a new Content page, at Settings → Content. It holds your documentation settings, which moved there unchanged from Settings → General, and a new Code Blocks section.
In Code Blocks you choose which of highlight.js’s languages, about 190 of them, appear in the page editor’s code block dropdown. Each language has a checkbox, and a filter box narrows the list by name. Changes save as you make them and show in the editor the next time it loads. Your custom highlighter languages sit at the top of the section and always appear in the dropdown.
The dropdown in the editor gets a filter box too, which has focus as soon as it opens: type to narrow the list, use the arrow keys and Enter to pick, or press Escape to close it without changing anything. A new Text option sets a block to plain text. If a writer cannot find a language, the help icon beside the block’s delete button tells them where an administrator can enable it.
Learn more: Code Blocks, General Site Settings.
AI tools can delete pages, with a 404 or a redirect
AI tools connected to your CMS over MCP can now delete a page. A delete always happens in two steps: the first call changes nothing and shows you exactly what will happen to that page, and only a second, confirmed call performs it.
- A published page is removed from the live site the same way as a delete in the editor. Before it can go, you choose what its live URLs do afterwards: return a 404, or redirect to another published page.
- A page that was never published, or an internal page, is deleted permanently.
Choosing a redirect now really creates it. That also fixes the editor’s own delete dialog, which offered a redirect page but did not set one up.
Learn more: MCP Tools: Pages and Content.
Fixes
The documentation sidebar keeps your place
The left navigation on documentation sites keeps the page you are reading in view again. It used to scroll to your page and then jump back to the top a moment after the page loaded, or whenever you resized the window. The table of contents no longer resets on resize either. Each site picks up the fix the next time it builds.
Searching a documentation menu filters its pages
Typing in the search box on the Documentation and Internal menus now filters the pages inside each menu by name. Before, it matched only the menu’s own name, so as soon as you typed anything else the whole menu disappeared. Folders that hold a match open by themselves, and typing a set’s own name still shows the whole set. Pressing Enter still searches the text of your pages.
Learn more: Left Navigation Menu.
Deployments no longer stay Queued forever
Occasionally a publish created its deployment but its build never started, and the deployment showed as Queued in your history indefinitely, with no way to retry it. Leed now spots these within a few minutes. If nothing newer has been deployed since, it starts the build; if a newer deployment has already replaced it, it closes the stuck one out as canceled.
Learn more: Deployment History and Status.
Renaming a page to its folder’s index no longer breaks the build
Clearing a documentation page’s slug, so that it becomes its folder’s index page, or giving an index page a slug of its own, now moves the page’s file. Before, the new file was written beside the old one, and the next site build could fail because two files claimed the same URL.
Large schedules over MCP no longer time out partway
AI tools scheduling pages over MCP now schedule at most 25 pages per call, because a larger call could be cut off partway, with some pages scheduled and the rest not. To schedule more, an AI tool makes several calls with the same publication time, so the whole set still publishes together. A call that was cut off can be repeated unchanged: pages already scheduled at that time are skipped. Releases scheduled from a CI pipeline are unchanged.
Learn more: MCP Tools: Publishing, Distribution and Users.