In Delta, an entry is any piece of content: a page, a post, or an item of a public custom post type. The agent manages all three the same way: create, update, publish, delete.
Every entry renders in one of two modes.
Native content
The entry’s text lives in the regular WordPress editor, blocks included, and a Delta template supplies the layout around it. This is the mode for posts and for any content your clients edit themselves.
What the block editor shows
The block editor is a writing space, not a preview. It shows your text in the site’s fonts and colours, so a heading looks like a heading and a link looks like a link. It does not show the layout. The layout comes from the single template, and every post gets it on the site.
Write a post the way you always did: new post, write, publish. Or hand the agent a finished document and it imports the text as blocks. The post opens in the block editor afterwards like any other.
“Import hardanger.md as a new post in Field notes, draft.”
Delta HTML
The agent designs the whole page: its own HTML, scoped CSS, and optional JavaScript, stored with the entry. This markup replaces the template’s body; the site header and footer remain unless you hide them. This is the mode for designed pages: homepages, landing pages, service pages.
This applies to posts as well as pages. A post the agent writes in HTML is edited by the agent from then on; the block editor shows a notice instead of the body. If you want to keep editing a post yourself, keep it in native content.
Switching between modes
An entry can switch between modes. When Delta HTML is on, the native content is preserved in the background: Delta refuses edits to it until the overlay is removed, and restores it when you switch back. A designed page does not lose the text it had before.
To check a specific page, ask the agent: “Does the About page use Delta HTML or native content?”
Entries of a content type
An entry of a content type carries custom fields and terms as well as its title and text. The agent sets all of them in the same request that writes the text. Each article on this site is an example: a doc entry with a summary field, an order field, a category, and a product term, written in one call.
“Add a course called Typography 101: level Beginner, topics Type and Layout, with the badge image from the Media Library.”
A term that does not exist yet is created on the way. A featured image comes from a file already in the Media Library, so upload it first, or ask the agent to. An empty field renders as nothing in the design, and the page still works.
When an SEO plugin is active, the search title and description go in the same request too. See SEO.
Many entries at once
The agent can change the status of up to fifty entries in one request: publish, draft, private, pending, or trash. Draft is the way to take an entry off the site without removing it.
“Set all the 2024 case studies to draft.”
What is not an entry
Some post types are outside the entry abilities, and the split is deliberate. WooCommerce products, orders, and coupons have their own abilities, because each has rules an ordinary entry does not. Form definitions belong to the form plugin. The internal records of a content plugin, such as a field group, are not content. The agent uses the matching abilities for each of these, or leaves them to the plugin.
For developers
Entry writes are delta/create-entry and delta/update-page. Custom fields go in meta, keyed by field name or meta key. Terms go in terms, one array per taxonomy, by slug or name. The featured image is featuredImage, an attachment ID. delta/bulk-update-entries takes up to 50 ids and one status, and returns updated[] and failed[]. seo on both writes takes title, description, canonical, noindex, nofollow, socialTitle, socialDescription and socialImage. A designed entry’s own excerpt shows in archives, feeds, the REST API and the excerpt placeholder.