Create and publish content

An entry contains values defined by an API schema. Owners and editors can create, edit, and delete entries. Viewers can only read them.

Create an entry

1. Select the workspace name in the header to switch to the workspace you want.
2. Select the API from the row of API names at the top of the screen.
3. For a list API, select "New content". For an object API, select "Create content" or "Edit content".
4. Fill in the fields, such as the title and body.
5. Select "Save" and check that "Saved" appears.

API names sit in one row, which scrolls sideways if it does not fit the screen. Open Media and workspace settings from the workspace name menu in the header.

Changes are not saved as you type. Wait for image uploads and saving to finish. If saving fails, read the error and try again.

Write the body

Rich text fields support headings, links, and other formatting. When you insert an image, add alt text if it needs it.

HTML written in a plain text field does not turn into rich text. If you need rich text, ask an owner to change the field type.

Enter starts a new paragraph, and Shift+Enter adds a line break inside a paragraph. The editor adds space between paragraphs, while line breaks inside a paragraph use normal line spacing. The delivered HTML uses separate p and br elements, so you can set paragraph spacing with CSS on your site too. Typing **bold** or *italic* right after Japanese text also converts it to bold or italic.

Insert a table

Rich text fields can contain tables.

1. Place the cursor where you want to place the table.
2. Select "+" in the insert bar that appears next to the cursor.
3. Choose "Table" from the tools that appear.

Place the cursor in a table to show controls for adding and removing rows and columns. New rows and columns are added next to the cell the cursor is in. If you delete every row and column, the table is removed from the body.

Merging cells and setting column widths are not supported. You can add a header row and add or remove rows and columns. For a complex table, split it into smaller tables or use a bulleted list instead.

When you import tables from other services, only supported markup is kept. Delivered HTML supports table, thead, tbody, tfoot, tr, th, td, and the colspan and rowspan attributes. Other tags, and settings such as column width, are lost on import.

Set publication status

Choose the status under "Settings" in the editor, then save.

Entries that are no longer delivered are left out of lists, and fetching one by ID returns 404. A status change takes effect once the save finishes.

You can also change the status without opening the entry. Open the "⋯" menu on a row in the content list and choose "Publication status". Every change asks for confirmation. Scheduling asks for a future date and time, and publishing an entry that has unpublished changes publishes those changes too.

Edit a published entry

For a published entry, open the "▾" menu to the right of "Save" and choose "Save as draft". This is the list-format editor; in object format, a "Save as draft" button appears while you edit. Your changes are saved as unpublished, and your site and the standard delivery API keep serving the published content. The option does not appear for entries that are not live, such as drafts or scheduled entries.

After saving, the editor shows when the draft was saved, and you can pick up from those unpublished changes next time. The content list and language switcher mark the entry "Unpublished changes". "View diff" compares the published content with your saved unpublished changes, field by field. Japanese text is compared character by character, and rich text is compared as Markdown. Input you have not saved yet is not included in the diff.

Select "Save" to publish. If you have saved unpublished changes, you can select it without editing anything more. The changes go live at that point. Select "Discard changes" to go back to the published content. A confirmation dialog appears, and any unsaved edits are lost. Saving or discarding unpublished changes does not send a webhook. The usual update notification is sent when you publish.

Saved unpublished changes are deleted if you change the status to draft or unpublished, restore a version, or overwrite the entry with an import. Deleting a language version also deletes its unpublished changes. Changing the status affects delivery as well: an entry saved as a draft is no longer available from the standard delivery API.

If your site uses caching or static generation, saving in the dashboard may not update the site right away. Use a webhook to trigger revalidation or a rebuild.

Preview saved content

Once you save an entry, you can see how it looks on your real site with Draft preview. The preview shows saved content, so save first if you want to see unsaved input.

To publish at a set time, see Scheduled publishing. To go back to earlier content, see Version history.

Delete an entry

Delete an entry you no longer need from "⋯" → "Delete" on its row in the content list. You can also select several rows with the checkboxes and delete them together. A deleted entry cannot be fetched from the delivery API or preview, and its version history is deleted too.

Before you delete, check whether other pages or entries reference it. Make your site show a 404 page or similar when an entry cannot be fetched. Content fetching has an example.

Create or edit a language version

In an API with multilingual content enabled, the list shows the status of each language version. Open an entry and switch "Language to edit". In object format, switch the language on the content screen. A language without a version shows "Not created". Select "Copy from main language" to copy the current main-language values as a draft. Then translate and save. If you change the main language later, the translated version is not updated.

Each language version has its own values and publish status. You can publish an additional language while the main language is still a draft, and setting one language back to draft does not affect the others. The entry ID and schema are shared, so you cannot change the ID from a language version. Scheduled publishing, preview, and version history also work per language.

"Delete this language version" deletes the content and history of that additional language. The main language and the other language versions remain. If you delete the main-language entry itself, all of its language versions are deleted.