This series is a practical reference for advanced Markdown authoring in WebGrid.
What “Native Markdown” Means Here
In real projects, “Markdown” usually means:
- Core/CommonMark syntax (headings, lists, links, images, code, blockquotes)
- Widely adopted extensions (tables, task lists, footnotes, strikethrough)
- Platform-native authoring features (wikilinks, callouts, transclusion)
This series covers all three, with notes on portability.
Portability Tiers
Use this quick model when writing content:
- Portable everywhere — CommonMark features
- Portable in modern static-site stacks — common extensions
- Vault/runtime-specific — Obsidian-style features
If long-term portability matters, keep critical content in tiers 1–2.
Minimal “Safe” Template
---
title: My Page
description: Short summary
visibility: public
---
# Main Heading
Intro paragraph.
## Section
- Key point
- Key point
[Reference link](https://example.com)
Best Practices for Advanced Authors
- Prefer explicit headings and short sections.
- Keep one idea per paragraph.
- Use examples that can be copied directly.
- Avoid relying on a single editor-specific feature for critical content.
What’s Next
Next post: deep text structure, headings, semantic emphasis, and clean document flow.