Ghost's draft preview feature relies on a stateless, token-signed endpoint that validates short-lived tokens, fetches drafts via the Admin API, and renders them with the live theme—keeping unpublished content secure.
Learn how to architect a production-ready Ghost instance, from choosing MySQL 8 over SQLite to establishing secure data boundaries and operational health checks.
Learn how to create a Ghost Custom Integration, generate an Admin API key, set up a webhook, and verify real‑time event delivery. Follow this step‑by‑step guide to safely connect Ghost to third‑party services.
When Ghost’s sign‑in links, staff invites, and member emails stop arriving, the site is still up. This guide walks through the most common causes, ordered checks, and fixes—complete with config snippets, log‑examining commands, and escalation criteria.
Learn how to decouple your frontend from the Ghost CMS using the Content API to build high-performance, custom sites with frameworks like Next.js or Nuxt.
Step-by-step guide to enable Ghost CMS's built-in AMP support, validate generated pages, customize the AMP template, handle common validation failures, and roll back if needed.
Ghost v5 exposes a configurable timeout for inbound HTTP request parsing and a gracefulShutdownTimeout for process termination on SIGTERM/SIGINT. The documented settings affect server close behavior, but the interaction with long-running Admin API operations and outbound webhook deliveries is not fully defined. The Admin API does not expose a standard AbortC
Goal Determine which image delivery strategy better preserves page load speed on a 3 Mbps mobile connection while keeping Ghost’s CPU usage and image quality consistent. Constraints & Uncertainty Ghost’s built‑in Sharp pipeline resizes and compresses on‑the‑fly, but the quality setting in config.production.json is not applied to cached images unless the