Record drafts
Editing a record does not change the site right away. Changes collect in a draft, you check them on the preview host, and visitors keep seeing the published version until you press Publish.
Turning drafts on
Drafts are a per-type setting. The type page has a “Drafts” card with a toggle. While it is off, a record saves straight into its published version.
Two types cannot use drafts: media and types with a password (bcrypt) field. Their records save immediately, and their row in a related-record card says “Saved immediately”.
Statuses
The status next to the record title describes the SAVED state:
| Status | Meaning |
|---|---|
| Published | the site has the current version, no draft exists |
| Draft | a saved draft is waiting to be published |
| Not published | a new record that has never been on the site |
Typing does not change the status. Unsaved edits show up as a grey “Unsaved changes” pill, and every touched field gets a “changed” badge.
Buttons
Only the actions that have work to do stay under the form:
- Save draft writes the current values to the draft. A draft may be incomplete; required fields are checked on publish.
- Publish moves the values into the published record. Unsaved edits are saved to the draft first.
- Reset edits restores the last saved values. It appears while there is something to reset.
An existing record with no edits and no draft shows neither Save draft nor Publish.
Cancelling a draft
The “Cancel changes” button in the yellow banner deletes the saved draft and leaves the published record untouched. In a related-record card the same button deletes that record’s draft.
When there is no draft and you cancel local edits, the form restores the saved values in place: no reload, no collapsed cards.
Related records
Related records keep their own drafts. Page blocks, the SEO card, list items: each card has its own Save draft and Publish pair in its expanded view. The parent record never saves them automatically.
On publish the admin panel checks those cards. Unsaved child edits bring a prompt to save them or continue without them; child drafts can be published together with the parent or left alone.
Each related row shows its own state: Published, Draft, Unsaved changes, or Saved immediately.
Checking before publish
The preview host (preview-<subdomain>.dynapi.ru) runs drafts; the main
address serves published data only. Until a draft is published, visitors see
the previous version and the new one is visible on the preview host.
Concurrent editing
If another tab saves the draft, the editor offers to reload the newer version instead of overwriting it silently. If the published record changed after the draft was started, publishing asks what to do: stay, load the live version, or publish with overwrite.
What next
- Data types and fields — which fields exist and how they work.
- Media — uploading files and linking them from records.
- Roles and access — who can save drafts and publish.