Technical Writer · Prague
Technical Writer · Docs-as-Code Practitioner · Available for hire
Documentation built with the same discipline it teaches.
A six-part documentation series built and deployed as a live static site. Written in Markdown, version-controlled in Git, and deployed automatically via GitHub Actions — the same workflow the series teaches.
Read the Series →
Hands-on API documentation built using the OpenWeather REST API and Postman — covering authentication, endpoint structure, request parameters, and response interpretation. Structured in Markdown following Docs-as-Code standards.
Read the Docs →
A technical writer's evolution — from producing content to designing documentation systems. Long-form series on Docs-as-Code, information architecture, and the thinking behind great developer documentation.
Visit the Blog →
A practical guide to building a personal website with a custom domain and professional email — covering GitHub Pages, Cloudflare DNS, HTTPS configuration, and Gmail SMTP. Includes troubleshooting for every common failure point.
Read the Guide →
A documentation-led review of a static frontend website — covering architecture decisions, security considerations, known limitations, and deployment strategy. The documentation is the product.
View the Repo →
Technical documentation for this portfolio site — covering architecture decisions, local setup, deployment pipeline, content workflow, and contributing guidelines. The site documents itself.
Read the Docs →I'm Douglas Ebhoman — a technical writer based in Prague, specialising in Docs-as-Code workflows, API documentation, and developer-facing content. I bridge the gap between engineering teams and the people who use what they build.
My background in creative writing gives me an instinct for clarity and narrative structure that most technical writers don't bring to documentation. I don't just describe systems — I make them legible.
I'm currently available for full-time roles and freelance engagements with engineering teams, developer tool companies, and SaaS products.
Peer Review
Douglas has nailed it with his 'Git & GitHub for Technical Writers' series. It's a must-read if you want to adopt Git and GitHub for product documentation. He has a knack for writing in a simple, clear style — it's a pleasure to read. I'm looking forward to more great insights.
Git, GitHub, Markdown, MkDocs, GitHub Actions, static site deployment, version-controlled documentation workflows.
Diátaxis framework, Single Source of Truth architecture, information hierarchy, internal linking, content strategy.
API documentation, technical blog writing, pull request discipline, engineering team collaboration.
Available for full-time roles and freelance engagements.
Based in Prague, open to remote.