Content Pipeline Health Checker

Diagnose where your documentation pipeline breaks across delivery surfaces, based on Despopoulos's source-to-delivery model and Iantosca's two-gate quality framework.

Step 1: Source Format

What format is your documentation authored in?

DITA XML

Structured, topic-based authoring with semantic tags

Markdown

Lightweight markup: GitHub, docs-as-code workflows

HTML

Direct HTML authoring or WYSIWYG CMS output

Unstructured Word / PDF

Binary formats without semantic structure

Step 2: Delivery Surfaces

Select all surfaces you deliver documentation to.

Docs site (static)

Hugo, Docusaurus, MkDocs, GitBook, or custom static site

In-app help / tooltips

Contextual help embedded inside the product UI

AI chatbot / LLM assistant

RAG-powered support, docs-trained chatbots

API reference (OpenAPI / Swagger)

Auto-generated or hand-authored API documentation

PDF / print

Printable manuals, regulatory filings, offline docs

Step 3: Transformation Layer

What sits between your source content and delivery surfaces?

Direct publish (no transformation)

Source files are deployed as-is to the delivery surface

Static site generator

Hugo, Docusaurus, MkDocs, Eleventy, Jekyll

CCMS / structured CMS

MadCap Flare, Ixiasoft, Paligo, Tridion Docs

Custom pipeline / scripts

CI/CD scripts, custom build tooling, bespoke transforms

No defined process

Ad-hoc, manual, or undefined workflow

Pipeline Health Report

Based on Despopoulos's source-to-delivery transformation model and Iantosca's two-gate quality model.

A. Break-point Analysis

B. Two-Gate Assessment

C. Top 3 Fixes

Share Your Results

Copied!

Built by Sulagna Sasmal · Frameworks: Despopoulos source-to-delivery model & Iantosca two-gate quality model · Portfolio