Editing normanli.net — Publishing Workflow

Quick reference for maintaining the blog at normanli.net.

Tech stack

• Static site: Hugo (v0.68.3 locally, newer on Cloudflare)
• Hosting: Cloudflare Pages (auto-deploys from GitHub)
• Repo: normanli33/blog.normanli.net (master branch)
• Theme: Custom (ChatGPT Codex design, self-hosted fonts, warm terracotta palette)

Content sections

Quick edit (fix a typo)

cd ~/blog.normanli.net
vim content/analysis/forecast-bias.md   # edit the file
hugo --minify                           # verify it builds
git add -A && git commit -m "Fix typo" && git push

Cloudflare auto-deploys in ~30 seconds.

Writing a new article

hugo new analysis/your-topic.md     # creates from archetype
# or create manually:
vim content/study/new-course.md

Required frontmatter

---
title: "Your Title"
description: "One-line summary shown on listing cards and in search."
date: 2026-07-13
tags:
  - forecasting
  - inventory
---

Tags generate the pill badges on listing cards and feed /tags/ pages. No tags = card falls back to section name.

Build + preview locally

hugo --minify          # builds to public/
hugo server            # dev server at localhost:1313 (live reload)

Full deploy loop

cd ~/blog.normanli.net
hugo --minify          # always verify first
git add -A
git commit -m "Brief description of changes"
git push               # Cloudflare auto-deploys master branch

What NOT to do

• Don’t edit public/ — it’s build output, overwritten on every hugo run.
• Don’t use Cloudflare dashboard for content changes — they’ll be overwritten by next deploy.
• Don’t edit theme HTML/CSS unless changing the design. Most content edits are just markdown files.

Pro tips

• The CSS file is at static/css/main.css — self-hosted fonts, no Google Fonts calls.
• All font files are at static/fonts/ (9 TTF files: Manrope, Source Serif 4, DM Mono).
• Config is config.toml (renamed from hugo.toml for local Hugo v0.68.3 compatibility).