Drafts and scheduled publishing

Both features use frontmatter only. There are no draft folders and no separate branches needed.

Drafts: published: false #

---
title: Half-formed thoughts on async
description: Not ready yet.
date: 2026-07-20
published: false
---

An article with published: false is not built at all: no HTML page exists, and it appears in no listing, feed, sitemap, or search index. It is only visible as a file in the repository.

To publish it later, change the value to true (or delete the line) and commit.

Note: the repository itself is public, so a draft is hidden from the site, not from someone browsing the repo.

Scheduling: a future date: #

---
title: Announcing Romyq 1.0
description: The launch post.
date: 2026-08-01
---

If date is in the future at build time, the article stays hidden — same treatment as a draft. You can write and commit launch posts days in advance.

Two things make the article appear when the day arrives:

1. The daily scheduled build. GitHub Actions rebuilds the site every day at 00:30 UTC (06:00 IST), so a scheduled article goes live on its date without any action from you.
2. Any other push. Every deploy re-evaluates all dates, so pushing anything after the date also releases it.

If you want a scheduled article out immediately rather than at the next daily build, trigger a deploy by hand: Actions → Deploy → Run workflow.

Checking what is pending #

Hidden articles are simply files whose frontmatter says "not yet". To review them, search the repo for published: false, or list files under content/ with dates ahead of today.