The word "template" gets used in at least three completely different ways in the markdown world. In Jekyll and Hugo, a template is a structural wrapper that determines how markdown content becomes an HTML page. In Obsidian, a template is a content scaffold that inserts pre-written text into new notes. In Unmarkdown™, a template is a visual styling layer that controls how your markdown looks without changing a single character of your content.
Understanding the differences matters because choosing the wrong tool for the wrong type of template wastes time and produces frustrating results. This guide breaks down what markdown templates actually are, how each approach works, and why visual presentation templates are becoming essential for anyone who publishes markdown content.
Templates in the static site generator world
The concept of markdown templates originated with static site generators. Jekyll, the first major SSG, introduced front matter in 2008: a block of YAML metadata enclosed between triple dashes at the top of a markdown file. Hugo later adopted the same convention, also accepting TOML and JSON as front matter formats.
In this context, a template is an HTML layout file that wraps your markdown content. When Jekyll or Hugo processes a markdown file, it converts the markdown to HTML, then injects that HTML into a template. The template defines the page structure: where the navigation goes, what the sidebar contains, how the footer looks, and where your content appears within the overall page layout.
The relationship between content and template is declared in the front matter. A layout field tells the generator which template to use:
---
title: "My Blog Post"
layout: post
date: 2026-02-24
---
Templates live in dedicated directories. Jekyll uses _layouts/ for full page layouts and _includes/ for reusable components like headers and footers. Hugo uses layouts/ with a hierarchy of base templates, section templates, and single page templates. Both systems support template inheritance, where a specific template extends a more general one.
This is a powerful model for building websites. But it requires HTML, CSS, and often JavaScript knowledge. The templates control rendering structure: they determine what HTML elements surround your content and how the page is constructed. They do not inherently control how your prose looks. Visual styling still requires writing CSS.
For developers building documentation sites or personal blogs, this approach works well. For someone who just wants their markdown to look professional, it introduces a significant learning curve. You need to understand the generator's templating language (Liquid for Jekyll, Go templates for Hugo), set up a build pipeline, manage a directory of template files, and write your own CSS for visual styling.
How Obsidian approaches templates
Obsidian takes a completely different approach. In Obsidian, templates are content scaffolds, not structural wrappers. They insert pre-written markdown into your notes, saving you from typing the same boilerplate repeatedly.
Obsidian offers two template systems.
The core Templates plugin is built into Obsidian and provides static snippet insertion. You create template files in a designated folder, and each file contains the text you want to insert. Three dynamic variables are supported: {{title}} (the current note's title), {{date}} (today's date), and {{time}} (the current time). When you trigger the template, it pastes the content at your cursor position with those variables replaced.
This is useful for consistent note structure. A meeting notes template might include headings for Attendees, Agenda, Discussion, and Action Items. A daily journal template might start with the date and sections for Morning Reflection and Goals. The template gives you a starting point, and you fill in the details.
The Templater community plugin goes much further. It supports full JavaScript execution within templates, enabling dynamic content generation, API calls, conditional logic, and file manipulation. Templater can query your vault, calculate dates, prompt for user input, and generate content programmatically. It is essentially a scripting engine embedded in the template system.
Both Obsidian approaches share one characteristic: they operate on content. The template determines what text appears in your note. Neither system controls how that text looks when rendered or exported. Obsidian's visual appearance is governed by CSS themes and snippets, which are separate from the template system entirely.
This means Obsidian templates solve a different problem than static site generator templates. SSG templates control page structure. Obsidian templates control initial content. Neither directly addresses the question: "How do I make my markdown look professional when I share it?"
The gap between structure and presentation
Both traditional template approaches leave a significant gap when it comes to visual presentation.
Static site generator templates define HTML structure, but visual styling requires writing CSS. You can change the layout of a page, but making your prose typography look polished means understanding CSS properties like font-family, line-height, letter-spacing, and margin-bottom. Most SSG themes bundle CSS with their structural templates, blurring the line, but customizing that visual styling still requires CSS knowledge.
Obsidian templates provide content scaffolding, but no presentation control at all. The same template content looks different depending on which CSS theme you have installed. And when you export or share that content outside Obsidian, the visual styling does not follow. Your carefully formatted note becomes raw markdown text, and the recipient sees whatever default styling their application provides.
This gap becomes more pronounced as markdown content moves beyond personal notes and developer documentation. When a consultant needs to send a polished report to a client, the typography and spacing matter. When a team publishes internal documentation, the visual consistency matters. When someone converts AI-generated content into a Google Doc or email, the professional appearance matters.
Content structure and content presentation are both important, but they are different concerns. The markdown ecosystem has spent years building excellent tools for structure (SSGs) and content creation (editors like Obsidian). Visual presentation has received far less attention.
Visual presentation templates
Unmarkdown™ approaches templates from the presentation angle. The core idea is simple: your markdown stays exactly the same, but the visual output changes completely depending on which template you select.
Unmarkdown™ offers 62 templates organized across eight categories: Free, Business, Academic, Developer, Creative, Dark, Productivity, and Special. Each template controls a comprehensive set of visual properties.
Typography includes body font family, heading font family, code font family, font weights, base font size, individual heading scales for H1 through H6, line height, and letter spacing. A template can pair a serif heading font with a sans-serif body font, tighten the letter spacing for a modern feel, or increase line height for better readability in long-form content.
Colors span 16 properties per light/dark mode: background, text, headings, accents, links, borders, inline code text, inline code background, code block background, code block text, highlight background, highlight text, blockquote border, blockquote text, table header background, and table border. Every template defines both light and dark variants.
Element styling covers blockquote presentation (left border, full border, or accent background), horizontal rule appearance, table style (minimal, bordered, or striped), code block corner radius, line number visibility, image border radius, and link underline behavior.
Spacing controls content width, paragraph spacing, heading spacing, and list indentation.
None of this requires front matter, build steps, or CSS knowledge. You write markdown. You pick a template. The output reflects that template's visual choices. Switch templates, and the same content looks entirely different.
For Pro users, a custom template editor provides direct control over all of these properties. Approximately 60 controls organized into five sections (Typography, Colors, Elements, Spacing, Alignment) let you build a template that matches your brand or personal style. The editor shows a live preview as you adjust settings, and your custom templates appear alongside the built-in options in the template picker.
Why this distinction matters
The three approaches serve three fundamentally different needs.
Static site generator templates are for building websites. They define page structure, navigation, and layout. They are ideal when you are creating a documentation site, a blog, or any web property where pages need consistent HTML structure. The audience is developers who are comfortable with build tools and templating languages.
Content scaffolding templates (Obsidian, Notion, and similar tools) are for writing efficiency. They save time by inserting boilerplate text and structure into new documents. They are ideal for anyone who creates similar documents repeatedly: meeting notes, journal entries, project briefs, status updates. The audience is writers and knowledge workers who want consistency in their content.
Visual presentation templates are for publishing. They control how finished content looks to the reader. They are ideal when your markdown needs to become a professional document, whether that document is a web page, a Google Doc, a Word file, a Slack message, or an email. The audience is anyone who needs their markdown to look polished without writing CSS.
The distinction matters more now than it did five years ago. AI tools generate enormous amounts of markdown content. Developers, writers, and business professionals all work with markdown regularly. The need to publish that markdown, to turn it into something visually complete, has grown faster than the tooling to support it.
How visual templates work in practice
The practical workflow with visual presentation templates is straightforward.
You write or paste markdown into Unmarkdown™. This could be content you wrote yourself, output from ChatGPT or Claude, notes exported from Obsidian, or documentation from a GitHub repository. The source does not matter. All that matters is that the input is markdown.
You select a template from the picker. The preview immediately reflects the template's visual properties. If you are preparing a consulting deliverable, you might choose the Executive template (serif headings, generous spacing, muted colors). If you are publishing developer documentation, the GitHub template or Terminal template might be appropriate. If you are sending a team update, the Newsletter template provides clean, scannable formatting.
You publish to your chosen destination. For a web page, you get a shareable URL with the template styling baked in. For Google Docs, the template's fonts, colors, and heading styles translate into native Google Docs formatting. For Slack, the content converts to Slack's mrkdwn syntax. For email, the styling becomes inline CSS that email clients can render.
The same markdown, published through different templates, produces visually distinct documents. A quarterly report looks like a quarterly report. A technical spec looks like a technical spec. A creative brief looks like a creative brief. The content stays identical. The presentation adapts.
Templates and AI output
AI-generated content has made visual templates more relevant than ever. When ChatGPT or Claude generates a report, a comparison, or a set of recommendations, the output is well-structured markdown with headings, lists, tables, and emphasis. The content quality is often good enough to use directly.
What the content lacks is visual identity. Raw markdown rendered as basic HTML looks functional but generic. It does not look like a document that came from your organization or reflects your professional standards. It looks like what it is: machine-generated text with default styling.
Visual templates close this gap. They take structurally sound AI output and give it a professional appearance. A document that would take 20 minutes to manually format in Google Docs or Word can be styled in seconds by selecting the right template.
This is particularly valuable for recurring workflows. If you regularly generate weekly reports, client summaries, or project documentation with AI tools, a template ensures every output looks consistent. The AI handles the content. The template handles the presentation. You handle neither the writing nor the formatting, and the result still looks like it came from a professional.
Choosing the right template approach
The right template system depends on what you are building and where your content needs to go.
If you are building a website with markdown content, static site generator templates remain the right choice. Jekyll, Hugo, Astro, and similar tools provide the structural control needed for web applications. The investment in learning their template systems pays off in flexibility and power.
If you are standardizing note-taking or document creation within a knowledge management tool, content scaffolding templates (Obsidian's core Templates or Templater) save time and enforce consistency. They solve a real problem for anyone who creates similar documents repeatedly.
If you need your markdown to look professional in its final destination, whether that is a web page, a Google Doc, a Word file, a Slack message, or an email, visual presentation templates are the right tool. They address the specific problem of turning raw markdown into polished output without requiring CSS knowledge or manual formatting.
Many workflows benefit from combining approaches. You might use Obsidian's Templater to scaffold a project brief, write the content in Obsidian, then use Unmarkdown™'s visual templates to publish it as a polished web page or format it for Google Docs. Each template system handles its part of the pipeline.
The markdown template landscape is broader than any single definition suggests. Understanding the distinctions helps you choose the right tools and avoid the frustration of trying to make a structural template solve a presentation problem, or vice versa.
