Creating open course environments with GitLab and Grav CMS
To search repositories and projects, login to gitlab.com . Suggestions GitLab Duo Agent Platform Code Suggestions (AI) CI/CD GitLab on AWS GitLab on Google Cloud Why GitLab? Published on: October 12, 2017 9 min read Enabling an open and collaborative course environment with GitLab and the Grav CMS Guest author Paul Hibbitts shares how he combines GitLab with the flat-file CMS Grav to provide an open, collaborative and flexible environment that partners with his institution's LMS.
Paul Hibbitts open source collaboration Tech-savvy educators! Do you want to: Share your course materials more openly? Support collaborative editing by students and fellow educators? Deliver a better multi-device experience of your course materials? Be able to update your online course materials in as little as 30 seconds? And, in general, move beyond the constraints of your current Learning Management System? If this sounds like you, then the combination of an institutionally hosted instance of GitLab and a modern flat-file (no database) Content Management System such as Grav might be your answer!
As an educator and software interaction designer, I am always striving to deliver a better experience for my students, both in person and online. In the past several years this has led me to ‘flipping’ the Learning Management System, where I use an alternative platform instead of the LMS as the primary online environment. Many instructors (including myself) have taken this approach in the past using a traditional platform such as WordPress, but I found significant new benefits from partnering the LMS with a more modern platform that was built to take full advantage of the open and collaborative ecosystem (i.e.
Git, GitLab, GitHub, etc.) we now have. With the above approach, direct links are provided to any appropriate LMS elements and sensitive student data remains in the LMS. Common elements across multiple courses, like calendars, assignments, discussion forums, and grades are still stored in the LMS for single-point access by students. While perhaps not suited for university-wide adoption, this is a very viable and productive approach for individual instructors and their students while we wait for more open and adaptable institutional-level tools to become available.
Open and Collaborative ‘Flipped’ LMS Approach Using GitLab and the Grav CMS Fortunately, my university ( Simon Fraser University , or SFU, in Burnaby, BC, Canada) also provides an institutionally hosted instance of GitLab which not only gives me an ideal workspace for my online course materials, but also supports single sign-on so my students can easily contribute to these materials as well. By combining GitLab with the modern flat-file CMS Grav, my institution's LMS and a small collection of other open source web apps, I’ve been able to reach more of my desired teaching goals (such as providing an anytime, anywhere performance support tool with real-time chat) for my own courses than by using the LMS as the primary online space.
In addition, I’ve made the resulting software open source to also help other instructors reach their own goals – more about this project at the end of this article! Why open source software? The advantages of using open source software in the field of education are well documented elsewhere (see Open Source Software in Education ), but from my own viewpoint, the things I value most are: having more control over the software I use, the online communities often found with open software projects, public communication with the team developing the software, and the wide range of ways I can contribute to projects.
I’ve also been keenly following several other open source, institutional-level learning ecosystem efforts, such as ELMSLN (a platform for building and sustaining innovation in course technologies) and TSUGI (a framework for building learning tools). Why GitLab? GitLab meets several key criteria for its use in a learning ecosystem. First, it is open source software itself and secondly, it is possible to install an instance of GitLab on your own server.
For universities and colleges this enhances the benefits of being open source in the first place as single sign-on and the storage of sensitive student data remains in the sole control of the institution. Using GitLab in combination with the GitHub Desktop application I can also very quickly update my online course sites from my desktop, while at the same time being able to then edit course site materials with any code editor I like.
Most importantly, students feel like active course participants when they see they are welcome to suggest changes to the course site, or even just to make corrections to course materials. Everything is of course version controlled, which means as a repository administrator I can easily see each and every change before approving them. For changes not immediately approved I can then start a discussion via GitLab with the author of the proposed change to work out any needed further changes, etc.
GitLab brings an industrial-strength software and document collaboration tool into the reach of my fellow university colleagues and students. Why Grav CMS? While looking for an open source platform to support a learning ecosystem I evaluated multiple options, including self-hosting (for full administrative control) WordPress, Concrete5, Moodle and others. I then came across a number of apps under the category of ‘flat-file CMS,’ meaning that content was stored in files instead of a database.
I could see that content as files would be a perfect partner for using a web-based Git service (such as GitLab, GitHub , GitBook , etc.) to share and collaboratively edit content. With such a partnership, CMS content can be automatically backed up in a straightforward manner, while also tracking all revisions along the way. Digging deeper, I discovered the open source flat-file CMS Grav (by the team behind RocketTheme ) used Markdown – the native format for Web-based Git services such as GitLab – for content.
Markdown is also an excellent system-independent format to support the ‘5Rs’ of Open Education Resources (Retain, Reuse, Revise, Remix, and Redistribute). Editing Markdown content in the Grav CMS Admin Panel Grav uses many existing modern standards and open source components, such as the very user-friendly Twig language (courtesy of Symfony) instead of pure PHP for theme templating. Grav also supports modular and custom content types, and was designed from the ground-up to be both fast and extensible.
In addition, with the creation of the open source Git Sync plugin (by Trilby Media ) it is now easier than ever to do two-way syncing of Grav content between a production server, Git repository and an optional local development instance. It is even possible to sync theme files, which determine the actual functionality and presentation of a site, so educators (or perhaps their tech-savvy students) can directly help other educators needing assistance in additional customization of their Grav sites.
It should be noted that Grav is not a static site generator, but rather a file-based CMS which supports not only dynamic content but also an online Admin Panel. CMPT-363 Open Course Hub For my SFU course CMPT-363 User Interface Design this Fall, I will not only be using GitLab and Grav (hosted on the educationally focused Reclaim Hosting ), but also a number of other web apps (also mostly open source) to provide a learning ecosystem to my students.
Since Grav itself is open and extensible, I can easily add in Javascript elements for a Livechat (which my students have told me they love) thanks to Rocket.Chat , responsive Markdown-based slide embeds thanks to the commercial Swipe.to web app, and links to an anonymous course feedback form thanks to Sandstorm.IO and Quick Survey . To address both various other teaching goals (the LMS actually does some things quite reasonably) and student data privacy concerns, I
The rest of this page is on the live site.