What Are the Digital Humanities? More Than Just Google Docs

Imagine you're holding not just a book, but a dataset—the complete works of Shakespeare, digitized and ready for query. Your mission: uncover how the Bard’s characters’ emotions shift across tragedies, comedies, and histories. You’re not just reading; you’re mining text with code, plotting joy and despair across acts, comparing the melancholy of Hamlet to the euphoria of Much Ado About Nothing. This isn’t a fantasy from a far-off research lab; it’s a real project undertaken by Maya, a high school student in Toronto, who used Python’s natural language processing libraries to ask questions no one had ever phrased quite that way before. Her tool? Not a magic oracle, but a blend of humanistic curiosity and computational method—a partnership that sits at the very heart of what we call the Digital Humanities (DH). Yet, when you hear “Digital Humanities,” do you picture someone typing an essay in Google Docs? If so, you’re not alone—and that’s exactly the misunderstanding this chapter will dismantle. The Digital Humanities is not about using digital tools to do traditional humanities work faster; it’s about reimagining what humanities questions can even be asked when we bring computation into the conversation. It’s a field where coding meets curiosity, where data visualization becomes a form of interpretation, and where collaboration isn’t optional—it’s the engine of discovery. Over the next fifteen chapters, you’ll embark on a hands-on journey to remix the humanities with code, but first, we must lay the foundation: What *are* the Digital Humanities, really? And why should you, as a teen, care? Let’s begin by moving beyond the Google Docs stereotype and into a world where humanities questions drive the tech, not the other way around.

Defining the Digital Humanities: More Than Just “Computers + Literature”

The Digital Humanities is often summarized in ways that undersell its revolutionary potential: “It’s using computers to study literature,” or “It’s making cool maps from history data.” While not wrong, these definitions miss the field’s core philosophical shift. At its essence, DH is an interdisciplinary endeavor that employs digital tools and methods to pursue humanistic inquiry, while simultaneously interrogating the digital technologies themselves through a humanistic lens. It’s a two-way street: we use code to ask new questions about culture, history, language, and art, and we use humanistic critical thinking to question the code, the data, and the platforms we build. This duality is what makes DH distinct from mere “tech in the classroom.”

Consider the origin story. The field didn’t emerge because someone decided to “digitize books”; it grew from scholars in literature, history, and archaeology asking: *What if we could analyze all of Jane Austen’s novels for word patterns at once? What if we could reconstruct a Roman villa from scattered excavation notes using 3D modeling?* These were humanities questions first—questions about narrative style, about spatial experience—that demanded new methods. As John Unsworth, a founding figure in DH, put it: “The Digital Humanities is not about the digital, and it’s not about the humanities. It’s about the *and*.” The “and” is the generative friction between the two.

For you, a teen growing up in a world of algorithms and memes, this matters because DH gives you a framework to be more than a passive consumer of digital culture—it empowers you to become a critical producer and analyst. It teaches you that the apps you use, the games you play, the social media feeds you scroll are rich texts worthy of study, and that you have the tools to study them. But first, let’s shatter three common myths.

Myth 1: DH is just making websites or digital archives. While many DH projects result in beautiful websites (like the *Perseus Digital Library* or *Slave Voyages*), the website is often the *output*, not the essence. The essence is the research question: *How did transatlantic slave trade networks evolve over centuries?* The website is a way to share those findings interactively. DH can also be a single-line of code that detects plagiarism in Renaissance sonnets, or a machine learning model that identifies anonymous 18th-century pamphlets. The medium varies; the humanistic drive remains constant.

Myth 2: You need to be a coding genius or a PhD to do DH. Absolutely not. DH thrives on beginner curiosity. Many groundbreaking projects start with someone learning a bit of Python to scrape a website they’re fascinated by. The field values iterative learning: you start with a small question, pick up a tool, and grow from there. This book is built on that premise—you don’t need prior expertise, just a willingness to experiment.

Myth 3: DH replaces traditional humanities with cold, hard data. This is perhaps the most dangerous misconception. DH does not reduce a Shakespeare play to a spreadsheet of word frequencies; it *augments* close reading with distant reading. Close reading—the meticulous, line-by-line analysis central to literary study—reveals nuance, irony, and aesthetic detail. Distant reading—using computation to see patterns across thousands of texts—reveals trends, influences, and historical shifts that no single reader could perceive. Together, they create a fuller picture. As Franco Moretti, a pioneer of distant reading, argues, “We need to stop reading and start counting—not instead of, but alongside” traditional methods.

With these myths dispelled, we can arrive at a working definition: The Digital Humanities is a collaborative, interdisciplinary field that uses digital tools and methods to explore humanistic questions, while applying humanistic critical perspectives to understand the impact and biases of those same tools. It’s a cycle of questioning, building, and reflecting.

Now, let’s see this in action through three stories—one from a high school student, one from a college class, and one from a community partnership—each embodying a different facet of DH.

---

Case Study 1: Mining Mood in Shakespeare with Sentiment Analysis

Maya’s project began not with code, but with a frustration: her English class was studying *Macbeth*, and she kept noticing how the play’s atmosphere shifted from act to act—from the eerie opening with the witches to the bloody climax. “Is it just me,” she wondered, “or does the emotional tone actually change in a measurable way?” That question—*Can we quantify the emotional arc of Shakespeare’s plays?*—is a classic DH prompt. It’s specific, researchable with digital tools, and deeply humanistic: it seeks to understand how art manipulates feeling.

The Technical Workflow: From Play to Plot

Maya’s journey from question to visualization followed a typical DH pipeline, which we’ll revisit in later chapters with more depth. Here’s how she did it:

1. Data Acquisition: She needed clean, machine-readable texts of Shakespeare’s plays. She downloaded the *Folger Shakespeare Library*’s open-source XML files from GitHub. These files structured each play with acts, scenes, and lines, making them perfect for analysis.

2. Data Cleaning & Preprocessing: Raw text is messy. Maya used Python and the `BeautifulSoup` library to strip out stage directions, character names, and XML tags, leaving only spoken dialogue. She then tokenized the text (split into words) and removed stopwords (“the,” “and,” “I”) using the `NLTK` library. This left her with a list of meaningful words per line.

3. Sentiment Analysis: This is where natural language processing (NLP) comes in. Sentiment analysis assigns a positive, negative, or neutral score to text. Maya used a lexicon-based approach: she employed the `VADER` (Valence Aware Dictionary and sEntiment Reasoner) model, which is pre-trained on social media text but works well for dramatic language. VADER assigns each word a “sentiment intensity” (e.g., “joy” = +0.8, “murder” = -0.9). For each line of dialogue, she averaged