Self-publishing OERs: Absolutely the right choice

Third-party hosting services (like WordPress!), as our readings point out, have several disadvantages, including their potential instability (i.e., they can disappear at any time, taking your content with them) as well as the lack of control you have over what else happens in that space (our reading’s example was YouTube advertising; I would also add commenting, because this is the reason many schools in my area block access to YouTube).

For my final project, I chose to set up a wiki because I wanted to learn how to use a new tool. But the wiki-hosting sites do not allow a lot of customization; in my case, I want to be able to control formatting, colors, and so on. In addition, free wiki-hosting sites also have some potential for putting ads on your wiki. (For instance, one OER I visited in my quest had advertisements from the Koch brothers—right-wing owners of the second largest private company in the United States—ads that were a complete contradiction to the stated purpose of the site itself.

So instead of choosing a third-party site, I decided to self-publish my wiki using a new site for my business. I am moving my files, etc., from Yahoo Small Business hosting (which charges $35 a month to host my website) to, which charges only $6 a month. When I first started my freelance business, I knew nothing about Web publishing and those were also the days of raw HTML. Yahoo offered a service to help build the site, and so I chose that option. Fast forward to now, in which not only have I learned a lot about Web publishing but also I have access to mountains of free tools to help me build a site. Bluehost is wonderful, too, because it has scripts that will set up a WordPress or wiki engine for you. So my hosted account Editorial Partners LLC is the host of my Professional Writing wiki, the final project for my course and an ongoing project for me.

For only $6 a month, an amount many people spend daily on a latte or chai tea from Starbucks, I have a space on the Web that is entirely mine: I control what’s there (and what’s not), there are no unwanted advertisements, very few schools have blocked the site from their students (none, actually), and it will never disappear unless I make it. I can change colors, change my whole theme, create subdirectories for different projects or clients, and so on. In addition, I researched different types of wikis and chose Dokuwiki as my engine because it creates text files rather than database entries, which means they are accessible on any device, easily printed, and require relatively low bandwidth and memory. And because they are text files, they play well with audio devices for people with sight disabilities and can be saved as a document that can easily be modified (e.g., scaling up the font size).

The only “down side” that I see (aside from the programming bits I need to learn—and for me, learning new tools never has a down side) is that these resources are less easily found on the Web. For instance, if I google “professional writing resources,” my little wiki does not appear in the search results. Perhaps that is something to add to the course resources, in the area of publishing: the basics of metadata, how search engines can find you, how you could submit to OER respositories, etc.

2 thoughts on “Self-publishing OERs: Absolutely the right choice

  1. Did you consider a self-hosted WordPress blog (open source) instead? Then you could export all the content from this site. In addition, WordPress blogs are very search engine friendly.

    • leahgrrl says:

      Yes, I’ve done installations for a couple of websites, and I’m in the process of migrating my old freelance website from Yahoo to a hosting service so I can pull in this blog and other things (and save money!). I started this blog as a course requirement for Connectivism and Connected Knowledge 2011 and continue my studies through it. I enjoyed very much your post on “Learning Is Everywhere”; for the past year I’ve been working on a business plan that helps organizations with on-call, just-in-time staff learning support (I wrote some intial thoughts in this blog). Thanks for stopping by!

Leave a Reply

Your email address will not be published. Required fields are marked *