Practice What You Preach:

October 15, 2018

Part of collaborating on a project is finding the right people to work with, but sometimes those people in the world of academia are miles apart. Such was the case with our editors for Soundwriting Pedagogies, Courtney S. Danforth, Kyle D. Stedman, and Michael J. Faris, who offer us a glimpse into how a notion of collaboration turned into a phenomenal book project that performs the very act it argues for within its figurative covers. Stedman writes when reflecting on this project, “I know of no other collection of webtexts that can also be subscribed to in your favorite podcast app. Yes, some chapters make more sense than others in the audio-only context, but that’s part of the fun and excitement. I think we broke new ground there.” The editors of Soundwriting Pedagogies allow us to see parts of their own creative process and the affordances and constraints they faced when taking on a project of this caliber. Our glimpse into the project from start to finish provides future authors of digital books some considerations as they think about taking an idea from start to digital finish.

Finding your People

Often when one meets people at a conference or event who are talking about the same things you are, there’s instant affinity. Later that affinity turns into an idea and an overture of collaboration. Danforth had always been interested in sound, but “started teaching soundwriting in a context of disability”;“that’s the direction my work is taking.” She saw a gap that she and her co-editors might be able to fill as “There was an exciting subfield of sonic rhetoric emerging but so much of the scholarship was intensely theoretical.” So...she reached out to Stedman in an email:

9 Dec 2014, Courtney to Kyle: I like working with you. Would you be interested in co-special-editing a journal issue on soundwriting pedagogy?

While a journal issue did not end up materializing, Danforth saw a possibility to look at teaching in different way and could see this being something larger like a book. She writes, “As faculty at teaching institutions, Kyle and I wanted to read more about how our colleagues were applying that theory in the classroom. Since that book didn’t exist yet, we decided to make one ourselves.” In an email to Danforth, Stedman began brainstorming:

25 March 2015, Kyle to Courtney: But I could see something like this happening: 1) CCDP publishes an edited collection on the theory and practice of sound from a rhetoric and composition perspective, writ large. I could write a chapter. So could you. We could all write chapters! But then: 2) Me and you work on something smaller, a collection of "case studies" as you said, or something else that really dives into the real, live practice of sound-teaching.

25 March 2015, Courtney to Kyle: I am on board for any/all of what you list. My motivations include: 1. I want to work on soundwriting pedagogy. 2. I want to write. 3. I want to find out what other people are doing with soundwriting. 4. I want to work on something with you. 5. My instinct was to do #3 before doing #1, but I suppose that isn't really mandatory.

As the ideas cemented and grew into a full blown project, Danforth realized that she and Stedman could not do it alone. “We put out an audio CFP in the summer of 2015 and quickly became so overwhelmed by the response we begged Michael to help us. Luckily, he agreed.” Reaching out to Faris provided him an opportunity he had not explored thus far in his career as his “previous (and continued) scholarship focused on pedagogical problems related to new media, and I had been working as an editor at Kairos when Courtney and Kyle asked me to join the editorial team.” Faris’ email of interest in joining the team reflects his view that this venture would be beneficial within his classroom and beyond.

13 Jan 2016, Michael to Courtney and Kyle: “What an exciting project! It’s great to hear that you got so much interest from contributors and have expanded the project. I’m excited by the opportunity to help — a bit worried about how much time it might involve. I think it would be great experience, and might help me conceptualize a few graduate and undergraduate courses and assignments I’ll be working on for next year (undergraduate writing courses and graduate new media courses), so I’m definitely interested!”

Making Tough Decisions

With a successful CFP, our editors were faced with some tough decisions. Stedman recounts their first thoughts, “Of course, we needed a publisher that was on board with our vision. We went with CCDP because they’re well-known as supporting exciting born-digital work, but they also wanted to keep an edited collection at 10 chapters or fewer, while we were initially imagining something much larger.” With so many proposals submitted, that led to a tough series of decisions on who to accept, so Danforth and Stedman developed a 5-point rubric that judged each proposal on the following traits:

After determining which chapters they would include in their collection, the question then became one of how to produce a text digitally when skill levels for producing webtexts varied. This variety in skill created one of the biggest challenges Faris found in

“designing it and getting it to work. We asked chapter authors to design their chapters as webtexts, some didn't have the ability to design html pages, and a few authors submitted chapters in formats that weren't sustainable or easily transferable to a publisher. I offered to design the html for those chapters, each of which went through multiple iterations as we discussed with authors what would be the best design for their chapters.”

This time inclusive process sometimes involved re-coding or coding from scratch because the interface of the various coding platforms did not transfer in ways that matched up.

Putting it All Together

Part of creating a digital book is figuring out how it all fits together, and this may prove difficult when you have a variety of designs being used. Faris discusses how “The book's landing page/TOC and introduction went through multiple design prototypes before we decided on the final version.” To facilitate better navigation and create consistency, Faris created a header and menu for the whole book.

Faris's designs went far beyond the book as a whole's landing page. For instance, here's an example of an early design for the Introduction chapter:

Both the landing page for the book and the design of the Introduction chapter needed to reflect the spirit of the project not only in format but in content. This required the authors to meet remotely to discuss their goals. We are fortunate to be privy to one of their first conversations that gives us a peek into their framing and goals for the entire collection.

On top of creating a framework for the whole project, the editors also collaborated heavily on the preface to the collection, the set ups to the various chapters, and the introduction chapter, which was no small feat. Below is a screenshot of their first draft of preface of introduction chapter along with notes and edits.

While this process looks neat and tidy from the screenshot above, Stedman shares that this lengthy introduction took many months to create:

“The version we sent to reviewers along with our prospectus was actually completely revised and rerecorded for the final book; the original had been recorded over multiple sessions, with lots of edits spliced in that were obviously recorded in other spaces. We also had to address pacing issues, clarifications of some of our points, adjustments to our style (this was informal, but how informal should it be?), and other nagging things that were bugging us. (I, Kyle, listened to that original version a few times in the car, and if something bugged me too much I made a note.) Eventually, with revised script in hand, we sat down and rerecorded the whole thing in one sitting, which greatly helped the audio quality, and the coherence of our ideas.”

Revising audio can prove difficult, and our editors have allowed us to not only see their processing up above but in recording iterations of a later part of the introduction to the collection. Below is a screenshot of a later portion of the introduction.

The goal of the introduction was “to be casual and personal, but this is an example of when it perhaps went too far, meandering into stories that weren’t really connected to the topic at hand. Notice that this was back when we were calling Michael a 'technical editor,' before we realized that that he was oh so much more than that.”

It wasn’t just the introduction text that took several iterations. Title pages for the chapters also needed to fit into the overall theme. This is an example of the iterations that one chapter title page went through as the final format moved toward something the authors felt meshed with the project as an overall concept.

Final Draft

Being able to edit easily in a document is something writers take for granted, but when html is involved, changes and revisions become complicated. Passing html files back and forth is not easy, so our editors “requested changes as lists in emails or using track changes in Google Docs, which led to dozens of emails with each author about their chapter and manually transferring changes from Google Docs to html files.” These exchanges resulted in a well over 1400 emails for this project alone in a 2.5 year period! Creating a workflow system and managing content becomes a must. Faris writes, “Numerous times, we had to ask ourselves, Is this the most recent version of the audio they sent? Or, where did we put that file? We worked through email, Google Drive, and Dropbox, which most of the time worked fairly well, but sometimes meant we forgot where something was stored or if we had communicated something with an author or not.”

Even in creating a navigable landing page/TOC, getting codes to mesh between the chapters required troubleshooting since the vastly different designs of the contributing authors varied. Faris explains, “For example, the css and javascript for the menu sometimes conflicted with css and javascript in individual chapters, and we had to do lots of tweaking to get it to work on some chapters.” This proved to be challenging but also enjoyable as Faris was tested with “imagining and testing what a sound-based and html-based book could look like,” and even though it took time, “it was also a lot of fun to test out ideas and troubleshoot problems.”

Not only did their own audio frame the book, the authors had to lean on their contributors to perhaps move out of their comfort zones. Faris shares, “Because audio-design and audio-editing are fairly new for most scholars in rhetoric and composition, another challenge was deciding when to ask for revisions to audio: Audio recording and editing can be time-intensive, especially for scholars trained to communicate scholarly work in alphabetic text.” Because of the time intensive work of audio, the editors respected their contributors and made suggestions to edit if possible on the contributors’ end or took care of minor problems like audio shifts themselves. Some contributors really embraced their chapters in surprising and nuanced ways. Danforth describes:

“The first time I heard a draft of Jeremy and Shannon’s chapter and they just call up Cindy Selfe? It blew me away. That’s the power of an audio citation. And then in Milena and David’s chapter, they let us listen in on a dinner party they have with Hildegard Westerkamp. Where else in the history of scholarly writing does something like that happen? This collection could not exist without the work of both these tremendous scholars, but we don’t just have their words on a page, we’ve got their living, teaching, voices enacting their ideas for our ears.”

The Finished Product and Beyond

After completing this book, our editors have only just begun to explore what soundwriting pedagogy looks and sounds like. Where to go from here? Each editor weighs in on the next steps for his or her work or study.

Faris’ work with Soundwriting Pedagogies had opened up his teaching: “Working on this project has really gotten me engaged in soundwriting: I've started teaching soundwriting in graduate courses, started a podcast (though I'm far behind in getting new episodes), and now that I administer TTU's First-Year Writing program, all of our undergraduates in ENGL 1301 are creating podcasts (an assignment I built off of Jeremy Cushman and Shannon Kelly's chapter). That's potentially 2700 podcast episodes this fall! I'm looking forward to continuing to write/create scholarship about and in audio.”

Stedman encourages other to take these ideas and run with them: “The next step beyond that is of course classroom practice: people using and remixing these ideas in their own classes, and then finding ways to share them. Most of the book is licensed with the very-open Creative Commons BY-NC license, which gives people the legal right to remix the words and audio files into their own contexts. So hopefully, the effect of the book will be a host of soundwriting assignments in the world throughout all sorts of distribution platforms.”

Danforth believes that they have only just begun in changing writing pedagogy, and “there is a sequel (of sorts) in progress! There has been so much interest already in pedagogical applications of soundwriting, we’re pretty far along now editing a second collection focused even more granularly on classroom activities and assignments that use sound to teach writing.”