Bench Notes

These are quick notes to verify the writing bench, rebuild flow, and the static site generation. Use this post as a reference while testing.

What to test

• Visit the bench UI at /bench
• Paste your ADMIN_TOKEN
• Create a post, tick “Rebuild after create”
• Confirm:
• New Markdown file appears under content/
• site/ is regenerated
• Homepage lists the new post
• Post page renders correctly
• Tag page includes the new post
• RSS and sitemap include updated entries

Bench endpoints

You can interact with the bench programmatically using Bearer auth.

Create a post (JSON):

POST /bench/create
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json

{
  "title": "Bench-created Post",
  "slug": "bench-created-post",
  "tags": ["bench", "api"],
  "excerpt": "Created via API from the bench.",
  "draft": false,
  "rebuild": true,
  "body": "# Heading\n\nThis post was created via the bench API."
}

Rebuild the static site:

POST /bench/rebuild
Authorization: Bearer YOUR_TOKEN

Code snippet rendering

Indented code block should render with code highlighting:

def bench_ok() -> bool:
    print("Verifying bench...")
    return True

Image, blockquote, table

Image (Markdown):

Blockquotes should render nicely and remain readable in both light and dark modes.

A small table:

Long link and UTF‑8

Long link to test wrapping: https://example.com/this/is/a/very/very/long/path/that/should/wrap/nicely/without/breaking/the/layout/or/overflowing/its/container

UTF‑8 sample: “Quotes”, en‑dash – em—dash, ellipsis…, emoji ✅

Notes

• If the homepage or tag pages don’t reflect your new post, ensure the site was rebuilt.
• Make sure BLOG_URL is set correctly for accurate links in RSS and sitemap.
• Private mode: when PRIVATE=true, you’ll need Basic Auth even for static pages.