published, versioned, public
Every item here is live on docs.oracle.com. Open any of them and read the real thing: no reconstruction, no NDA-safe stand-in.
Interactive Signal Management
An entire documentation set for Empirica's signal-management module, mine end to end, from information architecture to final content, on a regulated pharmacovigilance domain.
read it on docs.oracle.comSix randomization algorithms in one comparison table, then the impact traced through notifications, four reports, and the dataset.
docs.oracle.comURL structure with path parameters, authorization and redirect logic, training-study versus training-mode. Developer-facing.
docs.oracle.comThirty-plus tabs, permission gating, an audit trail with date ranges, and the link to the Trial Master File, a regulated artifact.
docs.oracle.comTask documentation for the topic-workflow endpoints, JSON request and response schemas, and conditional UI behaviour.
docs.oracle.comA conditional business rule with four trigger events, split for two audiences, every edge case documented, then propagated across three reports.
docs.oracle.comPath parameters, mode and authorization logic, framed around the user benefit: fewer clicks, faster workflows.
docs.oracle.comwrite once, publish everywhere
Single-source structured authoring is the spine: one governed source, many outputs, terminology that stays consistent because it lives in one place. Pick an output and watch the same source render into it.
Auto-lock rules
When any of four trigger events fires, the form locks and no further edits are accepted. An authorized reviewer can unlock it, and every lock and unlock is written to the audit trail.
When any of four trigger events fires, the form locks and no further edits are accepted. An authorized reviewer can unlock it, and every lock and unlock is written to the audit trail.
<concept id="auto-lock">
<title>Auto-lock rules</title>
<conbody>
<p>When any of four trigger events fires, the form
locks and no further edits are accepted...</p>
</conbody>
</concept>
Same words, three outputs. The source is written once; the terminology can never drift between them.
the same discipline, three ways
Docs-as-code, versioned with the product.
Git-based authoring on OAK Foundation, versioned alongside the product. I led the migration from the legacy Oxygen toolchain.
Accessibility built in, not bolted on.
I led the European Accessibility Act rollout on Empirica in 2025: alt text, screen-reader readiness, WCAG 2.1 AA.
Two generations of tooling, in parallel.
A mature legacy product and a docs-as-code platform maintained at once, including the migration of classic API docs to REST. The same single-source discipline shows up again in scientific publishing: DITA at Oracle, JATS in journals.
what the structure bought
Structured authoring in DITA XML cut documentation bugs by 70%, across forty-plus published guides held at 95% reuse consistency.
Progressive disclosure and in-app guidance raised task success by 40% and cut support tickets by 30% on the products I documented.
Structured query models with SMEs, engineers, and QA compressed the doc cycle from a build a week to two builds across four to five weeks.
Core contributor to Oracle's Redwood design system, recognised with the 2024 Indigo Design Gold Award for UX, Interface & Navigation.
what I took from it, and what's next
When the source is governed and single, quality scales without more effort. The terminology stays right everywhere because it is only ever written once.
Bringing the same structured-authoring rigor to AI-assisted documentation, where the source of truth is the code and every claim has to trace back to it.