Docs

Inka ships as a blank slate: your components are your blocks, and you decide what editors can build. The docs are a set of guides by audience — build a frontend, edit content, test it, connect a content store, and put compliance checks in front of editors.

The guides

Examples

Example blocks to spark ideas. Inka ships as a blank slate — these are things you can build with your own components, not a fixed library.

Testing & the mock API

Author content as Markdown, serve it through the mock API, and check that every block renders — the local loop for content and blocks.

CMS adapter guide

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

Compliance & audit

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.

Editor Guide

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.

Frontend developer guide

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 Start for your framework.

Why Inka?

  • Compliance and engagement, not a trade-off — you decide where the dial sits for each site, instead of choosing between locking editors down and letting the design system drift
  • Design-system-first — components declare what they tolerate, so off-system output can't be produced
  • Multi frontend, multi backend — Next.js, Nuxt.js, Astro, plus server-only stacks (PHP, Django, Rails, Laravel) via the server-render pattern; switch channels mid-edit
  • AI under the same constraints — everyone's AI can build you a page; ours can't build one that breaks your design system
  • Evidence, not just warnings — rules a machine can't decide go to the people who can, and the determination is recorded against that version of the content
  • Quick to adopt — enable visual editing with simple HTML data attributes, no React or Vue required in your frontend
  • A toolkit, not a CMS — good out of the box with zero configuration, extensible when you need more; open source and self-hostable

Try the online demo

The fastest way to feel what Inka does is to log into the hosted demo and edit a real page against a real frontend.

Open <https://admin.inka.sh>, log in, then:

  • Open user preferences (bottom-left).
  • Pick one of the preset frontends, or paste in your own frontend URL.
  • Edit any page — every change updates the live preview.

See Build a frontend › Deployment patterns, or to run Inka locally see the Run Locally section of the project README.