Technical writing portfolio
I am a technical writer. For eight years I wrote the controlled documentation for validated laboratory systems at a GSK vaccine manufacturing site: more than 100 documents and thousands of pages that had to survive QA review, internal audit, and FDA inspection readiness. This site is where I do the same work in the open, on the toolchain modern documentation teams actually use.
Every page here moves through a pull request. CI lints structure with markdownlint, lints prose with Vale against the Google developer documentation style guide, checks every external link, and runs a full build that fails on any broken internal reference. Merges to main deploy automatically to GitHub Pages. The pipeline is documented in How this site is built.
Start with the sample that matches your opening
| If you are hiring for | Read this first |
|---|---|
| API documentation | FileMaker Data API reference, with a hand-authored OpenAPI 3.1 specification |
| Developer onboarding and tutorials | Qdrant in Docker: a first vector search |
| Conceptual and architecture writing | Anatomy of an audit trail |
| Process, compliance, or platform docs | Change control was docs-as-code before Git |
| Content operations | How this site is built |
The short version
Regulated manufacturing taught me the expensive parts of this craft: extracting exact detail from busy experts, writing procedures people can follow under pressure, and running every change through review and approval with a reason attached. The tools here are newer than the ones I learned on. The discipline is identical.
More background, including the ten years of healthcare systems work before GSK, is on the About page.