Table Of Contents
A few weeks ago I wrote that the internet used to be a library and now it is a store. Since then, one question keeps following me around: fine, but what do I actually do on Monday?
This post is the answer. It closes out a series I wrote for my HT 930 Digital Humanities students and for anyone else who is tired of renting their voice from a company. We have covered where to blog, static site generators, Omeka, Dublin Core, and the tildeverse. Now we put the pieces together.
One promise before we start. You do not have to delete everything tonight. Leaving the corporate web is not a breakup text. It is a move, and moves go better with boxes, labels, and a plan.
Step 1: Take inventory #
Open a spreadsheet. List every place your work lives. Social media accounts, old blogs, Google Docs you shared publicly, slide decks, conference talk videos, a Medium post from 2019 you have tried to forget. For each one, write down three things: what is there, whether you can export it, and whether anyone links to it.
Yes, this is a metadata exercise. You knew I would get Dublin Core in here somehow.
Step 2: Get a domain #
The IndieWeb community's Getting Started guide begins in the same place every time: get your own domain, set up hosting, create your pages. A domain costs roughly what you spend on coffee in a bad week, and it is the single most important thing on this list.
I made the full case for this in Why Scholars Should Own Their Online Presence. Your name should point to a place you control.
Step 3: Pick a home that fits your skills #
Match the tool to your patience:
- No code, please. Knowledge Commons, Bear Blog, or omg.lol. Point your domain at it and start writing.
- Some code, happily. Neocities or a tilde, where you write HTML by hand.
- Full control. A static site generator like Build Awesome, Hugo, or Jekyll, hosted for free or nearly free.
- A collection, not a blog. Omeka.net, with good Dublin Core records.
You can mix these. My own life involves a static site, an omg.lol address, and a book review blog on the AT Protocol.
Step 4: Export and bring your words home #
Go back to your spreadsheet and start moving things, oldest and most important first. Most platforms bury an export or download option somewhere in their settings. Grab it. Convert posts to Markdown when you can, because Markdown is plain text and plain text is the closest thing digital scholarship has to acid-free paper.
When you republish an old post on your own site, keep the original date.
Step 5: Publish first, share second #
This is the habit that changes everything. The IndieWeb calls it POSSE, Publish (on your) Own Site, Syndicate Elsewhere. You publish the original on your own domain, then share a link or a copy on social media. The canonical copy stays with you. If a platform vanishes, your work does not. You do not have to quit social media. Just stop making it the only home for your thinking.
Step 6: Connect your identity #
Add links from your homepage to your other profiles, such as your ORCID, your Knowledge Commons profile, Mastodon, and Bluesky, and mark them with rel="me":
<a href="https://hcommons.social/@yourname" rel="me">Mastodon</a>
According to the IndieWeb wiki, rel="me" tells the web that the destination represents the same person as your page. It enables web sign-in with your own domain and lets other sites verify that you are you.
Step 7: Feeds, mentions, and machine-readable bits #
Three small technical upgrades make your site a full citizen of the web:
- An RSS feed. Readers can follow you without an algorithm in the middle. Every tool in this series can make one.
- Microformats. A few class names in your HTML, like
h-entryfor posts, let feed readers and other tools read structured data from your site. - Webmentions. These let other sites tell yours when they link to you, so replies can live on your own pages. I walked through the setup in Enabling Webmentions in Build Awesome.
For scholars, add one more: citation metadata. My post on making blogs easier to cite with Zotero explains how to help reference managers import your posts correctly.
Step 8: Plan for preservation #
Independence comes with responsibility. If you are the platform now, you are also the archivist. Keep your source files in Git. Save important pages to the Internet Archive. Deposit finished work in a repository like Knowledge Commons Works. I covered these practices in Digital Humanities Part 5: Preserving Digital Humanities Projects, and the short version is this: plan the ending at the beginning.
Step 9: Find your people #
The independent web is quieter than the corporate one, so you have to build your own front porch. Keep a blogroll. Mine is at adamdjbrett.com/blogroll. Join a webring. Subscribe to feeds in a reader. Comment on people's posts by writing your own post and linking to theirs. This is how the web worked before the feed decided for you, and it still works.
Why this is digital humanities #
Digital humanities asks who makes knowledge, who keeps it, and who gets to find it. Those questions do not stop at the archive door. They apply to your own writing too. Every time you publish on a platform you do not control, you hand those decisions to someone else.
The independent web takes more effort and grows slowly. But it gives you something the corporate web never will: a place that is yours, built on open standards, that a reader in twenty years can still find.
So here is your Monday homework, HT 930 or not. Fill out the inventory spreadsheet. Buy the domain. Publish one post there first. Then send me the link. I will add you to my feed reader, and the web will be a little more like a library again.
Tags : digital-humanities indieweb smol-web open-access ht930 how-to
Webmentions
No webmentions yet.