Cacao Kit

Demo & Semi Documentation

Cacao Kit – Best Practice Nuxt and Kirby Starter, next to a drawing of a cacao tree

Why Cacao Kit?

It bundles what works when Nuxt renders a headless Kirby: one KQL request per route, blocks resolved on the server, content in two languages, and SEO meta from the server. Clone both halves and start with a working site instead of a blank page.

Why Nuxt?

Nuxt is a Vue framework with server-side rendering, file-based routing and head management built in. Cacao Kit renders every page on the server and caches Kirby's answers there, so visitors get HTML first and JavaScript second.

Semantic HTML

The demo styles plain HTML elements with Oat, a small CSS library for semantic HTML, loaded from a CDN. To bring your own styles, remove the stylesheet from the useHead() call in app.vue – UnoCSS is already set up.

The Kirby Panel editing a note built from blocks
Everything is a block, if you want it to be.
Cacao Kit

Each block in the Panel maps to a Vue component in the frontend. Instead of writing a query and a template for every page, you build pages from blocks, and the catch-all route renders them.

Pages that need fields of their own still work: the about page has a Nuxt page with its own KQL query.

Two repositories

The backend is a Kirby site that only serves content. It holds the blueprints, the blocks resolver, and a KQL endpoint behind a bearer token. The frontend is the Nuxt app you are looking at. Each repository deploys on its own.

The notes below explain how the pieces fit together.

Ingredients: Nuxt × headless Kirby

Notes

The grid below is a custom block. The backend fills it with the listed notes, so it arrives with the page in a single request.