AI proposals are validated before they touch your site, broken components block publishing, and version history plus a live-site link make it easier to recover or verify what visitors actually see.
What we shipped
Quasar — the AI assistant in the site editor — works through structured tools on Once UI components, not open-ended HTML generation. Recent releases tighten that model on the safety side:
Validate AI MDX before storing — reject invented components and unparseable bodies
Validate proposal edits before applying — catch broken blocks before they land in your draft
Repair common AI MDX mistakes — including double-escaped content that breaks the parser
Block publish when any page has a broken component — no silent empty sections on the live site
Open published site from the editor — verify the public URL without guessing the slug
Together, these changes reduce the gap between “looks fine in chat” and “breaks on publish.”
Why we built it this way
Many AI site builders regenerate code on every prompt. That is fragile: models invent tags, escape MDX incorrectly, and drift from what the renderer actually supports.Aveiro’s approach keeps creativity in your hands and uses AI to adjust configs, copy, and layout settings inside a fixed component system. Validation is the enforcement layer — if Quasar proposes something the renderer cannot compile, you see it before publish, not after a visitor hits a blank block.
Recommended workflow
Ask for scoped edits — “Rewrite the hero headline” rather than “Redesign the entire site.”
Review change cards before applying AI proposals.
Check for broken components in the page list before publishing.
Use version history on the active page if you need to roll back a bad edit.
Open the live site from the editor and click through primary nav and CTAs.
If preview and live ever disagree, treat the published URL as source of truth.
When publish is blocked
Publishing is disabled while any page contains a broken component. Fix or remove the broken block in Visual mode, then publish again.This pairs with SEO and social settings: shipping a broken page hurts crawl quality and trust, not just aesthetics.
Recovering from a bad edit
Version history stores snapshots on each save. Select an older version, preview it, and restore to replace the current draft. Live content does not change until you publish again.For a longer walkthrough of Quasar’s tool-based flow, see AI overview and Working with AI changes in platform docs.
What is next
We continue hardening the editor prompt and expanding the admin AI error log so recurring failure patterns get fixed upstream. If you hit a block Quasar cannot resolve, version history remains the fastest rollback path.
