( _protected )

Behind the screens

Some details of this project are protected due to client confidentiality. Enter the password to view the full project.

( _protected )

Behind the screens

Some details of this project are protected due to client confidentiality. Enter the password to view the full project.

Quentic Content Hub

Quentic Content Hub

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

mountain_flag

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.

cognition

APPROACH

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.

The workflow

From product changes to published content — one connected workflow.

confirmation_number
01

Jira tickets

Collect product changes, linked work, and release context.

auto_awesome
02

Help updates

Analyze tickets and identify related help articles.

description
03

Documentation

Draft, review, and update user-facing help content.

translate
04

Translation

Review multilingual content and sync translation workflows.

history_edu
05

Changelog

Generate release notes from Jira and editorial decisions.

cloud_upload
06

Publish

Push final content to Joomla, Confluence, or GitLab.

mountain_flag

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.

cognition

APPROACH

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.

The workflow

From product changes to published content — one connected workflow.

confirmation_number
01

Jira tickets

Collect product changes, linked work, and release context.

auto_awesome
02

Help updates

Analyze tickets and identify related help articles.

description
03

Documentation

Draft, review, and update user-facing help content.

translate
04

Translation

Review multilingual content and sync translation workflows.

history_edu
05

Changelog

Generate release notes from Jira and editorial decisions.

cloud_upload
06

Publish

Push final content to Joomla, Confluence, or GitLab.

mountain_flag

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.

cognition

APPROACH

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.

The workflow

From product changes to published content — one connected workflow.

confirmation_number
01

Jira tickets

Collect product changes, linked work, and release context.

auto_awesome
02

Help updates

Analyze tickets and identify related help articles.

description
03

Documentation

Draft, review, and update user-facing help content.

translate
04

Translation

Review multilingual content and sync translation workflows.

history_edu
05

Changelog

Generate release notes from Jira and editorial decisions.

cloud_upload
06

Publish

Push final content to Joomla, Confluence, or GitLab.

Core features

Built for technical editors. Powered by AI.

Six AI-assisted workflows that reduce manual effort across the entire documentation lifecycle.

Core features

Built for technical editors. Powered by AI.

Six AI-assisted workflows that reduce manual effort across the entire documentation lifecycle.

Core features

Built for technical editors. Powered by AI.

Six AI-assisted workflows that reduce manual effort across the entire documentation lifecycle.

Impact

Central workspace for technical editing

The Content Hub transformed fragmented editorial workflows into a single AI-assisted workspace, reducing repetitive work, improving documentation quality, and accelerating release preparation.

Less context switching

Replaced constant switching between Jira, Joomla, Phrase, email, and documentation with one connected workspace.

Faster documentation decisions

AI automatically identified affected articles and recommended updates, removing hours of manual investigation before releases.

More consistent UX writing

Embedded style guidance and terminology validation directly into the editorial workflow, improving consistency across documentation.

Scalable content operations

Reduced changelog creation from 1–2 hours to approximately 30 minutes while creating reusable workflows for documentation, translation, and release management.

Impact

Central workspace for technical editing

The Content Hub transformed fragmented editorial workflows into a single AI-assisted workspace, reducing repetitive work, improving documentation quality, and accelerating release preparation.

Less context switching

Replaced constant switching between Jira, Joomla, Phrase, email, and documentation with one connected workspace.

Faster documentation decisions

AI automatically identified affected articles and recommended updates, removing hours of manual investigation before releases.

More consistent UX writing

Embedded style guidance and terminology validation directly into the editorial workflow, improving consistency across documentation.

Scalable content operations

Reduced changelog creation from 1–2 hours to approximately 30 minutes while creating reusable workflows for documentation, translation, and release management.

Impact

Central workspace for technical editing

The Content Hub transformed fragmented editorial workflows into a single AI-assisted workspace, reducing repetitive work, improving documentation quality, and accelerating release preparation.

Less context switching

Replaced constant switching between Jira, Joomla, Phrase, email, and documentation with one connected workspace.

Faster documentation decisions

AI automatically identified affected articles and recommended updates, removing hours of manual investigation before releases.

More consistent UX writing

Embedded style guidance and terminology validation directly into the editorial workflow, improving consistency across documentation.

Scalable content operations

Reduced changelog creation from 1–2 hours to approximately 30 minutes while creating reusable workflows for documentation, translation, and release management.