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...
Grav really never had a proper logo before. Frankly we never got around to it as we were too focused on making Grav as powerful and flexible as possible. But thanks to our good friend Christian at pixeden.com, we now have a new logo!
If you have been following us on Twitter you will know that along with the general development and improvement of Grav, we have been hard at work on an GUI Admin plugin. We have tweeted several screenshots from our initial design phase and also screenshots of the initial development. Things have been moving along really well and although we are not quite ready to release the plugin into the wild we are about 90% complete.
In this blog post we have provided a veritable slew of screenshots so you can see how things are progressing:
Since we launched the getgrav.org site, we have been repeatedly asked about a forum for new Grav users. We have been focused on improving Grav and releasing updates, but after finding Muut we were able to quickly set up a powerful real-time forum for our budding community.
Along with our new 0.9.0 release, we have also released three new plugins. The Archives plugin is used for displaying a list of months that can filter pages based on taxonomy. The GitHub plugin provides an easy way to access the GitHub API from Grav, either directly in plugins or in Twig templates. TwigCache is a plugin for advanced users that are trying to include slow requests or processing in their Twig template output.
Just over a week and a half after we made our beta 0.8.0 release available to the public, we are very pleased to announce the release of our latest 0.9.0 beta release. This is one of our biggest updates ever, and it contains lots of goodies! Read on to find out about what this release contains, and how the changes could potentially impact you!
Now that Grav is out in the wild as a Beta Release, I'de like to take this opportunity to outline what our plans are. Grav is already powering several sites and we wanted to make the core, some skeletons, and of course plugins available to those that want to check it out. However, Grav is not complete and there are several key areas we intend to focus on in the near future. So on to the Roadmap!
Updated 010/01/2015 to reflect current progress.