Ever since we added support for multi-language and translations in the beta releases of Grav, we have been asked about translating Grav into various languages. This has typically been centered around the Admin plugin as that has the most translation strings and subsequently is the most common focus of translation needs.

Up until this point, the process of translation involved Forking the plugin repository on GitHub, making edits or additions in the various languages, then submitting a pull request. This worked OK at first, but as the plugin became more complex, more strings were getting added, it became harder and harder to manage. We needed a better solution. Enter Crowdin to the rescue!

! We have decided to change the minimum requirements for Grav from PHP 5.4.40 to 5.5.9 to stay in line with the new minimum version of some of our key vendor libraries.

As is typical with these kinds of things, We launched Grav 1.0 right around the same time that PHP 7.0 was released, and everything seemed great. Even though Grav runs amazingly on PHP 7.0 there are some PHP 7.0 compatibility issues within some of the vendor libraries that Grav relies upon.

These external libraries are continually updated and have started dropping support for older EOL (End of Life) versions of PHP. In order to continue using the latest versions of these libraries and support the new PHP 7.0, we need to keep our requirements in line with our key libraries. Grav currently supports PHP 5.4 which was an actively supported version when we started developing Grav, but is no longer supported according to the PHP Supported Versions document.

Over the past weekend, the Grav project surpassed 3,000 stars on GitHub! This is a huge achievement for the Grav team, serving as a testament of the incredible community that has grown over the past year around a new open source flat-file CMS.

Grav is still a very young content management system...

After being in beta for just over a year, with nearly 50 releases and 250 closed issues, Grav is now a full featured CMS with all our roadmap tasks completed. We really could of put the Version 1.0 rubber stamp on Grav some time ago, but we decided to hold off until we had the admin plugin stable also. With an extensive beta development phase of it's own, the Grav admin has undergone a series of solid releases to add new functionality and address bugs. It is also on the cusp of getting a stable version number as we have 161 closed issues and no critical bugs currently open.

Grav is already one of the fastest CMS options available, but it's possible to easily transform your Grav-based site into a world-class performer. A CDN or Content Delivery Network and some new Grav features can make this possible.

It has been a little over 10 months since we launched the first public beta of Grav. We quickly reached our 0.9.0 release goals as outlined in the Grav Roadmap, and have spent the subsequent months bug fixing, adding requested features, and laying the groundwork for our upcoming 1.0.0 release.

A common question has been raised a few times on the forum, and it usually goes something like this:

"With traditional CMS platforms such as Joomla, WordPress, Drupal, etc, I can easily change themes and my site is instantly transformed. How does this work in Grav?"

In an effort to answer this question, I will endeavor to provide some of the fundamental operating paradigms behind traditional CMS platforms and how Grav's approach turns them on their heads.

I was asked on our Slack chat the other day about the best way to debug Grav plugins. I started to type out my process but quickly realized it would be better to show rather than tell. Yesterday I did a quick 30 minute Google Hangout and because it was of the Air variety, it also recorded it for posterity on YouTube.

I thought I would mention that OSTraining has published an interview I did with them that outlines what Grav is about and its place in the universe.