Something I’ve been thinking about lately is the ubiquity of WordPress for Domain of One’s Own-like initiatives. I’m a long-time WordPress user. Started using it for course sites and student blogging back in mid-2000s. Also launched a hybrid Digital Humanities degree program that used WordPress multisite for course sites as an alternative to the LMS. I still tend to teach WordPress for web design, because if a 1/3 of the web is WordPress, then giving students skills in developing WordPress sites seems super valuable.
And, yet, thinking about the philosophies underpinning Domain of One’s Own has made me want to start experimenting more with other platforms. In part to offer alternatives to students thinking about what to put on their Domain, but also because WordPress is not really tuned for all the uses I put it to.
So, this last year, I mapped a Domain (that I got through UMW DoOO) to a Medium site for my Digital Studies course.
And, now, I’m experimenting with two different approaches to installing Ghost via Reclaim: one for my personal site and the other for my new daddy blog. Thanks for the help, Tim
What I’m wanting to think through is a way to offer students and faculty a menu of options for stuff to put on their domains, which isn’t WordPress or WordPress or WordPress. But I’m also sensitive to the fact that “you can install ANYTHING” can be overwhelming. My impulse (and what we’re working on for UMW’s DoOO) is to highlight three platforms/applications and approaches to using those. Tuning support and development work toward those three approaches. But, then, of course, also saying and supporting “you can install ANYTHING.”
I’m curious if others have been thinking through how to strike this balance.