With Grav being a flat-file (no database) CMS tech-savvy educators have a wider range of possible development and deployment options for their Grav Course Hubs than most other database-driven systems. Recently I’ve been exploring an on-line alternative to my currently preferred local development approach, so I thought I would share both together for easier comparison. Both approaches will let you safely develop and test your Grav site before deploying changes to a live production server.
Here is a quick sampling of some Grav CMS Course Companion workflows:
Video 1. Simple install of the course companion on a Web server (in under 30 seconds).
Figure 1. Flipped-LMS approach using Grav CMS, GitHub, and Deploy.
What is a flipped LMS?
A flipped LMS approach is where an open platform, in the control of course participants, serves as an alternative front-end to the institutional LMS
Figure 1. Flipped-LMS approach.
Why flip the LMS?
To support pedagogical goals unmet by current LMS/platform
To deliver a better student (and facilitator) experience
To increase capability of access, sharing and collaboration
As a modern flat-file CMS, Grav can take full advantage of today’s ecosystem of open and collaborative editing services, such as GitHub or GitLab. In this article we will look at how to easily use Grav with GitHub Desktop (which uses GitHub and Git for source control) and the automatic deployment service Deploy to result in a very efficient, open and collaborative workflow. No scripting or command line interactions will be required, I promise.