---
description: Understand Studio content types, saved documents, autosaves, revisions, HTML editing, and body previews.
---

# Content

Studio stores authored content in D1. Published documents become inputs to the
next [Preview Data export](../publishing/index.md); the public website is
updated by its separate build and deployment.

## Content Model

| Area | Role |
| --- | --- |
| Posts | Articles with a public Author, categories, tags, and publication state |
| Pages | Standalone or hierarchical content, including a selected front page |
| Authors | Public bylines; optionally linked to a Studio account |
| Categories and Tags | Content organization used by the public theme |
| Media | Metadata and references to managed R2 objects or external files |
| Menus and Widgets | Saved navigation and content blocks rendered by the theme |

A Studio account controls access; a public Author identifies a byline. An
Author-role account needs a linked public Author before it can manage Posts.
See [Roles & Capabilities](../access-control/roles-and-capabilities/index.md).

Site settings determine public URLs, the homepage, output, branding,
localization, and custom code. Theme templates determine how the exported
data is presented; see the
[Preview Data reference](https://zeropress.dev/reference/preview-data/).

## Saved Content, Autosaves, and Revisions

The saved document is the canonical content. Autosaves preserve ongoing work
separately and can be restored for review. Saved revisions retain earlier
document snapshots. Restoring a snapshot is an explicit action; simply opening
history does not change the public content.

Writes check the document's revision. If another session changed the document,
Studio reports a conflict rather than silently replacing it. Review the latest
version before saving again. Save current edits before preparing a public-site
export; preparation does not select an editor's unsaved or autosaved draft.

## Document Formats and HTML Editing

Posts and Pages support HTML, Markdown, and plain text. HTML offers source
editing and SunEditor visual editing. Converting to the visual editor can
normalize markup or remove unsupported structure. Studio shows the proposed
HTML changes when conversion needs review; cancelling preserves the source.
Switching to HTML source exposes the current HTML without another conversion.

Keep source mode when the original markup needs to be preserved. A successful
WordPress import can retain HTML that needs source editing; visual-editor
compatibility is separate from import success.

## Preview and Permalink

**Preview** renders the current title and body, including unsaved changes,
using the same content renderer as ZeroPress builds. Desktop and Mobile change
the preview width. The neutral stylesheet supports tables and highlighted code
but does not reproduce the site's theme, menus, widgets, or custom code.

Scripts and external embeds do not execute. Select a link to inspect its
address and target; an embed card shows its title and source address. These
values reflect the renderer's output. Relative media URLs use the saved
permalink, or the site URL for new documents.

**Permalink** opens a saved, published document's public URL in a new tab.
A saved draft has a non-clickable planned permalink. The address updates after
saving a slug or status change; it does not prove the public deployment exists.

## Publication State and Trash

The All tab includes Draft and Published documents. Trash is a separate tab,
excluded from All counts and search results. Status, search, and applicable
Author filters are represented in the URL.

Restore returns a trashed document to Draft. Permanent deletion is available
from Trash and still checks revision, ownership, and references. The selected
front page must remain published; Pages with children cannot be trashed or
deleted until those references are resolved.

Bulk actions apply to the selected documents on the current page and report
individual results. A conflict or protected Page can leave part of a selection
unchanged. Review those results before retrying.

For body search and index availability, see [Content Search](search/index.md).
