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!

As promised, today I'm going to start covering the process of setting up a development environment utilizing GitHub to manage the code throughout the development life cycle, resulting in publishing to a live site.

As I blogged about the other day, as a web developer, the most efficient and more reliable development strategy is to develop locally, then push your local development to your production site. If you have not ready my post on Grav Development Strategy, you might want to read that first.

Over the course of this two-part series, we will cover the process from start to finish, and I hope to show you that this process is one that will enable you to develop and maintain your site more efficiently.

So, you’ve decided to get Grav and build a site with it. Congratulations! Building with Grav gives you the power and flexibility you need to realize your site but you need to develop that site first. Using an efficient development strategy will allow you to build your site faster and hassle-free. You might even have fun while doing it!

When you look at how easy it is to set Grav up and get it running on a remote server, it can be very tempting to just do development there, especially given the fact that there are no databases to migrate over, and everything is file-based. However, don't be tempted by this approach! In this blog post I'll endeavor to explain why...