16 Closing Thoughts
16.1 The Many Voices of Markup
When we began this part of The Textsmith Primer, we asked a deceptively simple question:
How can plain text describe more than just words?
The answer has taken us on an extraordinary journey.
We discovered that markup languages are far more than collections of symbols or syntactic rules. They represent different communities solving different communication problems through the same remarkably simple medium: plain text.
HTML connected documents and gave rise to the World Wide Web.
XML allowed every discipline to describe its own knowledge.
TeX demonstrated that plain text could rival the finest traditions of typography.
reStructuredText helped software developers treat documentation as an integral part of programming.
AsciiDoc made professional technical publishing more approachable.
Markdown brought structured writing to millions of people by making markup almost invisible.
Its descendants continue to shape research, publishing, note-taking, collaborative writing, and even communication with artificial intelligence.
Typst reminds us that the story of digital publishing is still unfolding.
Mermaid and Graphviz reveal that even diagrams can be described through carefully structured text.
Taken individually, these technologies appear quite different.
Taken together, they reveal a common philosophy.
Each asks the computer to understand the structure of information rather than merely its appearance.
Each separates content from presentation.
Each trusts software to handle repetitive formatting while allowing people to concentrate on ideas.
The syntax changes.
The philosophy remains remarkably consistent.
16.2 Different Communities, One Philosophy
Throughout this part, we encountered many different communities.
Each adopted plain text for its own reasons.
| 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 |
No language replaces the others.
Instead, each occupies its own place within the broader ecosystem of digital writing.
This diversity should be celebrated rather than feared.
Different problems deserve different tools.
The strength of the plain text world lies precisely in its openness to many approaches.
16.3 The Enduring Lesson
One of the most surprising discoveries of this part is that markup languages are not really about formatting.
They are about meaning.
A heading is identified as a heading.
A quotation as a quotation.
A chapter as a chapter.
A diagram as a diagram.
Once that meaning has been captured, software can transform the same source into books, websites, presentations, technical manuals, ebooks, accessible documents, and countless other forms.
This idea lies at the heart of modern publishing.
Write once.
Publish everywhere.
16.4 Looking Ahead
Markup gives plain text structure.
The next question naturally follows.
Once information has been written as structured text, what can we do with it?
Can we search thousands of files instantly?
Can we transform documents automatically?
Can we extract patterns hidden within large collections of text?
Can we build powerful workflows from small, focused tools?
These questions lead us naturally into the next part of this primer.
There we leave markup behind—not because it is complete, but because we have given plain text structure.
Now we learn how to make that structured text work for us through the rich tradition of text processing.
The story of digital writing continues.