I turn technical complexity into user enablement.

I am a technical writer and documentation strategist who builds bridges between complex code and the people who need to use it. My goal is to empower users with clear, actionable information while establishing the internal operations that allow documentation to scale.

I treat documentation like software. My workflow is built on Hugo, Git, and VS Code, ensuring content is version-controlled, testable, and maintainable. I also have extensive experience with CMSs, LMSs and enterprise knowledge management systems. I embed myself in the development lifecycle, partnering early with Engineering, Product, and CX to ship documentation alongside code.

The selection below demonstrates my range: from technical configuration guides and user enablement to the operational frameworks that drive the documentation function.

Configuration Guide: Configure Port Forwarding Rules
A vendor-agnostic architectural guide for IT administrators connecting cloud apps to on-premise hardware. This piece employs “Secure by Design” principles, clearly separating forwarding rules from firewall configurations to mitigate deployment risks. It features architectural diagrams and standardized terminology to ensure successful deployment in hybrid network environments. This was originally authored using a hybrid docs-as-code workflow. The company I was working for relied on CraftCMS for its documentation site, but I employed Git (for versioning); Markdown, Vale and Lychee to ensure that my draft complied with our style guide; and a custom script with Pandoc to move docs to Google Workspace for non-technical SME review. After approval I manually added the content to CraftCMS.
2025/08/25 · Portfolio
Conceptual Guide: What are OAuth Integrations?
Targeted at business stakeholders and admins, this guide demystifies the OAuth handshake to overcome security anxiety. By utilizing clear analogies (The Valet Key) and a multimedia approach, this content removes friction from the “Grant Access” decision, directly supporting product adoption and integration stickiness. This was written based on a developer portal page that explained the authorization flow, and includes a space reserved for a video discussion of the topic produced by their product team. The workflow involved a WYSIWYG to CMS toolchain. The original company has been redacted to preserve their brand.
2025/08/25 · Portfolio
Integration Guide: Mappings for Non-Technical Admins
This guide bridges the gap between raw API schemas and non-technical warehouse administrators. By creating a learning path and a dedicated JSON primer, I enabled users to configure complex ERP-warehouse management solutions integrations independently. This reduced engineering support tickets regarding integration failures by empowering the end-user to understand data structures. This was originally authored using a hybrid docs-as-code workflow. The company I was employed at relied on CraftCMS for its documentation site, but I employed Git, Markdown, Vale and Lychee to ensure that my draft complied with our style guide, and a custom script with Pandoc to move docs to Google Workspace for non-technical SME review.
2025/08/25 · Portfolio
Documentation Operations Handbook
This document is a blueprint of my technical writing process. As the first or “lone writer” it’s important to have a clear process so that managers and colleagues can understand how to work with me. This was written for working with small teams including developers, product managers, and CX staff. As part of workflows using Linear, JIRA, or a similar tool. It’s meant to showcase a transparent and efficient workflow for managing documentation tasks, from initial bug reports to comprehensive content plans for documenting new features.
2025/08/25 · Portfolio