---
title: "A Few Thoughts About... What Problems Grav Can Solve for Instructors"
date: 05/09/2016
published: true
continue_link: false
header_image: false
taxonomy:
    category: blog
    tag:
        - GravCMS
metadata:
    'twitter:card' : summary
    'twitter:site' : @hibbittsdesign
    'twitter:title' : A Few Thoughts About What Problems Grav Can Solve for Instructors
    'twitter:description' : The top 7 problems that the Grav CMS has solved for me as an educator trying to move beyond the LMS.
    'twitter:image': 'http://hibbittsdesign.org/blog/posts/2016-05-09-a-few-thoughts-about-what-problems-grav-can-solve-for-instructors/gravdotorg.png'
---

_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:_

<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">(1/8) Here are the top 7 problems the <a href="https://twitter.com/getgrav">@getgrav</a> flat-file (no database) CMS has solved for me as an educator trying to move beyond the LMS:</p>&mdash; Hibbitts Design (@hibbittsdesign) <a href="https://twitter.com/hibbittsdesign/status/727632035741732864">May 3, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
<br>
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">(2/8) Existing LMSs/CMSs controlled by IT are often locked down. A site built with a flat-file CMS enables easier HTML/CSS CUSTOMIZATIONS.</p>&mdash; Hibbitts Design (@hibbittsdesign) <a href="https://twitter.com/hibbittsdesign/status/727632076531335168">May 3, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
<br>
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">(3/8) Existing LMSs/CMSs most only support limited collaborative editing. Content and logic are BOTH editable collaboratively (i.e. GitHub).</p>&mdash; Hibbitts Design (@hibbittsdesign) <a href="https://twitter.com/hibbittsdesign/status/727632113218953216">May 3, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
<br>
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">(4/8) Existing LMSs/CMSs are often blob-based, where each page is a single blog of content rather than modular/reusable CONTENT CHUNKS.</p>&mdash; Hibbitts Design (@hibbittsdesign) <a href="https://twitter.com/hibbittsdesign/status/727632148941824000">May 3, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
<br>
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">(5/8) Existing LMSs/CMSs are often database-driven which can impact PERFORMANCE with even the simplest content presentation tasks.</p>&mdash; Hibbitts Design (@hibbittsdesign) <a href="https://twitter.com/hibbittsdesign/status/727632189790167041">May 3, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
<br>
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">(6/8) Existing LMSs/CMSs can often only be edited by pre-defined interfaces. A flat-file CMS gives authors and contributors tool CHOICE.</p>&mdash; Hibbitts Design (@hibbittsdesign) <a href="https://twitter.com/hibbittsdesign/status/727632229367611392">May 3, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
<br>
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">(7/8) Existing LMSs/CMSs often require IT involvement for content or server migration, while a flat-file CMS only needs simple FILE COPYING.</p>&mdash; Hibbitts Design (@hibbittsdesign) <a href="https://twitter.com/hibbittsdesign/status/727632263001690113">May 3, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
<br>
<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">(8/8) Existing LMSs/CMSs often prevent content from being globally searched and replaced by authors. Content as FILES removes this issue.</p>&mdash; Hibbitts Design (@hibbittsdesign) <a href="https://twitter.com/hibbittsdesign/status/727632316462305280">May 3, 2016</a></blockquote>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>