Built for Ghost, honest about the limits
Everything you need to design, validate, export and deploy a professional Ghost theme — and a clear account of where the boundaries are.
Global components
Build a header, post card, or newsletter form once and reuse it everywhere. Components compile to Ghost Handlebars partials, so the exported theme stays DRY and readable.
- Master + instances with props, slots and variants
- Editing a master shows how many instances change across which templates before you save
- Pin an instance to a version, or detach it when you need a one-off
The boundary: Cross-project copies become independent — they do not stay linked to the source master.
Comments
Leave feedback exactly where it belongs. Comments anchor to a stable element, component, or code line and survive layout moves, so a thread never loses its target.
- Threads anchored to elements, components, design tokens, or a specific code line
- Open / in-progress / resolved / reopened statuses
- Code-line comments are available on every plan
The boundary: The central comments dashboard is a Team-plan surface; element threads are available across plans.
History, version compare & rollback
Every change is recorded. Name a version when you hit a milestone, compare two versions as a diff, and restore an earlier state without losing the trail.
- Named versions with notes and change summaries
- Compare any two versions and restore in a click
- A single-writer lock keeps history linear — no merge conflicts to untangle
The boundary: History retention depends on your plan; older autosaves age out by a documented retention window.
Ghost compatibility
Inflozo knows which Ghost features your site supports. It validates against the Ghost version you target and surfaces compatibility issues before they reach production.
- GScan runs against your selected Ghost target version
- A compatibility panel flags unsupported or partially-supported features
- Problems Panel catches broken bindings and missing required helpers
The boundary: Compatibility is validated against your connected Ghost site — not assumed. Some features depend on your Ghost version and site settings.
Export
Export a developer-grade Ghost theme you fully own: semantic Handlebars partials, CSS custom properties, a README, and a valid package.json — no framework runtime, no random class names.
- Readable BEM-style classes and design-token CSS variables
- README, CHANGELOG and a manifest in every export
- routes.yaml is provided as a standalone file with manual-upload instructions
The boundary: Ghost has no stable API to upload routes.yaml, so routes are always a manual step — Inflozo never deploys them for you.
Deploy safety
Deploy to Ghost Admin in one click, with guardrails. The first deploy to a connected site is gated behind a backup confirmation, every deploy validates first, and the artifact is stored so you can roll back.
- Backup-gated first deploy; nothing deploys or activates automatically
- GScan runs before upload; the previous theme stays reactivatable
- Every deploy is logged with a job ID
The boundary: “Safe” means a backup gate, validation, and rollback — not a guarantee that a deploy can never break a live site.
Re-import boundaries
You can bring an Inflozo-generated theme back into the builder — but only when it is still genuinely Inflozo-generated. The manifest, schema, and checksums are the source of truth.
- Only Inflozo-exported themes with a valid manifest and matching checksums re-import
- Arbitrary or third-party Ghost themes cannot be imported
- Identity is verified by manifest + checksum before anything is read
The boundary: Once you edit theme files locally outside Inflozo, the checksums no longer match and the theme can no longer be re-imported. This is by design — re-import is not a lossless round-trip of arbitrary hand edits.