A book that renews itself

A book as a build artifact

“Christlich denken — Eine Bibliothek von Denkwegen” is a book that exists twice: as a growing library on christlichdenken.at and as downloadable PDF and EPUB editions — free, without registration or tracking. I am a co-author. The technically unusual part is that the book is not maintained separately. It is generated anew with every release, from the same sources as the website.

That sounds like an implementation detail. It is the opposite: it is the project’s most honest decision. A book manually maintained alongside a website starts becoming outdated the day it is created. Two versions of the same content drift apart until nobody knows which one applies. Generating both from one source avoids that problem. One truth, one place — the same principle I apply to software, applied to texts.

A text structure that supports scrutiny

christlichdenken.at connects texts on faith, the Bible and Christian life. The editorial structure is intended to make arguments traceable: textual reference, interpretation and conclusion must remain distinguishable. A fixed structure can support this work. It does not establish that every interpretation or factual claim is correct.

I realise that sounds strict for a faith project. But the rigour is the point. In texts about faith especially, it is tempting to mix claims with evidence. A fixed structure requires separation: here is the text, here is the interpretation, here is what remains open. Readers should be able to examine rather than be required to believe — “Read. Examine. Think. Pray. Decide freely.” is the approach stated on the site.

Deliberately simple

The platform serves static pages. This keeps the technical route to reading straightforward. The free book adds a way to read a downloaded version independently of the website. That choice supports the goal of making the texts as accessible as possible.

The distribution model also follows the content. The book is free in both formats and remains so. Reading it does not oblige anyone to provide an email address.

What software learns from books — and vice versa

This project taught me more about software architecture than one might expect. A book generated from one source follows the same pattern as a PDF generated from profile data or a vCard produced from a configuration file: repeatable outputs can share a source. That reduces conflicting versions; the content still needs editorial care.

Conversely, software learns from the book: its seven-part text structure is a schema — an enforced form that makes content open to scrutiny. The structure can reveal gaps. Checking the content itself remains a separate task.