Static assets used by the docs landing page (homepage hero video, etc.).
Advanced topics for optimising your Inka integration: lazy loading the bridge, authentication, and preventing reloads.
Located in
Docs
Instead of combining editing and rendering into one framework and codebase, these are separated and during editing a two way communication channel is opened ...
Located in
Docs
The actual code you write will depend on the framework you choose. You can look at these examples to help you:
Located in
Docs
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, ...
Located in
Docs
Define custom block types directly in your frontend configuration via the blocks option in initBridge. No Volto plugin deployment required. Each block type ...
Located in
Docs
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. ...
Located in
Docs
Inka works with any frontend, including ones that have no client-side
Located in
Docs
