Lohnt sich dein eigenes WordPress?

Build a self-hosted personal CMS for a single author. Empty folder, no cloud services, no telemetry, no accounts beyond one local admin.

Stack, non-negotiable:
- Node 22 with TypeScript, Fastify for the server
- SQLite via better-sqlite3, single file at ./data/cms.db, schema created on first boot
- Server-rendered HTML with Eta templates, no client framework
- Plain CSS in one stylesheet, readable typography, dark mode via prefers-color-scheme
- markdown-it for rendering, with a syntax highlight pass and HTML sanitization on output

Features in scope:
- Posts and standalone pages: title, slug, markdown body, excerpt, tags, status (draft, scheduled, published), publish timestamp
- Admin at /admin behind cookie session auth: one admin user, password hash from ADMIN_PASSWORD_HASH in .env, argon2 or bcrypt
- Admin editor: textarea with live preview pane, save as draft, publish, unpublish, delete with confirm
- Media upload to ./data/uploads, images resized to a max width with sharp, served with long cache headers, insert-into-post button that pastes markdown
- Public routes: home with paginated post list, /posts/:slug, /:pageSlug, /tags/:tag
- /feed.xml RSS 2.0, /sitemap.xml, per-post OpenGraph and Twitter card meta tags
- Full text search over posts using SQLite FTS5
- Scheduled posts appear automatically based on publish timestamp, checked on request, no cron needed
- Import script that reads a folder of markdown files with YAML frontmatter and inserts them, so a WordPress export converted to markdown can be loaded
- npm run backup that copies the db and uploads into a timestamped tarball

Explicitly out of scope: plugins, themes, comments, multi-user roles, multisite, e-commerce, a block editor, and any hosted API.

Secrets in .env with a committed .env.example. Ship a README with setup, the password hash generator command, and how to run it behind Caddy with TLS. Include a seed script with three sample posts and a page so the site is not empty on first run.