Tag
Automation
5 articles
-
One source, three languages: the strict facts-vs-display-strings split
events.yaml holds no labels. traduction.yaml holds no facts. The generator resolves them at build time with --lang fr, --lang en, or --lang es. What enforcing this constraint looks like in practice, and why the discipline is worth the friction it creates.
-
Reliability vs. latency: running Claude through the CLI so it can fix its own mistakes
Claude's LaTeX output frequently didn't compile. The fix wasn't to prompt better - it was to close the feedback loop. What looked like a reliability problem turned out to be a latency problem.
-
Non-blocking preflight, or: a build that always produces a PDF
One hard stop, five soft failures, a renamed file, and a report alongside it. The design philosophy behind a preflight that never aborts - plus the pikepdf/PyMuPDF six-check implementation and the --strict flag for CI.
-
Why hand-maintained InDesign files rot - and what docs-as-code does instead
A 370-cell calendar that shifts every year. A lead's name in three places. An IBAN in an invisible text box. These are not unusual InDesign problems - they are what InDesign files become when they accumulate facts with no single home. Two projects show what the alternative looks like - and where InDesign's own global tools stop short.
-
A decade of Word 97 conference files, rebuilt for the web for $30
How we transformed unstructured Word 97/2000 files into a decade-long web publication of conferences-using Markdown, Python, and GPT-powered automation for just $30.