Interactive Prototype Portfolio demonstration of Docs-as-Code engineering. Not a commercial product. Why I built it ↓
Docs-as-Code · Git-Native · CI/CD Powered

Documentation that
ships like software

I built this to show what documentation infrastructure actually looks like. Version control, automated linting, multi-format builds, and live deployment. All from a single Markdown source.

what the demo shows · pipeline walkthrough
01
write
Open the Editor module. Write Markdown with YAML frontmatter and see it render live in the preview pane.
MarkdownFrontmatterLive Preview
→ Module 02: Editor
02
structure
The Content Map shows how docs are classified by DITA topic type — Concept, Task, Reference, Tutorial, Troubleshoot.
DITATopic TypesTaxonomy
→ Module 03: Content Map
03
lint
The Style Linter runs Vale rules against your content and scores it against Microsoft Style Guide standards.
ValeMSTP RulesReadability
→ Module 04: Style Linter
04
build
Build Outputs previews all six formats generated from a single source: HTML, PDF, OpenAPI, Postman, JSON, CHANGELOG.
HTMLPDFOpenAPI
→ Module 05: Build Outputs
05
monitor
The Dashboard shows pipeline health, build history, contributor activity, and open doc issues — all in one view.
Build StatusMetricsHistory
→ Module 01: Dashboard

Documentation that behaves like code

Traditional docs rot. Docs-as-Code keeps documentation alive, accurate, and auditable.

📜
Full Audit History
Every change tracked in Git with author, date, and commit message. Roll back any edit instantly. Essential for finance and healthcare compliance.
🔁
Single Source of Truth
One Markdown source compiles to website, PDF, and API reference. No copy-paste drift between formats. Update once, publish everywhere.
🤝
Developer-Friendly Workflow
Writers and engineers use the same tools: Git, pull requests, CI pipelines. Docs ship with the feature, not weeks later.
Automated Quality Gates
Style linting, broken-link detection, and structural validation run on every commit. Errors are caught before they reach readers.
📦
Multi-Format Output
Generate HTML portals, PDF guides, JSON schemas, and changelog feeds from the same source. Tailor output per audience without duplicating effort.
Zero-Downtime Publishing
Continuous deployment means docs go live the moment a PR merges. No manual uploads, no publishing queues, no staging servers to maintain.

Six modules. One dashboard.

The interactive demo includes each module below. Click any view in the sidebar to explore it live.

module · 01
--dashboard
Pipeline health, build history, content metrics, contributor activity, and open issues at a glance.
--build-status--metrics
module · 02
--editor
Live Markdown editor with real-time rendered preview, YAML frontmatter, and syntax highlighting.
--preview--frontmatter
module · 03
--content-map
DITA-based topic taxonomy: Concept, Task, Reference, Tutorial, and Troubleshoot topic types with visual topology.
--dita--topic-types
module · 04
--lint
Automated quality checks against Microsoft Style Guide rules with readability scoring and issue counts.
--vale--mstp--score
module · 05
--build-outputs
Preview HTML portal, PDF export, OpenAPI spec, JSON schema, Postman collection, and CHANGELOG per build.
--html--pdf--openapi
module · 06
--config
Full docforge.config.yml with toggleable build, lint, and deploy settings. Environment-aware configuration.
--yml--env--targets

Why I built DocForge

"I've spent years writing documentation for FinTech, compliance, and enterprise platforms. I needed a way to show, not just tell, that I understand the infrastructure behind the docs. So I built one."
🤖

Why not GitHub Copilot or AI writing tools?

AI tools generate text. DocForge engineers a system. Copilot writes code comments and prose. It has no concept of DITA topic taxonomy, Vale style governance, or how to architect a compliance documentation framework. This is not about generating content faster. It is about making documentation reliable, auditable, and scalable at the infrastructure level.

📚

Why not Confluence, GitBook, or Mintlify?

Those tools host documentation. DocForge engineers the pipeline. There is a real difference between a writer who uses a docs tool and an engineer who builds one. CI/CD integration, automated linting, structured topic classification, format-agnostic output. None of that comes out of the box with any off-the-shelf platform.

The gap this fills

No tool today combines a docs-native CI/CD pipeline, DITA content validation, Vale style enforcement, and multi-format output in one place built specifically for documentation teams. Not developers. Not marketers. Writers who own the entire delivery chain from source to reader.

Learn how DocForge was designed, built, and documented

DocForge is more than a prototype. It is backed by a methodology reference, a build narrative, and a live interactive demo. These four resources work together as a complete documentation engineering case study.

$ open demo.html --interactive

See it for yourself

Six modules. No login. No signup. Just click through.

Open DocForge Demo →