Blocks move on the real layout with the real styles. What you arrange is what publishes, so there is no gap between the editing view and the live site.
MDX when the block editor runs out
Switch to MDX for anything structural, and use components inside the content. The visual editor keeps working on the same page afterwards.
Styling from a token system
Colour, spacing, radius and type come from your site's tokens. Change the brand once and every page follows, with no stylesheet to maintain.
An assistant that has to be right
The in-editor AI drafts and revises pages, and its output is validated against the component catalogue before it can land. Invented components are rejected, not published.
From empty to published
01
Start from a template
Pick a working site from the gallery, or start blank if you would rather.
02
Make it yours
Rearrange blocks, set your tokens, and write the pages — visually or in MDX.
03
Publish
One action puts it on your aveiro.page address or your own domain.
Do I have to choose between the visual editor and code?
No. Both views operate on the same page. You can lay a section out visually, drop into MDX for a tricky bit, and go back to dragging blocks.
Can I use my own components?
Pages are built from the Once UI component set that ships with Aveiro. Sites you build get the same catalogue, and the AI assistant is restricted to it so generated pages cannot reference something that does not exist.
What happens to my styling if I change the brand later?
Styling comes from tokens rather than per-page CSS, so changing a token updates every page that uses it. You do not need to revisit pages one by one.
Can an agent edit the same pages I edit by hand?
Yes. Pages written through the API or the MCP server are ordinary pages — you can open them in the editor afterwards, and vice versa.