II. Markup Languages
The first part of The Textsmith Primer introduced the remarkable world of plain text.
We discovered that plain text is portable, durable, accessible, and independent of any particular software. We learned how computers represent characters through Unicode and text encodings, and how the Unix philosophy transformed plain text into the universal medium through which software communicates.
Yet one important question remained unanswered.
Plain text stores characters—but how does it describe a heading, a quotation, a chapter, a mathematical equation, a hyperlink, or even a diagram?
The answer is markup.
Markup languages enrich plain text by giving it structure.
Rather than describing how a document should appear, they describe what the various parts of a document represent. A heading becomes a heading. A paragraph becomes a paragraph. A citation becomes a citation. A diagram becomes a collection of relationships.
Once that structure has been captured, software can transform the same plain text into many different forms: websites, books, PDFs, presentations, ebooks, technical manuals, documentation, and much more.
This simple idea has quietly transformed digital publishing.
The chapters in this part tell the story of how different communities embraced markup to solve different communication problems.
The Web needed documents that could be linked together.
Publishers needed documents that could be described precisely.
Scholars demanded beautiful typography.
Software developers required documentation that could evolve alongside their code.
Technical writers sought maintainable documentation for large projects.
Millions of everyday writers wanted a syntax that disappeared behind their ideas.
Today, even artificial intelligence systems rely heavily upon structured plain text to communicate effectively.
Although these communities developed different markup languages, they all arrived at a remarkably similar philosophy:
Describe structure. Let software handle presentation.
That principle has become one of the defining ideas of modern digital writing.
In This Part
6 Introducing Markup Languages Explores what markup is, how it differs from programming languages, and why describing structure rather than appearance transformed digital publishing.
7 The Hypertext Markup Language (HTML) and the Rise of the World Wide Web Examines how hyperlinks changed the way humanity discovers and shares knowledge, laying the foundation for the modern Web.
8 The Extensible Markup Language (XML) Introduces XML as a framework for designing markup languages, enabling every discipline to describe its own information while preserving structure and interoperability.
9 TeX, LaTeX, and the Art of Digital Typesetting Shows how plain text became capable of producing documents of extraordinary typographic quality and why TeX continues to influence professional publishing.
10 reStructuredText and Python Documentation Explores how software developers transformed documentation into a structured, maintainable publishing workflow.
11 AsciiDoc and the Evolution of Technical Writing Examines how professional technical documentation became easier to write without sacrificing the expressive power required for large publishing projects.
12 Markdown: The Everyday Markup Language Tells the story of the lightweight markup language that made structured writing accessible to millions of authors around the world.
13 Beyond Markdown: CommonMark, GitHub Flavored Markdown, and AI Markdown Follows Markdown’s remarkable evolution from a simple HTML authoring tool to one of the defining languages of modern publishing, collaboration, and artificial intelligence.
14 Typst and the Modernization of Digital Typesetting Introduces a modern document language that combines the typographic ambitions of TeX with the simplicity of lightweight markup and the expressive power of scripting.
15 Mermaid and Graphviz: Creating Diagrams with Text Demonstrates that markup is not limited to prose, showing how even diagrams and visual relationships can be described through plain text.
A Journey Through Communities
One of the themes running through this part is that markup languages did not evolve in isolation.
Each emerged from a community seeking a better way to communicate.
| Community | Primary Question | Representative Language |
|---|---|---|
| The Web | How do we connect knowledge? | HTML |
| Information Architects | How do we describe knowledge? | XML |
| Scholars | How do we present knowledge beautifully? | TeX and LaTeX |
| Software Developers | How do we document knowledge? | reStructuredText |
| Technical Writers | How do we maintain knowledge at scale? | AsciiDoc |
| Everyone | How do we write knowledge simply? | Markdown |
| Modern Publishers | How do we modernize professional publishing? | Typst |
| Visual Thinkers | How do we visualize knowledge? | Mermaid and Graphviz |
Different communities.
Different challenges.
Different languages.
Yet behind them all lies the same enduring belief: that carefully structured plain text can express ideas with remarkable clarity, flexibility, and longevity.
Welcome to the world of markup languages.