It is one thing to mortify curiosity, another to conquer it.

— Robert Louis Stevenson, The Strange Case of Dr. Jekyll and Mr. Hyde

Recently, I stumbled across Kris Shaffer’s project, Open Music Theory, which is a textbook hosted entirely on Github utilizing Jekyll, a “blog-aware, static site generator.”” This means if someone else who teaches music theory wants in on the textbook, they can not only quickly create a website for it through Github (which is called “forking” a repository), but they can delete the chapters they don’t want and modify the text of others to their taste. In fact, if they think they have found an error they want to suggest back to the original work, they can submit what is called a pull request which alerts the author and they can decide to accept the request. If they do, this will change the version.

This has really intruiging implications for open textbook adoption. Further, I’ve always thought there’s something deeply romantic about the discourse that takes place around how a text is formed. It wasn’t until recently that I learned, thanks to my good friend and Open Education Resource wizard, Stacy Zemke, that there’s a little “Talk” tab where you can see conversations about Wikipedia articles.


This really caught me off guard when I thought about how much I have interacted with Wikipedia’s content over time but had never bothered to peel back the Wikipedia onion. How did I miss this? As an example, on the band’s Kiss’s page (see above), I can now read arguments about their genre. The official page says Hard Rock while others call it “Glam Rock” and “Glam Metal.” Real serious stuff. Or how Anton Fick, whoever that is, was never in the band in May 1980 despite the Wiki page saying he was.

Anton Fick was not an official member of Kiss in May 1980. That is a lie, a big lie. And it is an evil lie! —

Sorry Anton Fick. But, anyways, what was I talking about?

My point is that the presentation of information is one layer of the web. Discourse and social interaction is another layer. And before anyof this can take place, there is the construction of the information, which is in turn disseminated; allowing for the opportunity for interaction to take place.

Web Cycle
Web Cycle

I see a lot of folks looking at the presentation and the social aspects that come thereof, but (for whatever reason) I don’t see a lot of people looking at how we structure the architecture that allows this to happen. What are the principles in which we can harness to build education technologies? To what standards do we hold companies (and even ourselves)? How can we begin to define indie edtech?

Continuing on the Wikipedia analogy, it’s been interesting to look at the Federated Wiki project from the creator of the Wiki, Ward Cunningham, quoted from Wired:

I always felt bad that I owned all those pages,” he says. The central idea of a wiki — whether it’s driving Wikipedia or C2 — is that anyone can add or edit a page, but those pages all live on servers that someone else owns and controls.

Mike Caulfield explained this really well at his NWACC keynote:

In a traditional wiki, you have multiple people sharing a single server, and the server is the ultimate arbiter of what’s on the wiki. In a federated wiki, everyone has their own server which stores the records associated with them. But the meaning is made in your browser. Your browser pulls wiki records from all over the internet, and makes them look like they exist on a single server.

And while Mike is brilliantly thinking on this application to wikis, I’m thinking about everything as simple as my own personal website. How can I be the original owner, and thus the authority, on myself, but still lend the site’s infrastructure and content?

I started poking around an article Kris wrote on Hybrid Pedagogycalled “Push, Pull Fork: Github for Academics” and made an unexpected move this weekend. I exported my entire personal web site and blog, which runs on the WordPress platform, and moved it to Jekyll (hosted on Github). This means, for the first time in five years, I’m working on a site that is 100% WordPress free. The two different versions are below:

See the difference? 😉


Honestly, this is the major reason I moved over to Github pages. If you want to take pieces of my site, or the entire site, you now can download this with the click of a button. On Github, you can fork, meaning you can make a copy of my repository and experiment with the site without actually affecting my site. Go ahead and check out the repository!

This is something I wanted to explore mainly for my course site,, but tested out with my main domain for the first go around. And I’m pleasantly surprised with how much I’ve enjoyed the experience so far. It’s one thing to put a Creative Commons license on a website (really, I think that’s fantastic!), but that doesn’t make the webpage any easier to recreate. In fact, if you decided to pull anything out of my currently CC-licensed course site, you’d be met with the resistance of broken code that doesn’t work outside the ecosystem that I’ve created. Most people would spend more time than its worth.




Source: API Evangelist

Backup and Security

The second big win for Github and Jekyll is that my entire site is cloned to my Dropbox account. I’ve got a certain level of peace of mind in knowing that should anything happen to my site, I can always quickly reupload the entire thing. I’ve ran across more instances recently where I’m frantically trying to update all my different WordPress instances because of a large and necessary update and it feels good to veer a little further away from that. This is solved because while WordPress utilizes dynamic code and relies on database calls, Jekyll is purely static on the server side. Additionally, there’s no need to worry about someones WordPress plugin code.

So am I now anti-Wordpress? Absolutely not. In fact, I still would argue its the easiest entry point into publishing on the open web. It’s relatively user-friendly and gives you a lot of features that are great for a classroom, such as an intuitive admin panel and extreme flexibility. I’m just more interested moving beyond the presentation of information and coalescing around the idea of technology that has the necessary infrastructure for shareability and discussion.

Some “how” info

I tried to keep as much tech out of this post as possible (I probably failed, sorry…). So rather than posting a tutorial for how to make this happen, I’ll post some the links that helped me make the transition: