Demo Post: Checking the Publishing Pipeline

This is a demo post created to verify that the write → commit → push → deploy pipeline works end to end.

---

What happens when I push

Pushing to main triggers the Build and Deploy workflow in .github/workflows/pages-deploy.yml:

1. Checkout the repository.
2. Setup Ruby 3.3 and install gems from the Gemfile.
3. Build the site with JEKYLL_ENV=production.
4. Test the output with htmlproofer — a broken internal link fails the build here.
5. Deploy the artifact to GitHub Pages.

The whole run usually finishes in a couple of minutes.

If a post never appears, check the Actions tab first. A failed htmlproofer step means the site was built but never deployed.

Anatomy of a post

Every file in _posts needs two things:

• A filename in the form YYYY-MM-DD-title.md.
• Front matter with at least a title and a date.

---
layout: post
title: "Your title here"
date: 2026-09-01 06:00:00 +0000
categories: [Tech]
tags: [Jekyll, Demo]
---

The date in the filename and the date in the front matter should agree. When they disagree, the front matter wins for sorting and display, while the filename still controls the generated URL.

A few Chirpy extras

Callouts are just blockquotes with a class:

Tips render in green.

Info renders in blue.

Code blocks get syntax highlighting and a copy button for free:

def greet(name: str) -> str:
    return f"Hello, {name}!"

That is all this post is for — if you are reading it on the live site, the pipeline works.