Content Lifecycle

Every content entry in InlineCMS has a status: draft, published, or archived.

Statuses

Status	Visible to visitors	Visible to editors
draft	No	Yes
published	Yes	Yes
archived	No	No

Editing flow

Editor makes a change
  → Content saved as draft
    → Editor clicks Publish
      → Status changes to published
        → CDN cache invalidated
          → Visitors see the new content

Draft vs Publish

• Save draft persists changes without making them visible to visitors. Editors can see drafts when authenticated.
• Publish promotes all drafts on the current page to published status and triggers CDN cache invalidation.

Content history

Every publish creates an immutable history record. The content_history table stores:

• The published field values
• Who published them
• When they were published

This provides a full audit trail of every content change.

CDN integration

When content is published, InlineCMS sends a cache invalidation request to your configured CDN webhook. This ensures visitors see updated content immediately.

• Editors always bypass the CDN and fetch directly from the API
• Visitors are served from the CDN edge (fast) with API as the origin

See CDN & Caching for configuration details.