Edit the exact website, like you did with Inspect Element as a kid, but now you can publish those changes. What’s different: Every CMS asks you to move your site into it. Webnak doesn't. Add one script tag to the site you already ship, then click any heading, image or button to change it. Webnak ushers in a new era of dynamic, overflow websites. Websites are no longer hard-coded. Context lives in an overlay, making Webnak stack-agnostic, repo-free, and every publish reversible.
Webnak lets the people who write your copy edit it on the live site, in the browser.
You add one script tag to the site you already ship. An editor loads only for people you have signed in. They click a heading, image or button and change it. Your stack, router, host and deploy pipeline are unchanged.
How the edits survive a deploy:
An edit pinned to a single CSS selector breaks when the markup changes. Each edit here binds to its element by several independent signals. A background checker re-anchors them after a deploy and flags anything ambiguous for review.
What visitors get:
One cacheable JSON manifest per page, about 6 kB gzipped, applied before paint. No editor code is served to visitors. No layout shift.
Current state:
- Research preview. It changes without warning, and is not suitable for a
site you cannot afford to have break.
- No public customers yet.
- Not a CMS. There are no content models and nothing to migrate into. For
structured content with relationships, use a CMS.
Question for anyone trying it: what would prevent you from installing this on a production site?
https://webnak.dev