Markdown parser reference for the Skins Protocol blog

This article replaces the previous Chinese sample and doubles as a markdown parser checklist for the blog.

Headings and text formatting

Paragraphs support bold text, italic text, and inline code. You can also combine bold italic in the same sentence.

Third-level heading

Keep sections short and scannable. This H3 confirms nested heading depth works.

---

Links

• Internal link to the articles index
• External link to the Next.js documentation

Unordered list

• Server Components for article pages
• Markdown files stored in the posts/ folder
• Frontmatter parsed with gray-matter

Ordered list

1. Write content in markdown
2. Add YAML frontmatter
3. Deploy and verify rendering

Task list (GFM)

• Parse frontmatter fields
• Render markdown body
• Add syntax highlighting for code blocks

Blockquote

Good markdown content should be easy to scan, technically accurate, and aligned with search intent.

Blockquotes are useful for highlights, pull quotes, or short summaries.

Code block

import { getPostBySlug } from '@/lib';

const post = getPostBySlug('markdown-parser-reference');

if (post) {
  console.log(post.title, post.readingMinutes);
}

Table (GFM)

Element	Supported	Notes
Headings	Yes	H2 and H3 styled in PostContent
Lists	Yes	Ordered, unordered, and tasks
Code	Yes	Inline and fenced blocks
Tables	Yes	Rendered via remark-gfm

Strikethrough (GFM)

This line includes deprecated syntax updated guidance for markdown-based blogs.

Final checklist

If every element above looks correct on the article page, the parser pipeline is working as expected.