Static publishing

When you publish, the platform renders the article once, verifies the result and only then makes it live. Readers receive that prepared page; the database and application are not involved in serving it.

• Homepage, section, tag and author pages are rebuilt automatically when a story changes — and only the pages that actually changed.
• Unpublishing removes a page and answers “410 Gone” at once.
• If a build fails, the previous version stays online and the failure is shown in the publish history.

How we check this: our automated tests count database queries on the server while requesting published pages and require zero. See Performance for what has and has not been measured.