Higher Ed is sometimes slow to change, which is, in many cases, a feature, not a bug. But when the pace of change in the broader society is so fast and constantly accelerating, it can lead to problems that linger (a word which will never not trigger this song for me) without resolution.
Back in 2009, Gardner Campbell published one of the most influential articles in my professional journey, A Personal Cyberinfrastructure. In it, Campbell argues that the web shouldn't be a series of templates and blanks to fill in, but a place to tinker, or, as I like to phrase it, muck about. He laments, however, that one of the things that many faculty have neither the time (nor inclination) to do, is tinker with/on the web, leading to a gap between the opportunities that modern learners have to learn and the capacity of faculty to even lead them to the fountain. This is a gap that has lingered (more Cranberries) as evidenced by the fact that clicking the link to Campbell's blog at the bottom on the EDUCause article shows his most recent post, 12 years after the original, and is still focused on the same idea.
But this isn't where the impulse for this post came from...that would have been this post by Bodong Chen, which I found looking for a way to integrate hypothes.is with a bookdown site, like this. As one might expect, when open tools are used, there is someone out there who has sorted out how to get them to play nicely.
Back to infrastructure...
Reading Chen's post on infrastructure immediately reminded me of Campbell's, (which led me to Campbell's new one), and has me tripping back through how I have built a personal knowledge infrastructure over the last few years by simply mucking about with web tools. I don't have any formal education in computer science (my undergrad degrees are in physical education, then an MEd, and now working on a PhD in education). I've written about a couple iterations on my workflow and infrastructure here and here and I think I have a thread on Twitter, but have you ever tried to search your Twitter timeline? I also posted about a possible collaborative workflow here.
I find that I am moving more and more towards a workflow that prioritizes creating content in text files and uses Markdown for styling (like this whole site as well as my new Bookdown site). One huge advantage of MD is that it is platform agnostic, so the content I have here on a Grav site can literally be copy/pasta'd into a bookdown site and published with very few, if any, edits aside from deleting the frontmatter that Grav uses. I recognize that learning to use a different infrastructure can be challenging, but, as Chen put it:
To change culture in science we need to change infrastructure.
So when I see recommendations like this one, I see the need for a change in infrastructure.
We @EdTechUVic have been working towards empowering learners to build their own knowledge infrastructures in the 5 (soon to be 6) undergrad courses that form a core of EdTech courses at UVic. I am currently teaching a course called Learning Design, EDCI335 where we host the course materials on an open WordPress site and invite learners to create their own WordPress sites on the Open EdTech Cooperative site, opened.ca. It certainly takes some time (usually a couple weeks) to orient learners to a new workflow, but it is very much worth the effort. Instead of learners losing their community to an abandoned, archived, or deleted LMS site, they get to use a single site that is under their control to curate their learning in accordance with their personal privacy preferences.
I've taught several sections of EDCI335, and a few of EDCI339, but this term was the first that I noticed several learners who were asking about being able to use their 'old' site for 335. Of course, the answer was a hearty 'Of course!'. There are 1 or 2 in this cohort who have menu links for all 5 current EDCI courses indicating a curated site of all of their learning over these courses.
If I were to recommend a set of tools for learners to build their own knowledge infrastructure, it might include things like:
- cPanel (which opens doors to...)
- Markdown (more doors...)
- git (in whatever GUI flavour...)
I'm sure there are others I would recall if I didn't have to vacuum the house, but these suggestions based on broad categories rather than discreet tools, would be an amazing starting point to allow learners to curate, build, and iterate on their findings over the course of a university career and beyond.