You spent an hour styling a post with custom CSS classes, embedded code blocks, and some modern layout tricks. You hit publish, select your subscribers, and... nothing arrives. Or worse — everything arrives, but it's mangled. A growing number of Ghost users are hitting exactly this wall, and the

You've cloned the Source or Casper theme, opened up assets/screen.css, made your changes — and nothing shows up in the browser. You restart Ghost. You clear the cache. Still nothing. This is probably the most common Ghost theme development frustration, and it happens because Ghost's

Quick answer: ghst is Ghost's official new AI-native CLI tool (developer beta, 2026) that lets you manage your Ghost publication from the terminal — or hand control to an LLM like Claude or Codex. It handles posts, members, themes, newsletters, tiers, and social publishing, all without opening the admin

Quick answer: When a Ghost newsletter sends as a test but fails for actual subscribers, the most common culprit is modern CSS that Juice (Ghost's CSS inliner) can't process — especially the CSS nesting & selector. Strip modern CSS from posts you want to email, and the

You're building a headless Ghost site. You've got the Content API working, posts loading beautifully, and then you hit a wall: where do comments go? This exact question popped up on the Ghost forum in March 2026: a developer working on a headless Ghost project couldn&

Quick answer: Ghost CMS connects to Bluesky in two ways. Ghost 6+ has a built-in Social Web (ActivityPub) toggle that bridges your posts to Bluesky via Bridgy Fed — readers can follow your site on Bluesky without you having a separate account. For direct, fully-automated posting, use a webhook + the ghost-bluesky-integration

You mark a post as "featured" in Ghost. You wait. You refresh your homepage. Nothing changes. The post sits in the same chronological list as everything else — no spotlight, no special placement, no visual cue. Sound familiar? This is one of the most common points of confusion on

Quick answer: Running Ghost in rootless Docker means the Docker daemon (and your containers) run as a regular user, not root. You configure user namespaces, bind ports above 1024, and adjust volume ownership — then use a standard Docker Compose file. Ghost runs fine; the main gotchas are port binding and

Quick answer: Ghost CMS has a native commenting system (available since Ghost 5.0) that requires members to sign in. To enable it: go to Settings → Membership → Access and turn commenting on. For custom themes, add {{comments}} to your post.hbs template. Third-party options like Disqus or Hyvor Talk work