Writing Samples

I write documentation for people who are trying to get something done: developers integrating an API, builders making product decisions, and teams trying to ship clearly in complex software environments.

Web APIs and Appian

Sample: Connecting Appian to custom websites with Web APIs

Documentation job: Explain how builders can connect Appian experiences to external web surfaces using Web APIs.

What this sample shows: Technical sequencing, conceptual framing, and the ability to make integration work feel approachable.

Design system guidance

Sample: Designing with card components

Documentation job: Help builders make better interface decisions with a reusable component.

What this sample shows: UX writing, design guidance, and translating component behavior into practical product judgment.

Function reference

Sample: Localize currency display

Documentation job: Make a narrow technical function easy to scan, understand, and apply.

What this sample shows: Concision, structure, and reference-writing discipline.

How I think about docs

Good documentation is not just an archive of product facts. It is part of the product surface.

The best docs reduce anxiety, remove hidden assumptions, and help users build confidence one step at a time.