Skip to main content
Shakewell

Structured Authoring

DocBook — Structured Authoring & XML Publishing Standard

Semantic markup vocabulary for technical documentation and publishing workflows.

Overview

What is DocBook?

DocBook is a semantic markup language for technical documentation. It allows you to create document content in a presentation-neutral form that captures the logical structure of the content.

Key Features

  • Semantic markup: focus on meaning, not presentation
  • Rich element set: comprehensive vocabulary for technical docs
  • Multiple output formats: HTML, PDF, EPUB from one source
  • Cross-references and linking: sophisticated reference capabilities
  • Internationalization: support for multiple languages

Also written as: OASIS DocBook

Who DocBook Applies To

DocBook is an open OASIS standard with no industry mandate behind it. It suits organizations whose deliverables are genuinely book-shaped — manuals, references, guides — and which want a rich vocabulary immediately rather than an architecture to build on. Choosing it is a judgment about the shape of your content, not about compliance.

Where DocBook Programs Go Wrong

  • Choosing DocBook when the real requirement is reuse across many publications, which is the problem DITA was designed for.
  • Using its breadth without constraint. The element set is large, and an unconstrained subset makes content inconsistent between authors and harder to transform.
  • Leaving legacy SGML DocBook unconverted until a toolchain change forces it.

How It Relates to Other Standards

DITA
The usual alternative. Choose DocBook for document-shaped deliverables and a comprehensive vocabulary out of the box; choose DITA when reuse across publications is the driving requirement.
SGML
DocBook's origins are in SGML, and legacy DocBook libraries are frequently found in SGML form.

DocBook Questions

What is DocBook?

A semantic markup vocabulary for technical documentation. Content is captured by what it means rather than how it should look, so one source produces HTML, PDF and other outputs. Its element set is comprehensive out of the box, which is its main practical advantage over architectures you have to model first.

Is DocBook still worth using?

For book-shaped technical content with an established toolchain, yes. The decision is rarely DocBook versus nothing — it is DocBook versus DITA, and it turns on whether your content is documents that need structure or topics that need assembling.

Where to Get DocBook

DocBook is an open OASIS standard: the schemas, the definitive guide, and the stylesheets are all freely available.

PublishingSemanticBooks

Where DocBook Applies

All standardsTechnical publications servicesTalk to us about DocBook

Get In Touch

Let's Talk

Planning, building, or migrating DocBook-compliant technical content? We can help.

Contact Shakewell LLC

or email hello@shakewell.agency