Portfolio

When Documentation Becomes a Systems Problem

For more than 25 years, I’ve written complex technical documentation and built the publishing systems around it. These case studies include current consulting work and earlier enterprise systems. The starting problems vary: outdated or conflicting source material, content drift, inaccessible output, fragile builds, and technical evidence that had not yet become a usable plan. Each case explains what I found, what I changed, and how the work held up in use.

Case studies based on client or employer engagements omit proprietary product details. Fictional, original writing samples are clearly labeled.

Case studies

The Problem Behind the Deliverable

Each case follows the problem, the constraints that made it difficult, the decisions I made, and the evidence left behind.

Everfox · Publishing Engineering

Building a Publishing Platform From a Bare-Bones Deployment

I inherited a bare-bones, partially working PDF deployment and made it reliable, then added online help, HTML, text, spreadsheets, man pages, eBooks, and ISO release media. As its product manager, I owned the roadmap, specifications, design and implementation, testing, user acceptance, releases, and writer training.

Read the case study →

Information Architecture · Cybersecurity

Separating Documentation When One Product Became Two

A management system that had existed only to administer a secure data-transfer software package became a separate product that could support other systems. I still owned both documentation sets, but legal boundaries meant information specific to the data-transfer package could not appear in the management-system documentation.

Read the case study →

Cisco · Metadata-Driven Help

Making Help Match the Device in the User’s Hand

Generic help could point users toward features their phone did not support or their administrator had chosen not to allow. The help system automatically assembled the right content on the fly, required no separate help configuration, and changed when the phone’s enabled features changed.

Read the case study →

Cybersecurity Assessment · Reporting

Turning Security Evidence Into Prioritized Action

As one of three assessors, I helped conduct an engagement that combined penetration testing performed remotely with onsite interviews, infrastructure review, network and wireless testing, photographs, and exported data. I then helped turn the results into prioritized findings and remediation paths.

Read the case study →

Direct demonstrations

Direct Demonstrations

These fictional, original projects let you inspect the finished documentation and the system behind it. You can follow the procedures, examine the information architecture and source, review the validation evidence, and compare the maintained content with the published outputs.

Docs-as-Code · CI/CD · Single-Source Publishing

Greenhouse Sentinel

A working, single-source documentation system with traceable training-content reuse, automated accessibility and responsive testing, public test evidence, synchronized website, Word, and PDF outputs, and a PowerPoint training deck generated from reusable source. The writing, information architecture, source, tests, and generated formats are all available for inspection.

Explore the project →

Administrator Documentation · Original Demonstration

Linux Service Troubleshooting Runbook

This fictional, original runbook investigates a systemd service that is still running but no longer delivering events. Each check preserves evidence and narrows the next decision.

Read the sample →

Need help with a complex project?

Let’s Talk About What You Need

If you are dealing with outdated documentation, a fragile publishing process, a difficult migration, or work that needs clearer ownership and validation, tell me what is happening. We can decide whether Structured Ink is the right fit.

Start a ConversationView Services