02 / Edit
Click, write, and watch the live preview follow along. The editing surface is your real website, so nobody has to picture how a field turns into a headline.
Included on every plan. Unlimited editors.
What this replaces
That loop is how most CMS editing still works. You fill out fields, publish a preview, find out the headline wraps badly, and start over.
Nobody thinks in form fields. People think in pages. So the page is where you edit.
How it works
A two-way connection between the editor panel and your rendered site. Six things it gives an editor.
Edit a field and the preview updates without a reload and without publishing. The words you are writing are the words on the page.
Select a headline, an image, or a whole block in the preview and the panel jumps straight to its fields. The page is the navigation.
Browse the block library, search by name, and drop a new block anywhere in the page. Every block is one your team already defined.
Switch viewport with one click and catch a broken layout before a visitor does. No second device, no DevTools.
Change language in the preview and keep editing. The asset library, the reference picker, and the rich text toolbar stay where they are.
Leave a note on the block you are looking at and keep the conversation next to the draft instead of in a separate thread.
No special build
Visual editing does not ask you to rebuild anything. Your site renders your content as it already does, and b10cks sends it live updates over a documented preview connection. Nuxt gets preview composables in the module. Everything else uses the preview API directly, with more framework SDKs on the way.
Give your editors the page
Invite your writers, open the preview, and let them work on the real thing.