Why typress

The author of typress had a personal site hijacked twice in a row through WordPress vulnerabilities. The second time, the entire site had been silently replaced with a Chinese e-commerce landing page selling Pokémon cards — they only noticed when Google sent a manual-action notice about unnatural links and undisclosed sponsored content.

The site moved to a static site generator after that. The attack surface dropped to roughly zero; so did the convenience of a dynamic CMS.

typress is an attempt to win that convenience back, on the condition that the WordPress-class vulnerability patterns can't follow it.

How to read these docs

Reading top to bottom from the side nav takes you from a fresh download to a hardened production setup. Each section is also self-contained, so jumping straight to a topic is fine.

• Getting started — install, first boot, admin account
• Configuration — environment variables, data directory, master key
• Deployment — systemd, nginx, Let's Encrypt, upgrading
• Authoring — block editor, media, layouts
• Extending — themes and plugins (build, sign, install)
• API — public REST, CLI, security model

Who it's for

Indie developers and small editorial teams comfortable with a single Linux box, vaguely aware of TLS / DNS / systemd. Some Bun + TypeScript helps when you start writing themes or plugins, but isn't required to run the thing.