See the result before it writes.
Click editable text or use the toolbar. Each proposed change appears on the page first.
Open source · Development only · Source aware
Work from the rendered page, preview each edit, and commit a reviewed batch to your Astro source files. Text, metadata, and declared page sections share one visible change queue.
Planning an Astro website? See Opace Astro developmentThe review loop
The browser remains the shared context. The source file changes only after the full batch has been checked and deliberately committed.
Click editable text or use the toolbar. Each proposed change appears on the page first.
The queue records the old value, new value, edit type, and expected source file.
One deliberate action checks and writes every update, or leaves the source untouched.
What it edits
Rendered text
Exact file annotations, route context, and structured paths identify where content is owned. Ambiguous expressions stop with a clear error instead of guessing.
Sections
Reorder, add, and delete sections with pointer, keyboard, or explicit move controls. The review ledger records section changes alongside text and SEO edits.
SEO
Page title, description, canonical URL, Open Graph data, robots, and keywords use the same preview and review transaction.
Source adapters
Syntax-aware adapters target literal values and exact structured paths while preserving comments and surrounding file structure where the format supports them.
A deliberately local editor
No public write route, no production editor bundle, and no silent fallback.
Release candidate
The code, integration metadata, documentation, tests, and release workflow are in the public
repository. The @opacedev/astro-visual-editor npm page will become the install
route after the first package publication is confirmed.
$ npx astro add @opacedev/astro-visual-editor@beta
✔ Update astro.config.mjs
✔ Run astro dev
✔ Open Visual Editor in the Dev Toolbar Questions before installing
No. Astro Visual Editor is built for local development. Production builds contain no public write route or editor client bundle.
You can move, add, or delete sections inside regions a developer has declared editable. That boundary keeps source updates predictable and prevents unrelated page structures from being changed by accident.
Not in every project. It suits source-controlled Astro sites where editors need a direct, reviewable way to make bounded changes. A team with permissions, publishing workflows, or a large content operation may still need a full CMS.
Use the public GitHub issue tracker with the Astro and Node versions, a small reproduction, and the result you expected.
Created by Opace Digital Agency
It is created and maintained by Opace Digital Agency's Astro development team. If you need a wider website project, see the web design services provided by Opace or get in touch.
Built in Birmingham for teams everywhere