How to Preview and Publish Markdown Posts to Hugo on GitHub Pages (Markdown 101 - Part 06)

// SERIES: Markdown 101 (10 lessons · Jump to any part)
  1. 01 Capstone Practice - Write a Complete Markdown Article from Scratch (Markdown 101 - Part 10)
  2. 02 How to Add Links and SEO-Friendly Images in Markdown (Markdown 101 - Part 04)
  3. 03 How to Create Tables and Horizontal Rules in Markdown (Markdown 101 - Part 07)
  4. 04 How to Preview and Publish Markdown Posts to Hugo on GitHub Pages (Markdown 101 - Part 06)
  5. 05 How to Use Obsidian Callouts and Wikilinks and Export Cleanly to Hugo (Markdown 101 - Part 09)
  6. 06 How to Write Checklists, Footnotes, and Escaped Characters in Markdown (Markdown 101 - Part 08)
  7. 07 How to Write Headings, Paragraphs, and Emphasis in Markdown (Markdown 101 - Part 02)
  8. 08 How to Write Lists, Blockquotes, and Code Blocks in Markdown (Markdown 101 - Part 03)
  9. 09 Minimal Markdown Post Template and YAML Front Matter for Blogs (Markdown 101 - Part 05)
  10. 10 What Is Markdown and How to Create Your First .md File (Markdown 101 - Part 01)

Markdown 101 · Part 6/10

Before publishing a Markdown draft from Obsidian to Hugo, review the content against a short checklist, preview the rendered HTML locally with hugo server, and verify the live URL after deployment. The blog commands below are part of Dyn’s custom workflow.

Pre-Publish Quality Checklist

  • Direct opening: Do the first 1–2 sentences answer the reader’s main question?
  • Heading hierarchy: Exactly one H1 (from the post title), with ## and ### in logical order.
  • Complete YAML: Unique Mô tả, lowercase hyphenated Slug, Chuyên mục, and tags.
  • Clean Markdown: Closed code fences, meaningful image alt text, and zero local drive paths.

Preview Locally With Hugo

Run the preview server in your Terminal (or click Preview in blog ui):

blog preview

This builds a local preview—including drafts—at http://127.0.0.1:1313. Because Obsidian-specific syntax (such as wikilinks) renders differently on the web, always use standard Markdown links for public navigation.

Publish to GitHub Pages

Before publishing, verify Ngày xuất bản in YAML (if blank, the converter falls back to Ngày tạo), then run:

blog publish "markdown-101-01-getting-started"

The script converts the Obsidian note into a Hugo bundle, verifies the build with hugo --gc --minify, commits, and pushes to GitHub. Keep unfinished parts in draft status and only add links to parts that are already live.

Post-Deploy Verification

  1. Open the live URL on cmduyeen.github.io and check layout, code blocks, and images on both desktop and mobile.
  2. Click every internal link and reference link.
  3. Confirm the post appears in Archive and /en/sitemap.xml.
  4. If your domain is verified in Google Search Console, run URL Inspection to check indexing status.

Practice Now

Fix the draft snippet below: add a space after ##, remove the filler intro, and turn the checklist items into a bulleted list.

Practice Now

Fix the heading syntax, remove the filler sentence, and format the last three lines as a bulleted list.

Live Preview
Show hint

Add a space after ##. Prefix each checklist item with - and a space.

Runs locally in your browser (nothing is uploaded or auto-saved). Supports headings, paragraphs, lists, checklists, tables, blockquotes, code, emphasis, links, and local site images.

Source: Hugo Content Management.


In the Markdown 101 series:

Loading comments...