Layout editor now warns about broken code as you write
You no longer create layouts on your own. The editor now works with you while you write: it reviews your template code in real time, tells you the moment something is wrong, explains what the problem is, and fixes the most common mistakes for you in one click.
You get the confidence of a second pair of eyes on every template. Less time debugging, more time designing.
Why it matters: a layout template is code, and small mistakes in it are silent. The template saves, the editor looks fine, and the problem only surfaces later, on a published post. These checks move that discovery to the moment you type, not after publishing.
The editor now catches three new cases:
- Invalid fallback layout references. A landscape layout needs to point to a valid fallback template. When that reference is left as a placeholder or set to a wrong value, the editor highlights it and offers a one-click fix that applies the correct fallback for you.
- Inline styles. Styles written directly on elements inside the template are flagged as errors, with a message prompting you to move them to the layout’s CSS tab before saving.
- External CSS imports. Importing stylesheets from external URLs, such as remote fonts, breaks rendering when your post is generated. The editor now rejects these imports before the layout is saved.
All three checks run inside the editor, before your layout is saved. Nothing reaches production with a known error in it.
Catch it while you write it, not after you publish it.