the candler blog

Markup as Language

Text, Writing,

I’m just now catching up with the excellent and gorgeous Contents Magazine. I love their publishing model. Each “issue” comes out over the course of a few weeks, basically a string of feature-length blog posts released on a sparing schedule. Smart.

I highly recommend all writers take a look at Mandy Brown’s article in the inaugural issue, Babies and the Bathwater. She lays out in plain English the way that the publishing landscape has changed for the better and how we, as writers, publishers, editors and readers, should be adapting.

One of my favorite parts of Mandy’s article involves something I just dealt with when switching from Wordpress to Octopress.

Content people are fond of leaving the code to the geeks while we debate the merits of the Oxford comma, but there is a difference between programming and markup. HTML, whose own name comes from the editor’s act of “marking up” a text, is an element of the text itself—a machine- and human-readable expression of the text’s underlying semantic structure. This is a language that we can and must speak, because it not only determines how the text looks but what it means.

Which brings us to more bathwater: WYSIWYG-style document editors that ignore the principles of semantic markup or prevent us from engaging with the text completely deserve a path down the drain. We need to adopt the mindset that markup—HTML, in particular—is part of our job, and we need to demand tools that let us do it.

I moved to a plain text workflow a while ago, but I always have trouble telling other people why I did, or why they should. The above quote pretty much says it all. Text is what I do.

It’s not that everyone should move to plain text, but people who write in public should have some understanding about what markup is. It’s possible to be vigilant and aware of markup in a WYSIWYG editor, but odds are you won’t notice if, for example, you’ve let a space fall into a block of bolded text or if you leave a letter or two unlinked.

Not every writer needs to learn code or Markdown or something, but at the very least they should have a passing understanding of what HTML is actually doing to their text. These are our words; they don’t come out of our heads by chance and we shouldn’t leave it up to the “nerds” to format it. The markup is part of our language whether we like it or not. If you haven’t yet, it’s time to learn it.

Working my way through the rest of Contents now. Also, check out Mandy’s other site, A working library, where she has followed the aforelinked article up with two additions: Represent and Markup.

Comments