Portfolio
The work spans technical documentation, information architecture, publishing systems, technical investigation, release processes, and complex products. It always starts by finding the problem people actually need solved.
Real work is sanitized where the original involved proprietary enterprise or cybersecurity products. Fictional, original writing samples are clearly labeled.
Case studies
Each case starts with a problem, the constraints around it, and the reasoning that shaped the intervention. The systems, tools, and documents are evidence of the solution.
Everfox · Publishing Engineering
Several active product releases depended on publishing infrastructure that had to enforce quality and compliance without becoming a release bottleneck. A redesign cut publishing time by approximately 40%, and documentation caused zero delays across multiple launches.
Read the case study →Current Consulting · Cyber-Defense Documentation
A complex cyber-defense platform had almost no current documentation, mixed old and current architecture, and only weeks before delivery. Beta administrator and end-user guides were delivered and reviewed.
Read the case study →Information Architecture · Cybersecurity
One product became a family with different owners and release schedules. Release-aware information architecture kept shared guidance coherent without copying it into versions that would drift.
Read the case study →Cisco · Structured Content
A three-person team had to determine whether a custom modular XML model could work in practice for an authoring organization of approximately 500 writers—not merely look sound in a diagram.
Read the case study →Cisco · Structured Content · Localization
Roughly a dozen related phone models shared substantial content but were not identical. Structured reuse limited maintenance and localization cost without erasing real product differences.
Read the case study →Cisco · Metadata-Driven Help
Generic help could describe features a user’s phone did not support. Feature metadata assembled topics, links, lists, and navigation appropriate to the actual device.
Read the case study →Cybersecurity Assessment · Reporting
Interviews, observations, photos, testing, exports, and penetration-test evidence had to become defensible findings and a plan the client could use for remediation, training, planning, and budget discussions.
Read the case study →Direct demonstrations
These fictional, original projects make the work inspectable: the writing, information architecture, source, validation, and published outputs.
Original Demonstration Case Study
A working single-source documentation system that publishes maintained Markdown as a website, handbook, and PowerPoint training deck with traceable slide notes.
Explore the project →Developer Documentation · Original Demonstration
This fictional, original API quickstart gives developers a task-first path through a validated request and actionable error guidance.
Read the sample →Administrator Documentation · Original Demonstration
This fictional, original runbook uses a layered diagnostic sequence to investigate a systemd service that is running but no longer delivering events.
Read the sample →Range
Structured content, metadata, reuse, version architecture, docs as code, and CI/CD publishing.
API and SDK documentation, administrator guidance, troubleshooting, online help, and validated examples.
Automated QA, accessibility, compliance, localization, regression testing, and release governance.
Linux, networking, secure systems, product behavior, requirements, UAT, and evidence traceability.
Have a difficult documentation problem?
I start by understanding what is true, what people need to do, and where the current system makes that harder than it should be.
