Type to search pages and sections.

Skip to content
Ginko

Changelog

0.4.0

The first public release, as 0.4, because older packages with these names went up to 0.3: one content system for Nuxt websites, from Markdown files in Git to a hosted platform that owners, staff and AI agents edit together. All packages release together under one version. Until 1.0, a minor version (0.4 → 0.5) may contain breaking changes; this changelog names each one and how to update.

Requirements: Node 22.18+, 24 or 26, and Nuxt 4.6+ or Nuxt 5 (tested on its nightly until it is released). Start with npm create ginko@latest my-site and Getting started.

Content

  • Bricks and fields in ginko.config.ts, with types, checks and a URL for every entry in every language. See Bricks.
  • Markdown everywhere, with field profiles that limit what a field may contain, components, route links ($blog.my-post) and snippets.
  • Files: Markdown, YAML, JSON and CSV, checked against the fields, with drafts and old addresses. See Content from files.
  • Queries, navigation trees, breadcrumbs and previous/next. See Reading content.
  • A link check before any HTML exists, in the build, the dev terminal and ginko check.
  • Images as WebP at 480, 960 and 1600 px with srcset.
  • SEO and agent output: head tags, JSON-LD, sitemap, robots.txt, redirects, /llms.txt, a Markdown version of every entry page, and generated share cards with nuxt-og-image. The Nuxt SEO modules work alongside and get Ginko's data. See SEO and agents.

Languages

  • @lupinum/ginko-i18n: routes, hreflang, messages with plurals, and formatters for dates, numbers, money and lists. It also works on its own in any Nuxt app. See Languages.

Components and docs

  • @lupinum/ginko-components: callouts, tabs, code groups, steps, cards, embeds, timeline, quiz and more, also as a shadcn-vue registry. See Components.
  • @lupinum/ginko-docs: a whole docs site from Markdown files, with search, blog, changelog and an MCP endpoint. See Docs sites.

Platform and Studio

The platform is hosted by Lupinum. Owners change content in the Studio, phone first, with quick tasks, a files library, approvals, scheduling, history and undo. See Platform and CLI.

Presets

  • @lupinum/ginko-preset-gastro: opening hours, lunch menu, menu, notices and events for restaurants. See Presets.
  • create-ginko: a new site, plain or with --preset gastro or --preset docs, in English or German (--locale de).

Not in 0.4

Real-time co-editing comes next. Also not included: an agency preset, the editor as a shadcn-vue registry, OAuth for agent connectors, and a Google Business sync.