The upcoming Festival of Learning (June 6 – 9, 2016) is shaping up to be quite the event, with nearly 400 registrants at last count. I am really looking forward to attending, and will also be sharing lots of open source Grav goodness at both the Maker Faire and my Studio session ‘Moving Beyond the LMS with Grav’.
Once you start using Grav you will also (more than likely) start using Markdown more than you used to. Wouldn’t it be great to apply your new Markdown skills to other aspects of your work? Well, recently I was introduced to the Markdown-based slides Web app swipe.to (thank you Bryan!) and I’ve really enjoyed using it so far.
I recently updated the list of problems that Grav has solved for me as an instructor/educator who facilitates a blended course, and I thought I would share them here:
(1/8) Here are the top 7 problems the @getgrav flat-file (no database) CMS has solved for me as an educator trying to move beyond...
Like any other Grav theme, both of the included Course Hub themes (‘Course Hub Bones’ and ‘Course Hub Bootstrap’) can be visually customized using CSS and/or altering their Twig template files. However, if you make changes directly to the Course Hub theme these will be overwritten when that Course Hub theme is updated. So, what to do?
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.