Anchors and drift
How an edit stays attached to an element across redeploys, and what data-webnak does.
An edit has to survive your next deploy. Webnak identifies elements by several independent signals rather than one brittle selector, and re-checks them in the background after your markup changes.
Name the elements that matter#
Add data-webnak to an element and its edit is bound to that name instead of to its position in the document. Rearrange the page, rename a class, change the wrapper: the edit still lands.
<h1 data-webnak="hero-title">Ship faster with Acme</h1>
<p data-webnak="hero-sub">The platform your team already knows.</p>
<img data-webnak="hero-image" src="/hero.jpg" alt="" />Untagged elements stay editable. They are matched structurally instead, which works until the structure around them changes materially.
Drift#
When your markup changes, a background check re-anchors existing edits and flags anything it cannot place with confidence. Those appear in the dashboard’s drift view for review rather than being applied to the wrong element.
A selector that matches zero elements, or more than one, is skipped. Webnak would rather leave the original text than edit something you did not mean.