Markdown
02 / 02

GFM Extensions & Doc Tooling

GFM Extensions & Doc Tooling

Tables & Task Lists

| Feature      | Status |  Priority |
| :----------- | :----: | --------: |
| Login        |   ✅   |      High |
| Dark mode    |   🚧   |    Medium |
<!-- :--- left-align, :---: center, ---: right-align -->

- [x] Write the draft
- [ ] Get it reviewed
- [ ] Publish

Raw HTML & Front Matter

---
title: My Post
date: 2026-01-15
tags: [markdown, docs]
---

<!-- Front matter (YAML between --- delimiters) is a static-site-generator
     convention (Jekyll, Hugo, etc.), not part of core Markdown/CommonMark.
     It's parsed separately from the body content below it. -->

Most renderers pass raw HTML through untouched for anything Markdown's
syntax doesn't cover:

<details>
<summary>Click to expand</summary>

Hidden content here — Markdown syntax still works INSIDE the HTML block.

</details>

CommonMark & Renderer Differences

The original Markdown spec left several edge cases ambiguous, so implementations (GitHub, Markdown.pl, various editors) diverged over time. CommonMark was created as a strict, unambiguous specification to reduce this fragmentation — GitHub Flavored Markdown (GFM, which adds tables, task lists, strikethrough, and autolinks) is built on top of CommonMark. If a document renders differently across two tools, it's often a genuine historical spec ambiguity rather than a bug.

Keep your own version of these notes — editable, searchable, and organised by your stack.

Start free