Skip to content
delta

v0.3.0

Released 10 October 2026

All releases

New features

  • Each integration now works through its plugin's own tools instead of copying them, so what you set in the plugin's own screens survives Delta's changes
  • Your agent can use the plugins' own tools through Delta: WooCommerce, WPForms, Secure Custom Fields, Meta Box, Ninja Forms, Fluent Forms and Gravity Forms
  • Delta adds its own tools for Contact Form 7, ACF, Custom Post Type UI, Pods, Meta Box and Forminator, which have none of their own
  • When your agent updates a form, content type or field group, it keeps fields you added in the plugin's editor. It removes them only when you ask it to replace everything
  • WooCommerce's own cart, checkout, mini cart and order confirmation blocks can be used in templates
  • Templates can show more WooCommerce details: cart and order rows, account pages added by extensions, and brand archives
  • Field maps now read values through ACF, Secure Custom Fields, Meta Box and Pods, and cover nearly every field type, including true/false, link, file, location, user and group
  • Field maps also cover ACF options pages, Meta Box settings pages, Pods settings and MB Relationships
  • Templates can loop over galleries, lists, repeaters and flexible content
  • Templates can show a block only when a field has a value
  • Your agent can save repeater and flexible content rows when it creates or updates a page
  • Header and footer templates can use loops
  • Front panel: a panel on your live site, opened from Delta in the admin bar or with ⌘⇧E. Visitors never load it
  • In the Front panel, click anything to read its HTML, CSS and JS, edit text in place, and reorder sections
  • Front panel tabs for the page's links, the design system and Memory
  • Sketchbook: boards where your agent tries ideas with the site's styles. The site does not change until you say so
  • Boards can be copied, renamed, shared with a read-only link, and turned into a draft page. Any change can be undone
  • Update website styles applies a board's style changes to the site. A snapshot is taken first, and Undo takes it back
  • Delta can be translated, and ships in Spanish, Japanese, German, French, Brazilian Portuguese, Italian, Dutch, Russian, Polish, Turkish and Simplified Chinese
  • Your agent can move a site to Delta's current starter design system and keep what the site changed. A snapshot is taken first
  • Your agent now sees each form and field plugin's tools, the names your stylesheet adds, and which starter design system the site uses

Improvements

  • Pages load faster: field maps are read only when a page uses them
  • A field whose name WordPress reserves keeps working: it gets the post type in front of its name
  • Permission errors say which user and which permission is missing
  • Each integration brings its own skills and rules
  • Long text fields keep their line breaks. Add _raw to the field name for the old output
  • Field maps made by an earlier version stay as they are until you ask your agent to upgrade them
  • Field maps sync when you save a post type, taxonomy or field group in ACF, Secure Custom Fields or Custom Post Type UI
  • Open in Delta Editor is now Open in Delta Front Panel. The Delta Editor is under Delta › Editor
  • The Delta admin has one sidebar item per tab: Agent, Appearance, Site, Editor and Integrations. Page addresses stay the same
  • Reset to defaults is gone from the Abilities page. All on does the same
  • With Soft Navigation on, pages with a contact form load fully, so the form's scripts run
  • Creating or changing forms needs Fluent Forms 6.2.5 or Ninja Forms 3.15. Older versions still show forms
  • Contact form field types follow each plugin and edition. For example, Fluent Forms Free has no phone field and Ninja Forms has no URL field
  • Delta's WooCommerce tools now go through WooCommerce itself, with its own checks and permissions
  • Custom Post Type UI's own checks now apply to Delta's changes, such as reserved names and slugs in use
  • Removed: the UI Editor, the chat editor inside the theme. Its stored AI keys, model settings and chat sessions are deleted when you update
  • Deprecated: Delta's own product and order tools. They keep working until 0.4.0, and your agent should use WooCommerce's own tools
  • For developers: new filters 21press_delta_loop_names, 21press_delta_render_source, 21press_delta_front_panel_tabs and 21press_delta_context_sources. The UI Editor hooks and the script handles of the six contact form shims are removed, and the editor's PHP helpers stay as stubs until 0.4.0

Fixes

  • Updating an ACF, Meta Box, Pods, Custom Post Type UI or Gravity Forms item no longer resets labels, menu position or permalink settings made in the plugin
  • Pods post types and taxonomies get the permalink base and REST API support you asked for
  • Form updates no longer publish a draft form, and Ninja Forms keeps its field IDs, layouts and conditional logic
  • Contact Form 7 forms send from an address on your site's domain, and Contact Form 7's own warnings are shown
  • Ninja Forms forms show their fields when the Layout & Styles add-on is active
  • Ninja Forms keeps a new recipient and subject when fields change in the same update
  • A new post type or taxonomy can no longer take a slug that is in use, such as post, page, product or category
  • Select field options can have a value and a label. Unknown settings now give a warning
  • No more false link warning for a taxonomy placed under its post type, such as books/genre
  • Updating a Meta Box or Pods field group by its ID now changes the right group
  • Saving a Pods template or page under an existing name updates it instead of making a copy
  • Meta Box fields for users and settings pages no longer show up as post field maps
  • Loop item cards are styled again on pages with their own design
  • WooCommerce → Status no longer lists outdated Delta overrides
  • Security: the plugin tools check permissions properly. Since 0.1.0, reading a plugin's details could activate it
  • A refused plugin install says why, for example a plugin that needs a newer PHP
  • A site set back to the starter design tokens is recognised as using them again