Understand the content lifecycle

States

• Draft — private and editable
• Scheduled — private until its publication time arrives
• Published — available to public readers and APIs
• Archived — removed from public listings restored is not a separate stored status. An archived post can be returned to draft, scheduled, or published through the editor or management API.

Revisions and slugs

Prosewire creates revisions before destructive content changes. Slugs are unique within a blog, and when a published slug changes, the old public URL redirects to the new canonical URL.

Revision snapshots retain the actor and version for auditability. The dashboard can inspect and restore them. Restore is also available through the management API, SDK, CLI, and MCP. Prosewire saves the current post as a new revision before a restore, so the operation remains reversible.

New snapshots include category relationships. Older snapshots created before category capture leave the post’s current categories unchanged when restored. Changing an archived post back to a working status does not delete its revision history.

Managed cover images

Editors can keep using an external cover URL or choose a managed media asset. A managed upload is reserved against the publication quota, sent directly to object storage with a short-lived signed request, then completed through Prosewire. Completion validates the stored size, detects the real image MIME type, rejects unsupported or animated inputs, removes metadata, and generates original, large, and thumbnail variants. Posts store both the asset reference and the large CDN URL so every reader and framework integration keeps the same public post contract.

The content library shows direct post references. An asset cannot be deleted while a current post uses it. Deletion permanently removes its stored objects and active library record. Revision snapshots can retain an old asset identifier; restoring such a revision clears the managed reference if that asset is no longer ready.

Portable exports

The posts screen provides a versioned JSON export containing publication metadata, authors, categories, snippets, redirects, media metadata and references, full posts, and revision snapshots. CSV contains post fields plus author, category, and managed cover identifiers for spreadsheet interoperability. The separate media ZIP contains the sanitized original for every ready asset and a checksum manifest. Prosewire does not currently provide an import workflow, so test your own restore process before relying on exports as a backup.

Discovery follows publication

Search, RSS, sitemap, related-post, and structured-data surfaces follow the same public visibility rule: content must be published and its publication time must have arrived.