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...
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.