Create and publish content

An entry is a specific piece of content: the event "Open House", the post "Welcome, families". Each entry belongs to a content type and has one value per field.

The life of an entry

draft ──publish──▶ published ──edit──▶ unpublished changes ──publish──▶ published

any state ──archive──▶ archived ──unarchive──▶ draft

• Everything an agent creates starts as a draft. Publishing is a separate step, with its own permission.
• Saving never publishes. Your site keeps showing the published version until you publish again.

Create an entry

In your site, go to Content → New entry and pick the type. The form builds itself from the type's fields:

If the type is a singleton, it has a single entry: Pluma won't let you create a second one.

Publish

Publishing validates the whole entry:

• Required fields have a value.
• Each value is the right type (a number is a number, a date is a date).
• Slugs are unique within the type.
• References point to entries that exist and are of an allowed type.

If something fails, it isn't published and you see which field to fix. Saving a draft only checks types, not required fields: you can save halfway.

Empty text is an empty field. Sending "" (or only spaces) leaves the field with no value, and the API doesn't return it. If your site needs "", use that as the default when reading.

Versions

Every time you save, a new version is created: number, who (person or agent) and when. Nothing is overwritten.

• You can restore any version. Restoring creates a new version with that data; it doesn't delete the ones in between.
• The published version is marked. If you restore an old one, it stays as unpublished changes until you publish.

Possible errors