Developer documentation , API documentation , Docs-as-code
I work with engineering teams on developer and API documentation, from information architecture and authoring to automated builds, checks, and publishing.
Paris · Available for a new opportunity from October 2026
Technical documentation
Developer guides and API reference reviewed with engineers, from reference templates to OpenAPI generated from a single source, organized by concept, task, and reference.
Evidence: Developer & API documentation (opens in a new tab) · Documentation process & quality (opens in a new tab) · Multilingual documentation (opens in a new tab)
Documentation in Git next to the product, topic-based DITA XML with content reuse and conditional text, and an architecture that keeps large documentation sets consistent.
Evidence: Docs-as-code (opens in a new tab) · DITA & structured authoring (opens in a new tab) · Documentation architecture (opens in a new tab)
Reproducible builds with pinned toolchains, automated checks, publishing pipelines, and content generated from data. I use AI for selected documentation tasks, with human review before publication.
Evidence: Automation & CI/CD (opens in a new tab) · AI-assisted documentation (opens in a new tab)
Problems I have worked on
View evidence: Single-source API documentation Live API docs: Single-source API documentation
View the case study: NuFirewall product documentation (opens in a new tab) When DITA pays off: NuFirewall product documentation
View evidence: CI/CD for print deliverables Example CI/CD pipeline: CI/CD for print deliverables (opens in a new tab)
See how it is built: The documentation portfolio (opens in a new tab) Translating it with AI: The documentation portfolio
docs.redaction-technique.org
My technical-writing methods, case studies, and working examples. Bilingual (English and French), maintained in Git since 2014.
Articles
Notes on decisions I have made while building and maintaining documentation systems.
Running make locally is one thing. Guaranteeing that every contributor’s push or YAML edit on GitHub produces the same press-ready artifact on a clean machine with a pinned toolchain is another. How two print projects implement that guarantee with GitHub Actions.
Most of a small organization’s website barely changes. This is an argument for building the smallest editing interface it actually needs, using Astro, Git, YAML, and a small admin layer instead of a full CMS.
A GUI hides complex code behind menus and drag handles you operate by hand. AI hides the same complexity behind a conversation. Recreating a hand-built InDesign leaflet as a YAML-to-LaTeX pipeline: abandoned in 2025 as beyond the time I could afford: is what made the difference concrete.
Index
AI documentation assistant
Ask a question in plain language. The assistant answers from the articles published on this site, grounded in their text, and lists the ones it used. To look up an exact term, use search.
Try rephrasing with a more specific term, browse by topic, or search the articles.
Need methods, templates, and case studies? See the documentation portfolio (opens in a new tab).
Contact
My current Senior Technical Writer contract at Unity ends on October 1, 2026. I am open to new opportunities in technical writing, developer documentation, documentation architecture, and docs-as-code.
To discuss a technical writing role or project, reach me on LinkedIn or use the contact form.
