# Changelog, September and October 2026: inline editing and Next.js 16.4

Inline text editing in Presentation, a hero split block, an ask-a-question FAQ, SEO fixes and Next.js 16.4 with the Rust React Compiler.

![Neon yellow and orange light streaks crossing a dark dotted grid](https://cdn.sanity.io/images/s6kuy1ts/production/57efbed4ccc2c41cd2bb2821848afe69b12edd57-4096x2596.png?w=1600&fm=webp&q=80&auto=format)

September was about the editing loop. October so far is about speed.

## Edit text where you see it

The Presentation preview now supports inline text editing. A `defineDocuments` resolver maps routes to their main document, the new page form stays open, and draft refresh no longer makes the preview flicker. A full Presentation end-to-end suite, with video on failed runs, keeps it that way.

## New blocks

A simple hero split block joined the page builder. The FAQ block now lets visitors ask their own question, with focus and overflow fixes for narrow screens.

## SEO and resilience

Inherited SEO and structured data defects were fixed. The Markdown route respects `DRAFTS_WITHOUT_SESSION`, and the footer and images render with JavaScript disabled. Release version ids no longer trip the slug uniqueness check.

## Next.js 16.4

The web app moved to Next.js 16.4 with the Rust React Compiler. The compiler handles memoisation for you, so you can keep writing plain components.

## Smaller fixes

- Empty env strings are treated as unset, so optional variables accept blanks.
- The unmaintained Lucide icon picker was replaced and `@sanity/ui` 3 was unpinned.
- Mobile menu, nav drawer, feature card and FAQ polish.
- Every seed blog post now has a category.

Edit in context, ship on the latest Next.js, and let the tests catch the rest.