Design it live: how Besigner renders the real page

Most site builders keep two copies of your site: the one you edit and the one you ship. Besigner keeps one. The canvas you design on is the same document your published pages render from, so what you see while editing is — literally — the page.

One document, two views

Every screen in Aglyn is a tree of nodes stored with the site itself. Besigner opens that tree on a live canvas; the published site renders the very same tree on your domain. There is no export step, no code generation, and no second copy that can drift out of date. When you hit Save, the change is the deploy.

Real components, real content

The canvas doesn't paint approximations. It runs the same component library your visitors get — text, images, containers, collection entries, forms — bound to your real content, theme tokens, and interactions. Editing a blog card on the canvas is editing the block that lists your actual posts.

Versioned, so you can be brave

Each screen keeps versions. Publish when you're ready, roll back when you're not. Combined with live co-editing, that means a team can work on the real page together without a staging maze.

Why it matters

Preview environments, sync scripts, and "it looked different in the builder" bugs exist to bridge a gap Aglyn doesn't have. Design it live, publish in one click, and move on.