Open-source visual editor
Your static site.
Now editable.
Xyle adds a safe editing layer to the HTML and assets that you already own. Review each change, then publish it back to the same files.
No account. No content database. No change to your public pages.
A clearer
headline
ContentYour HTML and assets
DraftsYour browser memory
HostingYour existing provider
PublishYour decision
One short path
Edit the site you already have.
Xyle works with final static output. It does not require a framework adapter or a second content model.
-
01
Open
Start Xyle beside a static folder and open its protected editor path.
-
02
Edit
Change existing text, links, images, structure, layout, and SEO in context.
-
03
Review
Inspect useful before-and-after values. Undo one change or discard the draft.
-
04
Publish
Write the reviewed result to ordinary static files on infrastructure you control.
The editing boundary
A CMS-like experience without moving your content.
People edit visually
The protected preview blocks site scripts and form submissions while the owner edits.
Agents use the same controls
WebMCP changes enter the same ChangeSet, safety rules, history, and review surface.
Only the owner publishes
An agent can prepare work. It cannot bypass the final human-controlled Publish action.
Start with one folder
Two commands. Your existing files.
Run Xyle from the directory that contains your static website output.
$ cd /path/to/static-output
$ npx xyle init .
$ npx xyle dev .
Public site: http://127.0.0.1:4173
Editor:
http://127.0.0.1:4173/edit
No-login browser sandbox
Make a change without changing our site.
The demo keeps its files in your browser. Refresh the page to start again.
Open the editor
Xyle