Development Blog

The Grav admin has carried the project for the better part of a decade. Admin Classic was always pragmatic: a Twig-rendered interface, jQuery for the dynamic bits, built directly on top of the same render pipeline that serves the public site. It worked, it shipped, it scaled to a global community...

Back in late 2015, we announced that Grav's translation workflow was moving to Crowdin. At the time it was a huge step forward. Instead of forking a plugin repo, hand-editing YAML in your editor, and submitting a pull request for every typo, contributors could log into a polished web UI, translate strings in context, and let Crowdin manage the round-trip back to GitHub. For a community that was just starting to grow internationally, it was the right call.

A decade later, the picture has changed. The Admin plugin became Admin2 with its own SvelteKit5 SPA. The plugin ecosystem expanded well past what a single Crowdin project was comfortable indexing. AI translation went from "interesting demo" to "genuinely usable", and our own ecosystem now ships a first-party API plugin and Admin Next that make it trivial to build the kind of integrated tooling that used to require a whole separate platform.

So we built one. Today I'm thrilled to announce the Grav Translations Portal, live at translations.getgrav.org, and the new home for translating Grav plugins and themes going forward.

The Grav API plugin is the load-bearing component of Grav 2.0. Admin Next is built on top of it, the MCP server runs through it, and any third-party tool that wants to talk to a Grav site (a build script, a CI job, a headless frontend, a mobile app, an AI agent) goes through it. The API ship...

If you ship a Grav plugin or theme, the new compatibility flag is one of the most important things to know about for Grav 2.0, and it's also one of the easiest 2.0 updates you can make. It's a one-block addition to your blueprints.yaml that tells Grav exactly which major versions you've tested...

If you maintain a Grav plugin or theme, this post is your starting point for Grav 2.0. I know how a major version bump can look from the outside, especially when the headline features include a brand-new admin and a first-party API, so I wanted to get out in front of the obvious question: "what do...

One of the biggest lessons we took from the 1.8 beta cycle is that in-place upgrades across a generational library change are inherently fragile. When the PHP stack moves, the Symfony vendor packages move, and Twig moves all at the same time, even a well-tested upgrade path can fall over the m...

After nearly two years of development (including a 1.8 beta cycle that taught us a great deal about what not to do), I'm thrilled to announce that the entire Grav 2.0 suite has reached Release Candidate status today. Grav 2.0 core, the API plugin, Admin2, Quark 2, and the Migrate plugin are all available right now via GPM (the MCP server is a separate standalone Node.js package, see below), and they all behave like the final product is going to behave.

I want to take a moment to write honestly about where Grav is, how we got here, and what's coming next. The short version is that Grav 1.7 has been the backbone of this project for the past five-plus years, it's been remarkably stable, and we've reached a natural ceiling that means it's time for...

We're excited to announce the launch of our brand new in-house licensing and purchase system for all Grav Premium products. This is a change we've wanted to make for a long time, and we're confident it will provide a much better experience for everyone.

Why the Change?

When we first launched G...