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 the LMS:

— Hibbitts Design (@hibbittsdesign) May 3, 2016

(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.

— Hibbitts Design (@hibbittsdesign) May 3, 2016

(3/8) Existing LMSs/CMSs most only support limited collaborative editing. Content and logic are BOTH editable collaboratively (i.e. GitHub).

— Hibbitts Design (@hibbittsdesign) May 3, 2016

(4/8) Existing LMSs/CMSs are often blob-based, where each page is a single blog of content rather than modular/reusable CONTENT CHUNKS.

— Hibbitts Design (@hibbittsdesign) May 3, 2016

(5/8) Existing LMSs/CMSs are often database-driven which can impact PERFORMANCE with even the simplest content presentation tasks.

— Hibbitts Design (@hibbittsdesign) May 3, 2016

(6/8) Existing LMSs/CMSs can often only be edited by pre-defined interfaces. A flat-file CMS gives authors and contributors tool CHOICE.

— Hibbitts Design (@hibbittsdesign) May 3, 2016

(7/8) Existing LMSs/CMSs often require IT involvement for content or server migration, while a flat-file CMS only needs simple FILE COPYING.

— Hibbitts Design (@hibbittsdesign) May 3, 2016

(8/8) Existing LMSs/CMSs often prevent content from being globally searched and replaced by authors. Content as FILES removes this issue.

— Hibbitts Design (@hibbittsdesign) May 3, 2016