Development Blog

If you've moved a site to Grav 2.0 and a bit of {{ ... }} you had sitting in a page suddenly shows up as literal text instead of rendering, this post is for you. We changed how Twig runs inside page content in 2.0, and it's the single most common "wait, why did this stop working?" question we'...

Not every plugin needs a whole admin page. Sometimes you just want a button in the toolbar, or a little assistant in the corner, or a panel that pops out next to whatever you're editing. AI Pro drops a chat assistant into the bottom-right of every admin screen. Revisions Pro slides a revision-hi...

For a decade, Grav has had exactly one front door for managing a site. If you wanted to change something, you either edited the files by hand or you opened the admin plugin. And the admin was welded to the same rendering pipeline that served the public site, which is part of why it worked so well fo...

Yeti Search Pro isn't a settings page. Open it in Admin Next and you get a real search dashboard: index management, document counts, a live search tester, analytics, all in one place. SEO Magic is the same idea pointed at SEO: a crawl report, per-page scores, a re-crawl button, CSV export. Thes...

With Grav 2.0 getting closer, I've been living inside the new Admin2 for months now while we build it out, and a handful of features have completely changed how I work on my sites day to day. Admin2 is a ground-up rewrite of the Grav admin as a modern single-page app talking to the new Grav API...

If your plugin adds its own Markdown syntax — a callout block, a shortcode-like construct, a custom inline mark — you've historically done it by assigning a closure to Grav's Parsedown instance and registering a trigger character by hand. That approach still works in Grav 2.0, and it always will....

Markdown is the heart of writing content in Grav, and for Grav 2.0 we gave it a proper pass. The engine is still the same fast, Parsedown-based renderer it has always been, and everything you've written over the years still renders exactly as before. What's new is that Grav now understands a muc...

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 blueprint field types are the one place where you've actually got work to do, because the way they're built has genuinely change...

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. A chatbot in the corner, an autocomplete button in the editor, a "summarize this post" feature that ships your content off to so...