Markdown parser with unified pipeline

5 min read

The markdown format is a natural format to store structured content for a content management system:

  • it is a text format which is both easy to read and easy to write without any tool
  • it describes only the structure of the content, and is totally presentation free
  • with the addition of front matter, you can then easily add all the meta information required to support the content: name of the author, date, tags etc…

That’s the reason why most static sites generators rely on that format to store their content.

You still need some extra tooling to integrated markdown content in a website.

For instance, you need mechanisms:

  • to wrap the content in a generated HTML page with possibly a header, sidebar, footer etc…
  • to process the content, such as applying a code highlighter on code blocks
  • to generate a table of content for the home page of the site

There are also a lot of markdown parsers and they come in 2 flavors:

  • they transform the markdown input into HTML (or some other formats like pdf)
  • they provide an API to give access to an Abstract Syntax Tree (AST) for further processing

In the latter category comes unified


The best way to understand what unified is about is to look first at some code:

  .use(markdown) // 1
	.use(toc) // 2
  .use(remark2rehype) // 3
  .use(doc, {title: 'My Web site'}) // 4
  .use(html) // 5
  .process('# Hello world!', function (err, file) { // 6
    console.error(report(err || file))

Unified provides an entire pipeline to process structured data:

  • step 1: you parse some input text data into a Markdown AST tree
  • step 2: you transform the markdown AST to add a table of content on top of the document
  • step 3: you transform the markdown tree into an HTML tree
  • step 4: you add in the HTML header the title of the page
  • step 5: you transform the HTML tree into a html text representation
  • step 6: that’s where the processing takes place XXYYZZ:
    • you provide the markdown text input to be parsed in step 1
    • you retrieve the html data at the end of the pipeline, and store it in a file

Unified = parser + transformers + compiler

All the components of the unified pipeline are plain old javascript function.

Even though the unified API use a common syntax (use) to build the pipeline, there are different types of components in the pipeline.


The parser is unique in the pipeline and its role is to parse text into a syntax tree.

Unified supports out of the box 3 main specifications for syntax trees:

  • mdast : representation of a markdown syntax tree
  • hast : representation of an HTML syntax tree, with embedded SVG or MathML
  • nlcst : representation of natural language syntax tree

All those trees implement the unistspecification which is a very simple tree description with node and children…

There are a few parsers available but it is pretty easy to write your own. The major constraint is that the parser has to be a synchronous function.

From an API perspective, the way to write a parser can be a bit confusing:

  • this is a javascript function for which this is set to the unified pipeline instance
  • when this function is called, you set the value of this.Parser to another function which is the actual parser
  • the prototype of that parser is: (text: string, file: VFile): Node where
    • text is the text to parse and
    • file is a data structure describing the input to be processed.
    • The function returns a Node which is the tree representing the content and that has to be compliant with the unist specification.


At the other end of the pipeline is the compiler which is in charge of converting back the tree into a text representation. There are few cases where you would want to write your own compiler as you have implementation to compiler mdast (Markdown) or hast (HTML) back to text.


That’s where the magic of unified happens.

From an API perspective, a transformer method is a method which returns a function which follows the Transformer type:

type Transformer = (
    node: Node,
    file: VFile,
    next?: (
      error: Error | null,
      tree: Node,
      file: VFile
    ) => Record<string, unknown>
  ) => Error | Node | Promise<Node> | void | Promise<void>

At its core, this function can transform the tree provides as the node parameter: you can add, remove or change nodes in that tree.

The next option parameter allows you to implement asynchronous transformation: you call that method when your processing is over.

Unified ecosystem

Unified comes with a huge ecosystem of plugins. You can easily assemble or build your own set of transformers to parse your markdown content and generate the associated HTML files for your static site.

Unified usage example

The site that you are reading ( uses a custom made static site generator which relies heavily on unified.

The content is written in which acts as a headless CMS and a couple of github actions process that content to generate the website.

The generation of this site is a 2 steps process.

step 1: content retrieval

A custom parser parses the notion pages into a markdown tree

Another custom transformer retrieves the images from to store them along side the generated markdown

The result of this first step is to have all the page contents retrieved from and stored into markdown files and archived in github

step 2: site generator

Another unified pipeline parses the markdown files from github and generate the HTML pages which will be served by github pages.

There are also a coupe of transformers used in that process:

  • a transformer to add a header and footer to each blog article page
  • a transformer to process the code blocks in order to provide syntax highlighting
  • a transformer to generate the home page