Most of the Grav 2.0 developer series so far has been quick wins. The compatibility flag is a one-line change. Adding API endpoints is a couple of event handlers. Custom …
19 mins
I've been running my own Grav sites through an AI agent for a few months now, and the thing that kept nagging me was how every other CMS handles AI. It's always bolted on…
11 mins
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 …
23 mins
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-edi…
10 mins
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 ta…
14 mins
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 update…
11 mins
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 head…
8 mins
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…
9 mins
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 sui…
11 mins