Publishing from this repo

July 25, 2026 · TJP Studio

This post exists so the blog has real content to render, and so the shape of a post is visible without reading the schema.

Adding a post

Create a markdown file in src/content/blog/. The filename becomes the URL, so spring-update.md publishes at /blog/spring-update. The frontmatter needs a title, a description (used for search results and link previews) and a published date.

---
title: 'A new thing'
description: 'One sentence that will appear in Google and on social.'
published: 2026-08-01
---

Write the post here.

Set draft: true while it is unfinished — the post still builds, but it stays out of the listing, the RSS feed and the sitemap until you remove the flag.

What happens next

Opening a pull request builds a preview at its own URL, so the post can be read in its final form before anyone approves it. Merging to main publishes it in about a minute — no application deploy, no CI queue, and nothing that can break the product.

Why the blog lives here rather than in the app

The application ships behind a full test and end-to-end suite, which is correct for code that takes payments and generates media. It is the wrong pipeline for a typo fix in a blog post. Keeping content in its own repository means writing does not wait on engineering, and a bad sentence is a revert rather than an incident.