CHALLENGE
Technical editors managed 326 help articles across multiple Joomla instances while juggling Jira, Phrase, Figma, email, and internal documentation. Preparing each release meant hours of manual research, context switching, and coordination.
Some details of this project are protected due to client confidentiality. Enter the password to view the full project.
Some details of this project are protected due to client confidentiality. Enter the password to view the full project.
I designed and built an AI-powered content operations platform that unifies Jira, Joomla, documentation, UX writing, translation, and release management into a single workspace. The platform manages 326 help articles across multiple Joomla instances, supports 25,000+ translation strings in 37 locales, and dramatically reduces the manual effort required to prepare each release.
Year
2026
Scope
Product Design, UX Writing, AI Workflow Design, Content Strategy, Documentation Operations, Front-end Development



Technical editors managed 326 help articles across multiple Joomla instances while juggling Jira, Phrase, Figma, email, and internal documentation. Preparing each release meant hours of manual research, context switching, and coordination.
Rather than replacing existing tools, I designed a workflow layer that connects them. AI identifies documentation gaps, prioritizes work, drafts updates, and automates repetitive editorial tasks while keeping editors in control.
From product changes to published content — one connected workflow.
Collect product changes, linked work, and release context.
Analyze tickets and identify related help articles.
Draft, review, and update user-facing help content.
Review multilingual content and sync translation workflows.
Generate release notes from Jira and editorial decisions.
Push final content to Joomla, Confluence, or GitLab.
Technical editors managed 326 help articles across multiple Joomla instances while juggling Jira, Phrase, Figma, email, and internal documentation. Preparing each release meant hours of manual research, context switching, and coordination.
Rather than replacing existing tools, I designed a workflow layer that connects them. AI identifies documentation gaps, prioritizes work, drafts updates, and automates repetitive editorial tasks while keeping editors in control.
From product changes to published content — one connected workflow.
Collect product changes, linked work, and release context.
Analyze tickets and identify related help articles.
Draft, review, and update user-facing help content.
Review multilingual content and sync translation workflows.
Generate release notes from Jira and editorial decisions.
Push final content to Joomla, Confluence, or GitLab.
Technical editors managed 326 help articles across multiple Joomla instances while juggling Jira, Phrase, Figma, email, and internal documentation. Preparing each release meant hours of manual research, context switching, and coordination.
Rather than replacing existing tools, I designed a workflow layer that connects them. AI identifies documentation gaps, prioritizes work, drafts updates, and automates repetitive editorial tasks while keeping editors in control.
From product changes to published content — one connected workflow.
Collect product changes, linked work, and release context.
Analyze tickets and identify related help articles.
Draft, review, and update user-facing help content.
Review multilingual content and sync translation workflows.
Generate release notes from Jira and editorial decisions.
Push final content to Joomla, Confluence, or GitLab.
Six AI-assisted workflows that reduce manual effort across the entire documentation lifecycle.
Six AI-assisted workflows that reduce manual effort across the entire documentation lifecycle.
Six AI-assisted workflows that reduce manual effort across the entire documentation lifecycle.
The Content Hub transformed fragmented editorial workflows into a single AI-assisted workspace, reducing repetitive work, improving documentation quality, and accelerating release preparation.
Replaced constant switching between Jira, Joomla, Phrase, email, and documentation with one connected workspace.
AI automatically identified affected articles and recommended updates, removing hours of manual investigation before releases.
Embedded style guidance and terminology validation directly into the editorial workflow, improving consistency across documentation.
Reduced changelog creation from 1–2 hours to approximately 30 minutes while creating reusable workflows for documentation, translation, and release management.
The Content Hub transformed fragmented editorial workflows into a single AI-assisted workspace, reducing repetitive work, improving documentation quality, and accelerating release preparation.
Replaced constant switching between Jira, Joomla, Phrase, email, and documentation with one connected workspace.
AI automatically identified affected articles and recommended updates, removing hours of manual investigation before releases.
Embedded style guidance and terminology validation directly into the editorial workflow, improving consistency across documentation.
Reduced changelog creation from 1–2 hours to approximately 30 minutes while creating reusable workflows for documentation, translation, and release management.
The Content Hub transformed fragmented editorial workflows into a single AI-assisted workspace, reducing repetitive work, improving documentation quality, and accelerating release preparation.
Replaced constant switching between Jira, Joomla, Phrase, email, and documentation with one connected workspace.
AI automatically identified affected articles and recommended updates, removing hours of manual investigation before releases.
Embedded style guidance and terminology validation directly into the editorial workflow, improving consistency across documentation.
Reduced changelog creation from 1–2 hours to approximately 30 minutes while creating reusable workflows for documentation, translation, and release management.

