For developers

How SiteHome decides what is editable

One rule for every website, the closed-field reasons and what that means per CMS.

SiteHome applies field policy inside each CMS adapter, without per-website or content-type exceptions. The general rule below applies to Sanity and legacy connections; new official Payload MCP connections follow the server-owned validation policy described under Payload.

The rule

• A field without a rule of the website's own is editable. SiteHome applies the standard rules the CMS describes: required, minimum and maximum length or value, link schemes and the choices a field offers.
• A field with a rule of the website's own (code SiteHome cannot run), or one that is shown or read-only only under a condition, stays closed, together with the block it is in, because such rules often depend on the fields beside them.
• Content SiteHome cannot edit yet is shown as closed, never changed.

Each closed field carries one neutral reason, shown in plain language in the app:

• own-rule: the website checks this field with a rule of its own.
• conditional: the field only appears under a condition.
• read-only: the field is read-only in the CMS.
• address: the address (slug) of an existing item, so links keep working.
• page-builder: the page is laid out with a page builder.
• unsupported: SiteHome cannot edit this kind of field yet.

Per CMS

• Sanity: a custom validation function is a rule of its own; hidden or readOnly as a function is a condition. Built-in rules (required, max, uri, regex) are applied. References to other documents are editable: one reference as a choice, an array of references (such as a menu) as an ordered list, from the published documents of the referenced types. A reference to a draft or with a rule of its own stays closed.
• Payload: new official MCP connections use authoritative extension metadata for scalar controls, supported Lexical rich text, single images and single/multiple/polymorphic relationships. Payload owns custom validation, hooks and access; their presence does not close otherwise supported fields. SiteHome does not reproduce conditional admin presentation. Unknown custom controls, arbitrary arrays, galleries, nested groups and localized editing remain outside scope. Existing legacy bindings keep their original policy.
• WordPress: title, excerpt, block content, the featured image, categories, tags and custom taxonomies are editable. With plugin 0.4.0, also ACF fields of the types text, text area, number, email, URL, select, checkbox, radio, button group, true/false, date and image. An ACF field with conditional logic, a read-only or disabled setting, or an acf/validate_value or acf/update_value filter for that field stays closed; repeaters, flexible content, groups and relationships stay closed. Classic-editor content and page-builder layouts are left alone.

After the website's fields change

When a developer changes the website's fields, an administrator taps Velden opnieuw inlezen (Read fields again) in the website's options. Concepts made for the old fields expire; publishing stays as it was.