Repository navigation
Releases
Releases · descoped/krantho
v1.1.1
Publish a repository's existing docs folder as a static site.
- A collection's
indexFilereadsREADME.mdas its home page (#15) site.renderingforinitServerLoader(): relative links between markdown files go to their pages, and files beside them are served from the site's root (#15)renderContent()takesresolveUrl;initServerLoader()takesresolveUrlandatNotation(#15)- The
srcandhrefof raw<img>and<a>tags get the same rewriting as markdown links (#16) - A static site's pages follow
content.atNotation; the static starter writes no.envand styles tables (#15)
No database reset is needed: the release adds content files only.
v1.1.0
Static krantho sites, built from markdown to plain files and published to GitHub Pages.
Added
@krantho/static: build a site from its markdown at build time, with every page's structured data, the sitemap, llms.txt and robots.txt, for GitHub Pages or any file host (#13)create-krantho: a "Static site (Next.js, GitHub Pages)" choice, a docs site with a grouped sidebar and a workflow that publishes it on every push (#13)- Links and images in markdown that start at the site's root get the path the site is served under (#12)
@krantho/apiexports the sitemap, robots.txt and llms.txt builders (#12)
Fixed
v1.0.2
Fixed
- A content file removed from the repository deletes its document on the next deploy, unless an editor changed it in Studio (#7)
create-krantho: a scaffolded pnpm project builds SQLite on pnpm 10, 11 and 12 (#4)
Changed
- SvelteKit 3, postgres.js 4, and every dependency and tool at its latest version (#5)
No database reset needed: the deploy imports the changed content and removes the documents of deleted files.
v1.0.1
A patch release for sites that install krantho from npm.
Fixed
- Next.js sites installed from npm start:
@krantho/server-nextimports next's subpaths with their file extension. In 1.0.0 every page, the API and Studio answered 500 (5244e82). - Studio is found under every package manager, pnpm's strict layout included:
@krantho/serverdepends on@krantho/studio(6c100fb).
Changed
- Every published package has a description; packages are published through npm trusted publishing, with provenance.
- Dependencies updated to their patched versions (efd3746).
No database reset: the deploy imports the new and changed content files.
v1.0.0
The first release of krantho, and where its changelog starts. Krantho is a CMS library for Next.js, SvelteKit and Express: you add it to a site you build yourself, and it runs inside your app, on your host and your database.
- Content templates defined in code: a collection is a Zod schema, its documents are markdown with frontmatter.
- Studio, the dashboard for editors, served at
/studioby@krantho/studioon every framework. - Drafts, publishing, version history, editing locks, locales and a media library.
- Structured SEO: one JSON-LD graph per page from site, collection, route and document archetypes, with meta tags, sitemap,
robots.txtandllms.txt. - SQLite or Postgres; media on local disk, Vercel Blob, S3-compatible stores or Google Cloud Storage.
- Page caching with Next.js ISR or a CDN.
- A REST API with an OpenAPI 3.1 specification, plugins, webhooks, and sign-in by token or OpenID Connect.
- The
kranthocommand-line tool, the Claude Code plugin andcreate-krantho.
The packages are not on npm yet. See CHANGELOG.md.