Custom DITA and XML Authoring Tool
Oxygen licensing limited who could work directly in structured help. I developed a runnable stopgap for authoring and review, and team managers used it while broader authoring options were explored.
These projects start with a documentation problem and show the workflow or tool I developed in response. More work is covered throughout my story.
Oxygen licensing limited who could work directly in structured help. I developed a runnable stopgap for authoring and review, and team managers used it while broader authoring options were explored.
Starting a new release from a blank page meant researching feature tickets, mockups, and existing help separately. I built a reusable AI-help skill that brings Jira, Figma, and help source together to prepare a 2027.0 draft for writers to test, edit, and approve.
I mined approximately 2,500 peer-review comments from Git history to identify recurring editorial patterns, then refined a review skill through repeated use and comparison with my final decisions.
Manual transfer of structured help into Umbraco was difficult to scale. I developed AI-assisted conversion, reconciliation, and export workflows to preserve content, media, links, and help navigation as authoring moved beyond Oxygen.
A short epic description rarely shows the complete feature. I developed a Jira-to-Figma discovery workflow that follows related tickets to surface mockup links and frames, with image export designed to put those visuals beside the requirements.
Broken links, images, tables, and migration output were hard to fix without a clear inventory. I used AI-assisted checks and structured trackers to identify affected pages, preserve exact symptoms, and give reviewers a reproducible starting point.
When more contributors author help, unclear ownership and stale browser sessions put content at risk. I clarified the review path, separated formal approvals from comments, and raised safeguards against overwrite conflicts.
Jira research is useful only when another team can adapt it to its own site and permissions. I packaged a generic skill and helper for issue search, reading, and specifically requested creation with a read-back.
Review standards should be usable beyond one product or reviewer. I packaged a generic skill that checks factual support, reader flow, structure, accessibility, and language, with optional DITA and Oxygen guidance.
Two generic skills are packaged for Codex and Claude. Other projects are explained at the level supported by the audited record; a description of a workflow or experiment does not imply a public release or tested installation.
Read the project chapter