Hugo on Artark AI

The Missing Slash: Troubleshooting Hugo Twitter Cards and baseURL Paths

Thu, 27 Aug 2026 05:57:00 -0400

I recently finalized a pretty neat automation for my static blog. I built a custom Gemini skill that takes my Obsidian drafts and automatically generates wobbly, hand-drawn-style cover banners and spot illustrations. The workflow is entirely frictionless: I write in Obsidian, sync via the iOS Git plugin, and GitHub Actions takes over to build the Hugo site.

The pipeline worked flawlessly—until I tried to share the latest post on X (Twitter).

Hugo Blog Pipeline: From Markdown to Live Site in One Push

Sun, 23 Aug 2026 14:40:00 -0400

I open-sourced the tooling I use to run this blog. It is a set of scripts that sit on top of Hugo and GitHub Pages, handling the things Hugo does not: scaffolding posts correctly, validating front matter before deploy, fitting banner images for social cards, and keeping two devices in sync through git alone.

The repo is here: github.com/robertluwang/hugo-blog-pipeline

This post explains why it exists and how to set up a new blog from scratch using it.

The Complete Hugo Blogging Pipeline

Sun, 23 Aug 2026 09:58:00 -0400

This is the whole pipeline I use to write and publish a Hugo blog from Linux (including WSL on Windows 11): repo layout, scaffolding, banner handling, a validation gate in CI, and one command to publish. It also covers writing from an iPhone, because the moment a second device exists most of the interesting failures appear.

It replaces an earlier setup of mine that used an Obsidian vault on Windows and an rsync script. That approach is fine for one device — the original post still stands if that is you — but it silently deleted a section from a published post once I added a phone. That failure shaped everything below.

Fix the Missing Social Card Banner in Hugo PaperMod

Sun, 23 Aug 2026 06:56:59 -0400

You share a post link on X or LinkedIn and the card comes up as a bare title with no banner. The image is right there on the page, so the obvious guess is that the crawler cannot find it. That guess sends most people down the wrong path.

The tags the crawler actually reads

Social platforms never look at the images in your page body. They read two meta tags in <head>:

Blog from iPhone with Obsidian Git

Sat, 15 Aug 2026 18:17:00 -0400

You can write and publish blog posts from your iPhone using Obsidian and the Obsidian Git community plugin. No computer needed — write a post on the train, push to GitHub, and your Hugo site updates automatically.

Here is the setup.

What You Need

iPhone with Obsidian installed (free from App Store)
GitHub repo with Hugo + GitHub Actions pipeline already working
GitHub Personal Access Token (fine-grained)

Step 1: Generate a GitHub Token

Go to https://github.com/settings/tokens
Generate new token → Fine-grained token
- Token name: obsidian-iphone
- Expiration: 90 days (or longer)
- Repository access: Only select repositories → pick your Hugo repo
Under Permissions, click "+ Add permissions"
- Find “Contents” → set to Read and write
- Metadata (Read-only) is auto-added
Generate token → copy it immediately

Step 2: Create a Vault

Open Obsidian on iPhone → Create new vault:

Obsidian + Hugo + GitHub Pages on Windows 11

Sat, 15 Aug 2026 00:00:00 +0000

Obsidian is a beautiful markdown editor. Hugo is a fast static site generator. GitHub Pages is free hosting with CI/CD. The challenge is wiring them together on Windows 11 where Obsidian runs natively but Hugo and git live in WSL.

Here is the setup that works.

The Problem

Obsidian is a Windows desktop app. Hugo and git run in WSL (Ubuntu). They need to read and write the same markdown files. The obvious answers all fail:

Hugo Blog Pipeline

Sat, 08 Aug 2026 16:27:40 -0400

I got tired of WordPress. Not because it crashed or ran slow — it worked fine — but because every time I sat down to write, I was fighting the editor instead of writing. The block system turns a simple paragraph into a drag-and-drop puzzle. I wanted a blogging pipeline where I write a markdown file, push it to git, and the post goes live. That is it. No block picker, no sidebar toggles, no plugin updates, no database.