Blog

Exploring and Building Open [Source] Software for Learning Ecosystems and OER

EXPERIENCE DESIGN / EDUCATION / OER/ MULTI-DEVICE / GRAV CMS

Recently, I’ve been exploring ways to use the modern flat-file CMS Grav as a simple open publishing tool. Grav is a natural candidate for this usage, as all content is stored as individual files which can be stored on a variety of open and collaborative editing environments (e.g. GitHub).

I’ve been trying to formulate a sustainable approach of an open design practice for my experience design work in the education field, and I think I am getting closer to defining a workable approach:

While every project has different needs, I am finding that database-based CMS platforms such as WordPress are often too complex/feature-laden for the needs of individual educators/publishers. In contrast, flat-file CMS platforms offer more simplicity and control. Here are some of the key reasons I am now focusing on using modern flat-file CMSs for my development work (especially when implementing a flipped LMS approach):

In a recent discussion the question of how a traditional LMS implementation compares to a flipped LMS was asked. Here are my initial thoughts so far, based on my experiences with several institutional LMSs and using the flat-file CMS Grav in a flipped-LMS approach:

So, why would course facilitators want to utilize a flipped-LMS approach?

Here are three primary reasons that come to mind:

  • To support pedagogical goals unmet by current LMS/platform
  • To increase capability of access, sharing and collaboration
  • To deliver a better student (and facilitator) e...

One of the (many) great things about using the open source CMS Grav for a flipped-LMS approach is that no database is required, which makes running a local copy of Grav on your computer for testing purposes a very straightforward process. This also makes deployment to a Web server a breeze - just a simple folder copy.

But first, what does the term ‘flat-file CMS’ mean? In a nutshell, content is stored as individual text files rather than in a database.

While I’ve been using the term learner experience (LX) design myself for several years, I am finding it more and more problematic.

Too often people think of learner experience design separate from, or a subset of, user experience design, but this is misleading and certainly not what I have found the situation to be. Learner experience design also assumes the audience in question are just learners, which is not the case either (they are people with goals to accomplish).

Key learner experience design goals:

  • Engaging
  • Convenient
  • Organized
  • Relevant
  • Enjoyable