“Some Web pages also have colophons, which frequently contain (X)HTML, CSS, or usability standards compliance information and links to Web site validation tests.”

Hyperverses is a web site. Each page is compiled as HTML from markdown formatted plain text. The pages are served by an Apache web server.

The bit that does the marshalling from markdown bits to a full-fledge HTML site is middleman. Middleman was chosen because it is not blog software. I aim to build a website, not a blog. A blog has particular trappings such as calendar pages, a long scroll of a post-filled index page, categories. Sometimes comments. Hyperverses is a series of linked pages. The index is simply the most recently composed page. In this way the most fresh utterance becomes the primary entry point into the site.

Using middleman to build the site gives me a playground to tinker in. Hyperverses explores textuality and digitality, and extending middleman to suit my own experimentations is very much a part of that.

One day, if I am a good boy and can coax the muses into imbuing me with good coding practices, I might release a middleman plugin-as-CMS.


Currently there are no images on Hyperverses. This may change. I enjoy the written word more than video and the visual arts. I am not insensible to graphic design, however. I spent longer than I ought to have picking out fonts and tweaking the spacing and column width, among other things. The site title is set in LMR. The titles are set in Market Deco, red. The body text is set in Theano Old Style. All are generously licensed and freely available online.

Links on Hyperverses hopefully flatter traditional paper highlighters with imitation. Unvisited links have a yellow background, and visited a blue. Hyperverses is also concerned with analog methods of producing and consuming the written word, so I felt this slight homage was warranted. It is my only nod to skeumorphism.


While the site is not a blog, it ought to have an RSS feed. It does not. It will.

The site has footnotes. It does not yet have a navigational scheme of any real utility. A list of every page is not going to cut it.

While each update to the site is captured in a git repository, I do not yet have navigable versioning set up for individual lexia. Then again, I haven't felt the need to revise any published lexia yet either.

Text Editors

I collect text editors like Sauron collects jewelry. My go-to text editor is vim. I cut my teeth on, and still get use out of, emacs. Portions of this site have also been written in Mou, Byword, and Writing Kit. I primarily use Writing Kit on the iPad, and am very inconsistent with what I use on a computer. Writing Kit's killer feature is the ability to set a dark background, facilitating nighttime writing. I used to write in Moleskine Cahier notebooks, but then I took an iPad to the knee.

What To Make Of This

This site is a product of my sensibilities. In 2002 I ditched Windows in favor of Linux. I have primarily used Macs since 2011. I spend more time composing in vim and emacs than in web forms. I think plain text is a pretty neat idea. I dig footnotes1. I am pretty skeptical about hypertext, actually. I hate it when people redefine words. Reading means reading words, possibly with illustrations or inside of comics. (Unless you are visually impaired, in which case my personal taxonomy starts to totter.) I read way too much ftrain in college. When @eastgate notices something I've said on twitter, he tends to disagree with me. He is far more knowledgeable about hypertext than I. I am still learning. I will get things wrong. Heck, I am getting things wrong right now. Most of what I've written on this page should not be in a colophon. That's just not what a colophon is for. You know, I'm not entirely sure what a colophon is for. I just added a book on colophons to my Amazon wish list. Maybe someday I will write a better colophon.

  1. My best friend made fun of me the other day for reading a book on footnotes.