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.

Today along with Grav 0.9.13 being released, we have made several updates to five of our plugins that could cause your site to break. If you use Breadcrumbs, GitHub, Pagination, SnipCart or TaxonomyList plugins on your Grav site, you need to read this!

Back in October I penned a two piece series on setting up Yosemite with Apache with PHP, APC, Virtual Hosts and other goodies. There are other options available however, and one of the more popular ones is to use Vagrant to easily spin up a pre-configured virtual-machine.

In this tutorial, we'll step through the process of getting an RTD (ready-to-develop) environment installed on your Mac, Windows, or Linux desktop.

Today we have made several updates to the getgrav.org site. The most obvious of which is a refresh in header images, but also there several other updates throughout, but most focus on improving the downloads section.

Most people that are initially developing with Grav either modify the default Antimatter theme directly, or copy-and-rename it, providing a separate theme to modify. Each of these approaches have their own issues.

By modifying the base theme directly, any theme update will potentially overwrite changes made. By copying the theme, the theme will not be overridden, but updates and fixes to the core theme, have to be manually merged over to the copied theme.

There is a much simpler, and much more maintainable method however: Theme Inheritance.

This Special Guest article describes how to deploy (and work with) Grav utilizing Microsoft Azure for hosting and Bitbucket, acting as a source control repository.

In this second part of our two-part series, we will dive into using GitHub to manage our locally-developed site and integrate it with our live production environment. If you have not already done so, please ensure you have a working local Grav site as outlined in Part1 of this series.

So enough blathering, it's time to get our feet wet with GitHub!