A design-system-first page-builder toolkit. Guides for building a frontend, editing content, testing, adapters, and compliance.

Layout and block templates

Connect Inka to a content store through one adapter contract — the same experience for editors whatever sits behind it.

Instead of combining editing and rendering into one framework and codebase, these are separated and during editing a two way communication channel is opened across an iframe so that the editing UI is no longer part of the frontend code. Instead a small JS file called hydra.js is included in your frontend during editing that handles the iframe bridge communication to Inka which is running in the same browser window.

Put checks on content and design in front of editors — plugins for accessibility, design-system conformance and content rules, with a record of what was checked and who approved it.

This guide is for content editors using an Inka-powered site. It covers how to use the editor — how to select things, edit text, add and move blocks, work with containers and templates — without assuming you know how the site was built.