Recently I tweeted about possible workflows with Grav, and I thought I would share them here:

So, what workflows does @getgrav support? One example is to use the desktop app @Typora to create/edit Markdown content and then @GitHubDesktop to preview and push changes to your Grav site👇Alternatively, you could edit and push changes with just one app, such as @AtomEditor⏱ pic.twitter.com/EaIyikgQFh

— Hibbitts Design (@hibbittsdesign) June 25, 2019

And because Markdown is the primary content type (HTML is also supported) you can leverage the open and collaborative ecosystem of Git (@github, @gitlab, etc) for others to propose changes and also to enable direct access to raw content for supporting the 5Rs of #OER.

— Hibbitts Design (@hibbittsdesign) June 25, 2019

This use of the Git ecosystem also brings some strategic options - like using the upcoming @openetc Cloudron service for empowering students to collaborate on course materials on a FIPPA server while using a commercial supplier for Web hosting… such as my fav @ReclaimHosting 👇 pic.twitter.com/pffhiwiQWd

— Hibbitts Design (@hibbittsdesign) June 25, 2019

This approach also makes it feasible for multiple course instructors/facilitators to contribute to the content of one or more courses, in a manner where each revision is tracked and is reversible. Over time, I expect the editing experience of Git-based Web apps to improve too🚀

— Hibbitts Design (@hibbittsdesign) June 25, 2019

This seems like a good time to also show the various types of review screens provided before any proposed changes are approved (and even after approval changes can be rolled back)👇 pic.twitter.com/j5uVu7OmwB

— Hibbitts Design (@hibbittsdesign) June 25, 2019