One of the things that I’m confronting as I write this book is my overwhelming desire to use hyperlinks. The link is truly one of the great affordances of blogging: each time I set out to say something new, I can easily point to things that I’ve already said. As I’ve been thinking more about this issue, I realize that links play two slightly different roles in my posts. The first is a straightforward offer of more information. Any time I type the word ‘paragraph’, for instance, I can render it a link. My reader doesn’t necessarily need to know what I think about paragraphs to continue reading; I’m just putting it out there, in case they want more. In the second case, however, I’m using a link precisely because the reader does need to know what I mean by the term, and I don’t presently want to tell them. I often do this with ‘metadiscourse’, a term that I use frequently and that I know to be unfamiliar to many readers. Broadly speaking then, some links offer the reader supplementary information; others offer the reader something that may be essential now. In both cases, the reader is able to choose their own adventure: they can take a byway or, if they wish, just stick with the main path. Links allow me to construct each post to stand alone, but where I think my point will be enhanced by a familiarity with earlier posts, I can indicate that without breaking my stride. Every time I create a link, I take pleasure in the efficacy of these potential digressions: offered but not mandated.
In the process of composing the linear narrative of a physical book manuscript, however, I’m struggling to manage these types of internal references. Like all writers (of non-digital texts), I’m trying to make an accurate estimation about what type of orienting information my readers might need. In the earliest drafts, I found myself writing versions of ‘see above’ and ‘see below’ way too much. No reader wants to be constantly dispatched to a different precinct of a book. We expect the writer to dole out information in the exact right way: enough repetition that we know where we are, enough anticipation that we know where we are going, and never a suspicion that we’ve missed something. As a writer, I’m learning to be more judicious, both in providing reiterations of key points and in trusting the reader’s ability to manage without such reminders. If they’ve been paying attention—and I’ve done a good enough job—they’ll understand abbreviated references to earlier material and they’ll have faith that they’re being given what they need now.
This issue doesn’t just affect someone like me who is making this particular blog-to-book transition. Any academic writer is going to have to puzzle through how to give the reader enough guidance to orient them on their journey through a text. In general, we accomplish this task through the prudent use of signposting and strategic repetition. As we’ve discussed often here, signposting is a particularly crucial type of metadiscourse. A simple ‘as will be discussed below’, to take a common example, lets the reader know that they’re not expected to fully grasp that topic yet. This placeholder allows the writer to raise an idea without explaining it or needing the reader to understand it. If the writer lacked this option, they would have to try to explain everything at once or would have to hope that the perplexed reader sticks around long enough for full edification. We all know that neither of those options is ideal. Prioritization—a determination that a reader needs this now and can wait till later for that—is part of our job as writer. A promise of an elaboration to come is a crucial tool for managing that dynamic.
Similarly, using a device like ‘as discussed above’ prevents the reader from mistaking strategic repetition for inadvertent repetition or for a new idea. If a writer repeats themself and gives no indication that the repetition is strategic, the reader may be annoyed or, worse, may question the acuity of their own reading. That is, they may suspect that they’ve misread something because they thought this idea had already been introduced. Being puzzled about repetition isn’t as deleterious as being puzzled about new information, but both have the capacity to interrupt our forward momentum as readers.
As writers, we all understand the need to deploy appropriate markers of anticipation and summation, of alluding to what is to come and recapping what has already happened. The tricky part comes in the negotiation of what is, in each context, appropriate. As I continue working on this manuscript, my ability to negotiate the appropriate markers—and thus to live without links—is slowly improving. You’ll have to read the eventual book to see if I end up with a well managed flow of information!
This post is the third in a series of book reflections posts. At least once a month, I’ll come here to talk about my progress and, more importantly, about my thoughts on the writing process. The progress reports are really just for me: I’m using the public nature of the blog to keep me accountable. The actual point of these posts will be what I’m learning about writing and how these insights connect to the topics covered here on the blog.
Status Update: In the spirit of public transparency about my book writing process, I’m going to conclude these book reflections posts with a status update. I am currently even less on schedule than I was in my last update. I still haven’t finished my provisional revision of Part One, and I didn’t get Chapter Four completely drafted by March 1st. I hope to be able to complete these two tasks in the next week and move on to Chapter Five on March 11th. I think my next book reflections post will be on the dynamics of managing an artificial and aspirational writing schedule!
Every university I work with requires doctoral students to submit hard copy, making hyperlinks impossible. It makes me wonder which century universities are living in.
You probably know them already, but there are several books on use of time fro academic writing, liste don p. 2 here: http://www.frontinus.org.uk/postcards/writing.pdf
I’ve found the Zerubavel book really helpful.