Skip to content
This repository has been archived by the owner on Feb 24, 2019. It is now read-only.

Latest commit

 

History

History
56 lines (52 loc) · 5.23 KB

File metadata and controls

56 lines (52 loc) · 5.23 KB
Error in user YAML: (<unknown>): found character that cannot start any token while scanning for the next token at line 18 column 22
---
title: "A Few Thoughts About... Why Use the Grav OER Content Space?"
date: 02/07/2017
published: true
continue_link: true
header_image: false
taxonomy:
    category: blog
    tag:
        - GravCMS
        - Markdown
        - GitHub
        - GitLab
        - GitSync
        - Open
        - OER
metadata:
    'twitter:card' : summary
    'twitter:site' : @hibbittsdesign
    'twitter:title' : A Few Thoughts About Why Use the Grav OER Content Space?
    'twitter:description' : A collection of tweets highlighting the goals of the Grav Open Educational Resources (OER) Content Space project.
    'twitter:image': 'http://hibbittsdesign.org/blog/posts/2017-02-07-a-few-thoughts-about-why-use-the-grav-oer-content-space/screenshot.jpg'
    'og:title' : A Few Thoughts About... Why Use the Grav OER Content Space?
    'og:image' : 'http://hibbittsdesign.org/blog/posts/2017-02-07-a-few-thoughts-about-why-use-the-grav-oer-content-space/screenshot.jpg'
    'og:description' : A collection of tweets highlighting the goals of the Grav Open Educational Resources (OER) Content Space project.
    'og:url' : http://www.hibbittsdesign.org/blog/posts/2017-02-07-a-few-thoughts-about-why-use-the-grav-oer-content-space
---

I recently tweeted some reasons for using the Grav Open Educational Resources (OER) Content Space, and I thought I would share them here:

(1/8) So, perhaps you are wondering... why use the @getgrav CMS Open Educational Resources (#OER) Content Space Project? #openaccess #LMS

— Hibbitts Design (@hibbittsdesign) February 6, 2017
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

===


(2/8) To quickly leverage a modern flat-file CMS (i.e. Grav) for the creation and presentation of OER content

— Hibbitts Design (@hibbittsdesign) February 6, 2017
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

(3/8) To provide direct access to OER raw content (in Markdown or HTML format) to facilitate easier reuse and remixes

— Hibbitts Design (@hibbittsdesign) February 6, 2017
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

(4/8) To support collaboration and version control of your OER content with the Git service (e.g. GitHub, GitLab, etc.) of your choice

— Hibbitts Design (@hibbittsdesign) February 6, 2017
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

(5/8) To quickly and easily update OER content online or locally using the tools of your choice

— Hibbitts Design (@hibbittsdesign) February 6, 2017
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

(6/8) To provide a mobile and multi-device friendly visual presentation of your OER content

— Hibbitts Design (@hibbittsdesign) February 6, 2017
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

(7/8) To easily customize the presentation of your OER content using a visual drag-and-drop theme builder (i.e. @gantry_fw)

— Hibbitts Design (@hibbittsdesign) February 6, 2017
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>

(8/8) Want to learn more? Visit the GitHub repository of the project at https://t.co/o53uFgzUtS and explore demo at https://t.co/EbKOUqsbQg.

— Hibbitts Design (@hibbittsdesign) February 6, 2017
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>