Stacks
Stacks
Krantho on Next.js, SvelteKit and Express with Vite: the same content, API and admin on each, with the UI package of your choice.
- Next.js
Krantho for Next.js
Server components read published content in-process, and each page stays cached until an editor changes what it shows.
Add content management, an admin and Schema.org structured data to a Next.js App Router project. Pages are server components that read published content, cached until an editor changes it.
- @krantho/next
- @krantho/server-next
- @krantho/ui-react
- @krantho/ui-react
- @krantho/ui-mui
- @krantho/ui-tailwind
- SvelteKit
Krantho for SvelteKit
Load functions read published content in-process, and a CDN in front can keep each page until an editor changes it.
Add content management, an admin and Schema.org structured data to a SvelteKit app. Load functions read published content, and a CDN can keep each page until an editor changes it.
- @krantho/sveltekit
- @krantho/server-sveltekit
- @krantho/ui-svelte
- @krantho/ui-svelte
- Express / Vite
Krantho for Express and Vite
The API and the admin mount as middleware, and your server-side render reads published content from the same database.
Add content management, an admin and Schema.org structured data to an Express server or a Vite app with server rendering. The API and admin mount as middleware; your render function reads published content.
- @krantho/node
- @krantho/server-node
- @krantho/ui-react
- @krantho/ui-react
- @krantho/ui-svelte
- @krantho/ui-mui
- @krantho/ui-tailwind
Krantho has an adapter for each framework it supports, and the same collections, API and admin on all of them. Pick yours to see how to add it, wire it, render pages and deploy. Code samples across the site follow the stack you choose.