DocBook is a markup vocabulary built for technical documentation. The project’s own description states that DocBook is “an XML vocabulary ideally suited to computer hardware and software documentation, though it is by no means limited to those domains.” Rather than describing how a document should look, DocBook describes what each part of a document is: a book, a chapter, a section, a procedure with numbered steps, a programlisting, a warning, a cross-reference, or a glossary entry. Authors write this structured source once, and tooling transforms it into many presentation formats.
That separation of structure from appearance is the heart of DocBook’s design and the reason it became a standard for large documentation projects. A single DocBook source set can be rendered to HTML for the web, to PDF or PostScript for print, to manual pages, to help formats, and to ebook formats, all from the same content. Open-source toolchains built around DocBook, in particular the DocBook XSL stylesheets, turn the markup into finished output, so an organization can maintain one authoritative version of a manual and publish it everywhere. This single-source, multi-output workflow is what DocBook is most known for.
DocBook began in 1991 as an SGML application, originally a joint effort associated with HaL Computer Systems and O’Reilly for exchanging technical books and manuals. It was an early and influential demonstration of SGML’s promise: define a document type with a declared grammar, mark up content against it, and validate and process documents mechanically. As XML emerged as a simplified subset of SGML, DocBook migrated to an XML schema, and the same vocabulary carried forward with modern, more easily implemented tooling. The W3C XML Recommendation describes XML as “a subset of SGML,” which is exactly the migration path DocBook followed.
For most of its life DocBook was developed and maintained under the Organization for the Advancement of Structured Information Standards (OASIS), through a dedicated DocBook Technical Committee that issued successive versions of the schema, including DocBook 5, which adopted relax NG and namespaces for a cleaner modular design. That committee structure made DocBook a formally governed, vendor-neutral standard rather than a single company’s format. The committee was closed in 2024, and the canonical schemas, stylesheets, and documentation continue to be hosted at docbook.org.
DocBook’s lasting significance is its role as the proving ground for structured, single-source technical publishing. Many large software projects, operating-system documentation sets, and computer-book publishers adopted it, and the patterns it established — semantic element names for documentation, a declared grammar for validation, and stylesheet-driven transformation to multiple outputs — shaped how technical documentation is authored across the industry, influencing later lightweight and XML-based documentation systems alike.