# Work on your real site, not a mockup.

> Bixlow's visual editor is a workspace over a live preview of the customer's real site, where pointing at an element makes Bixlow create its selector and the matching node, and a docked AI agent builds changes on top of what you are looking at.

- Source: https://bixlow.com/en/platform/visual-editor
- Language: en
- Publisher: Bixlow

Open your site in the editor, point at what you want to change and the agent builds it in front of you. What you see in the preview is what your visitors will get, and nothing ships without your approval.

- **Where you edit:** On your real site, live
- **How you select:** Point at the element
- **Who builds it:** The agent or you
- **Safety net:** Versions and autosave

## Why changing a live site is so slow

Changing a page you don't control usually means a chain of screenshots, tickets and guesses about how it will look.

### Design happens on a mockup

The change is approved in Figma or a screenshot, and on the real site the block doesn't fit, the copy wraps badly or mobile breaks.

### Finding the element is a job in itself

Touching one button means opening developer tools, finding a selector that won't change tomorrow and explaining it to whoever will code it.

### Two people overwrite the same change

One person edits, another edits on top, and nobody knows which version was the right one or how to get back to it.

## From click to published change

Everything happens in one editor: the preview of your site, the workflow canvas and the agent's chat.

1. **Open your site in the editor.** With the script installed, the editor loads a live preview of your site. You browse it the way a visitor would.
2. **Point at the element.** Click a headline, a button or a section and Bixlow builds the selector and the node that represents it in the workflow.
3. **Ask the agent for the change.** Describe what you want in the docked chat. The agent builds it on top of what you are looking at and the preview updates.
4. **Review and publish.** Check the result in the preview. Publishing is always your call, and every version is saved.

## An editor built for working on production

Being able to change something is not enough. You need to see exactly what changes and be able to undo it.

### Live preview: Your site, not a copy

You edit on the real page, with its content, styles and behavior, and see the change applied before you publish it.

- Point at an element and the selector and node are created.
- The change shows up in the preview right away.
- What you approve is what your visitors will see.

### Docked chat: The agent works on what you are looking at

The AI chat sits next to the preview and knows the open workflow, so you can ask for changes without explaining where everything is.

- Builds banners, bars, popups and sections in your brand's look.
- Edits elements that already exist on the page.
- Asks when it is missing information instead of guessing.

### Versions: Nothing gets lost, nothing gets overwritten

The editor saves on its own, keeps a version history and stops two people from editing the same draft at once.

- Autosave while you work.
- Version history with restore.
- Edit lock so nobody overwrites someone else.

### Assets: Your images, close at hand

A per-project asset library for the images your changes use, without uploading them to your own server.

- Upload images once and reuse them.
- The agent can upload and use images too.
- Everything stays inside the project.

## You point; the agent builds

The editor is not a toolbox for doing everything by hand. It is where you see what the agent builds and decide whether it ships.

### You decide

- Which page and which element to change.
- How it should look, in your own words.
- Whether the result in the preview works for you.
- Publishing: nothing reaches your site without your approval.

### The agent does

- Builds the component or change on the real page.
- Follows your brand's typography, color and tone.
- Sets up the triggers and goals it needs.
- Lists earlier versions and restores the one you ask for.

### A change in the editor

- **Element selected:** Shipping block on the product page
- **Request:** "Add a free shipping notice above the button"
- **What it builds:** A bar with the brand's copy and colors
- **When it shows:** On page load
- **Status:** Draft saved · waiting to publish

## Bixlow Studio: Would you rather someone built it for you?

Bixlow Studio works in the same editor on your site: designers and engineers build the changes and a strategist reviews them before you approve.

- Custom components in your brand's look.
- Changes and tests delivered every week.
- Goal setup so every change is measured.

## FAQ

### Do I need to code to use the editor?

No. You point at the element and ask for the change in the chat. If you do code, you can review and edit what the agent builds.

### Does the editor change my theme or CMS?

No. Changes are injected into the page when it loads. Stop the workflow and the change disappears on the next page load, with your theme untouched.

### What if I make a mistake?

The editor saves on its own and keeps a version history, so you can go back to any earlier version. And nothing is published without your approval.

### Can several people edit at once?

The draft has an edit lock: while someone is editing it, nobody else can overwrite it without noticing.

### Does it work with my platform?

It works with Shopify, WooCommerce, PrestaShop, Webflow, Framer, WordPress and custom builds: any site where you can add a script.

## Open your site in the editor

Install the script, point at the first element and ask the agent for the change.
