Client mode, standalone pages & Settings

Under Kerf → Settings, agencies and site owners can lock down page structure for clients, tune how WordPress core CSS interacts with imported stylesheets, and manage staged asset folders.

Client mode: safe handoff for editors

When you hand a finished WordPress site to a client or content editor, you want them to update headlines, paragraphs, photos, and links—without accidentally dragging a column out of a CSS Grid or deleting a wrapper div.

Enable Client mode under Kerf → Settings:

• Blocks cannot be moved, inserted, or deleted, and raw HTML tag/class attributes are locked.
• Every heading, paragraph, button label, image, background picture, and link destination remains fully editable.
• You can enable Client mode for Editor roles only (leaving Administrators unrestricted) or for everyone until toggled back off.

Importing a page with a design of its own

Want to launch a special campaign page or microsite with a completely different look from your main site? On Kerf → Import design, set Scope to A page of its own. Kerf imports that ZIP or HTML document into a single WordPress page with its own self-contained header, footer, stylesheets, and scripts—leaving your main site’s header, footer, and global assets untouched.

Core CSS level & registered assets

• Core CSS level: By default, Kerf strips interfering WordPress block-library layout margins on imported pages so your mockup’s CSS rules win without a specificity war. You can adjust this setting if you use third-party block plugins on the same page.
• Asset list: Inspect the exact stylesheets and scripts registered from your mockup in their load order.

Cleaning up staged mockup files

Each ZIP import stages its assets into a timestamped folder under wp-content/uploads/kerf-blocks/mockup-*. Under Kerf → Settings → Staged mockup files, Kerf scans every published page, draft, and template part to show which folders are actively in use and lets you delete unused folders from older imports in one click.