Documentation

Edit the live page. No rebuild, no repository.

Webnak lets the people who write your copy change it on the site itself. You add one script tag to what you already ship; they click a heading and type. These pages cover installing it, how it stays attached to your markup across redeploys, and every field it reads.

Paste this

Anywhere in <head> or before </body>. Your site key is in the dashboard, and it is public by design.

Your page template
<script src="https://cdn.wolfigs.com/webnak.js" data-site="ilk_your_site_key"></script>

Start here

Install2 minAdd the script tag or the npm package to the site you already ship.Read Your first edit5 minOpen the editor on a live page, change a heading, publish it.Read How it works6 minThe manifest, when it is applied, and why your build is never involved.Read

What it is, and is not

What you get

  • No build step. Publishing content never touches your pipeline.
  • No source access. Webnak never sees your repository or hosts your site.
  • Any stack. Next.js, Vue, SvelteKit, Astro, WordPress, Webflow, plain HTML.

What it is not

It is not a CMS and does not want to become one. There is no content model, no migration, and nothing to move into. Your components, your router and your deploy pipeline stay exactly as they are. Webnak only overrides what is already on the page.

Everything else