Documentation Center Platform
19 years building documentation systems for high-stakes FinTech and enterprise platforms. This portfolio demonstrates work across the full documentation spectrum: REST API references, SDK guides, admin deployment docs, developer onboarding kits, and operator-facing portals.
Each project targets a distinct documentation type, audience, and delivery format. The table below maps what was produced. Every linked site includes full dark and light mode support.
Complete REST API reference for an enterprise AML and SAR-filing platform. Covers authentication, case management, entity screening, SAR submission, and webhooks. Written to Stripe-quality bar: every endpoint has request/response examples, error codes, and field-level descriptions.
View live site ↗Developer-first documentation for a FinTech payment API. Guides engineers from sandbox setup through production cut-over. Includes OAuth 2.0 flows, idempotency key strategy, webhook signature verification, and error recovery patterns.
View live site ↗System administration and deployment guide for an enterprise payment platform. Covers installation, compliance configuration, user access controls, payment rail setup, monitoring dashboards, and production troubleshooting. Structured for operators and IT admins.
View live site ↗Operator-facing reference hub for US payment rails: ACH, Fedwire, RTP/FedNow, and SWIFT. Covers processing flows, NACHA rule compliance, OFAC screening obligations, exception handling, and ISO 20022 migration context. Written for payment operations teams.
View live site ↗Post-sale onboarding package for enterprise customers adopting CaseForge AML. Covers kickoff checklists, environment provisioning, data migration, user training tracks, and go-live validation. Structured as a time-boxed 30-day program with clear owner assignments.
View live site ↗SDK guide for Python and Node.js wrappers around the CaseForge REST API. Covers quickstart, authentication (API keys and OAuth 2.0), error handling with exception hierarchies, a full code-sample library, release changelog, and v1.x → v2.0 migration guide with side-by-side breaking-change comparisons.
View live site ↗This hub, the capstone project, brings all phases together with navigation, explanatory meta-documentation on writing craft, information architecture decisions, and the docs-as-code workflow that underpins the entire portfolio. You are reading it now.
Current pageThe three documents below explain the practitioner decisions behind this portfolio: not what was produced, but how and why.
This portfolio demonstrates the following skills in deployed, publicly accessible documentation.
Every page in this portfolio follows the Microsoft Writing Style Guide: active voice, second person ("you"), sentence-case headings, present tense, no minimizers, task-oriented structure. These are not aesthetic preferences; they are precision tools that reduce reading friction and support translation and localization.
Each project starts with an audience definition and works backward to content structure. A developer integrating an SDK needs different navigation landmarks than an IT admin deploying a platform. The IA decisions are documented explicitly in the Information Architecture page.
Every project is delivered as static HTML with shared CSS and JS, with no static site generator dependency, no build step required to view or edit. This makes the documentation portable, offline-capable, and embeddable in any environment. The tradeoff is deliberate: simplicity and longevity over toolchain convenience.
The most valuable pages in any API or SDK reference are the error handling and troubleshooting sections. This portfolio documents failure modes with the same depth as success paths: exception hierarchies, retry semantics, idempotency key strategy, and per-status-code guidance rather than generic HTTP tables.
Each project in this portfolio was built to demonstrate a specific documentation skill. The Writing Philosophy page explains the practitioner decisions behind the work: what makes good developer documentation, and how to measure it.
Interactive tools built to diagnose, measure, and improve documentation systems, not just describe them.
A 4-step diagnostic wizard that identifies where a documentation pipeline breaks when content crosses from source format to delivery surface. Applies Despopoulos's source-to-delivery model and Iantosca's two-gate quality framework. Produces a prioritized fix list and shareable report.
Try it now ↗Live analytics dashboard powered by the GitHub public REST API. Displays repository stats, language breakdown, contribution activity, and a full repo table, all fetched and rendered on page load with no server required.
View dashboard ↗I'm open to senior-level technical writing and documentation engineering roles, particularly in FinTech, developer tooling, and regulated enterprise software. The best way to reach me is via LinkedIn or through the contact information on my GitHub profile.