I write technical documentation, heuristic reviews and terrible puns.
Technical writing portfolio

Examples of my product documentation work
Using video footage and interviews with data centre engineers, I created racking and installation guides for server hardware, working fully remotely.
I worked remotely with software and hardware engineers to create and maintain current and historical software documentation versions.
A reference architecture is a blueprint that provides guidance on how to design, build, and deploy a product or system. Read on for details on how I produce reference architectures.
I have created numerous solution briefs that prioritise communicating a concise, clear value proposition to how my client's products address specific business challenges.
Version control for documentation with Git
I have extensive experience managing documentation in Git-based CI/CD environments, particularly GitLab.
On past projects, I have:
-
Collaborated with engineers to review and refine merge requests, ensuring adherence to our technical documentation standards.
-
Used GitLab’s issue register to monitor gaps in documentation, either authoring the new content myself or coordinating with subject matter experts to draft material.
-
Used the Git command line for tasks better suited to terminal workflows.

Explainers and technical deep dives

A single source of truth is essential for maintaining consistent, clear and usabile documentation within an organisation. Click through to find examples of my technical documentation style guide work and the strategies I use to maintain high-quality, up-to-date documentation.
Instructional books and eBooks
Book: Twitter for Museums
​Back when Twitter (now X) was still a cultural behemoth, I contributed two essays to the book Twitter for Museums, a practical explainer on how to use the platform as an educational institution. ​​

SoftIron eBooks
* Longer than a pamphlet, shorter than a novel, these documents marketed as "eBooks" were generally about 5,000 words each.