Preface
Every book has a beginning.
This one began not with a manuscript, but with a question.
Why does plain text continue to matter?
Like many people, my early experiences with computers were shaped by software that often hid its inner workings. Configuration lived behind graphical interfaces. Important settings were buried in places that were difficult to understand. The computer did many remarkable things, yet it often felt like a machine that preferred mystery over explanation.
Over time, I began discovering another way of working.
It started with something surprisingly simple: configuration files.
Instead of clicking through layers of menus, I found myself opening ordinary text files. Their contents were readable. Their structure was understandable. Every line described something the computer was doing. For the first time, I felt that I was not merely using my computer—I was beginning to understand it.
That discovery eventually led me much further.
I encountered the Unix philosophy, where everything seemed to revolve around small tools, simple files, and thoughtful composition.
I discovered Markdown and realized that writing did not require complicated word processors to produce beautiful documents.
I learned version control and understood that every revision had value.
Publishing systems such as Pandoc and Quarto showed me that a single source document could become books, websites, presentations, and articles.
Gradually, I realized that these technologies were not isolated inventions.
They expressed a common philosophy.
They valued openness over opacity.
Structure over appearance.
Longevity over convenience.
Communication over complexity.
This book grew out of a desire to explore that philosophy.
It is not intended to convince every reader to abandon their favourite software.
Nor is it an attempt to argue that plain text is the answer to every problem.
Rather, it is an invitation to discover why so many writers, developers, researchers, educators, publishers, and lifelong learners continue returning to these remarkably simple ideas.
Along the way, you will meet familiar tools and perhaps discover new ones.
More importantly, I hope you will discover patterns that connect them.
Why markup languages matter.
Why text processing remains relevant.
Why publishing is more than formatting.
Why version control preserves more than files.
Why teaching is an act of generosity.
Why ethics is an act of respect.
And why, despite the continual evolution of technology, thoughtful craftsmanship continues to matter.
This primer was written for beginners who are taking their first steps into the world of plain text.
It was also written for experienced practitioners who wish to step back from individual tools and consider the larger philosophy that connects them.
Whether you are a student, developer, researcher, technical writer, educator, publisher, or simply someone who enjoys understanding how digital tools work, I hope you find something useful within these pages.
The title of this book is The Textsmith Primer.
A textsmith is not merely someone who writes with plain text.
A textsmith is someone who believes that ideas deserve clarity, structure, preservation, and thoughtful communication.
If, by the final page, you find yourself looking differently at the documents you write, the tools you choose, the knowledge you preserve, or the people with whom you share your work, then this book will have achieved everything I hoped it might.
Welcome to the journey.
Welcome to the workshop.
Welcome, fellow textsmith.