hugo new blog/my-post.adocToph treats AsciiDoc as a first-class content format. Everything that works with Markdown also works with AsciiDoc β taxonomy badges, post metadata, cover images, heading anchors, and navigation.
Why AsciiDoc? π
AsciiDoc offers features that Markdown does not:
Native table of contents with
:toc:document attributeAdmonition blocks (NOTE, TIP, WARNING, IMPORTANT, CAUTION)
Include directives for reusing content across pages
Built-in support for complex tables and nested lists
If you are already comfortable writing in AsciiDoc, Toph will serve your needs without compromise.
Creating an AsciiDoc post π
Create a file with the .adoc extension in your blog directory:
Add YAML front matter at the top of the file, followed by AsciiDoc content:
---
title: "My Post Title"
date: 2026-01-15
draft: false
categories:
- "tech"
tags:
- "hugo"
- "asciidoc"
author: "Author Name"
description: "A short summary of the post."
---
Your AsciiDoc content starts here.Table of contents π
To enable a table of contents, add the :toc: attribute after the front matter:
---
title: "My Post Title"
toc: true
---
:toc:
== First SectionTophβs CSS styles the AsciiDoc-generated table of contents identically to Markdownβs toc: true front matter option.
Both formats produce the same visual result.
Heading anchors π
Clickable anchor links (π) appear on hover for all section headings. For Markdown, this is handled by a Hugo render hook. For AsciiDoc, Toph injects the same anchor markup via template processing. Both formats produce identical results.