Search results

Advanced topics for optimising your Inka integration: lazy loading the bridge, authentication, and customising the editor.

The actual code you write will depend on the framework you choose. You can look at these examples to help you:

A block — or the page itself — is divided into regions, and each region holds an ordered list of blocks. Sliders have a slides region, grids have columns, ...

Define custom block types directly in your frontend configuration via the blocks option in initBridge. No editor plugin to deploy. Each block type needs an id, ...

Get the Inka bridge into your project — prerequisites, getting and loading hydra.js, and the minimal initBridge() call that makes a page editable.

A listing block fetches content from the server (e.g. latest news) and renders each result as a separate block, repeating each block once per result entry. ...

Inka works with any frontend, including ones that have no client-side

Inka is the page-building and governance layer between your CMS and your front ends. Content stays in the CMS, rules come from your design system, and front ...

Build a frontend that Inka can edit — add one small script and a few HTML attributes, then wire up blocks, live preview, and templates. Start with the Quick ...

Static assets used by the docs landing page (homepage hero video, etc.).