Plugins

WordPress and Payload plugins

What each plugin adds, downloads and versions.

SiteHome reads and publishes through each CMS's own API. Two CMSs need a small plugin for that; Sanity needs none.

WordPress plugin

Install SiteHome from WordPress.org: in WordPress, choose Plugins → Add Plugin, search for SiteHome by bkeetman, install and activate it. Requires WordPress 6.0 and PHP 7.4 or newer. WordPress handles update notices; automatic installation is optional under Plugins → Enable auto-updates. See the installation and update guide.

Without the plugin, SiteHome can connect, read and edit, but not publish. The plugin adds:

• A revision check: an update from SiteHome carries the revision it reviewed (X-SiteHome-Expected-Revision); when the item changed since, WordPress refuses it (409). Updates without that header, from the block editor or other apps, are not affected.
• Page builder detection: items laid out with Elementor, Divi, WPBakery, Beaver Builder, Oxygen or Bricks are reported, so SiteHome leaves their content alone.
• Advanced Custom Fields (0.4.0, on new items 0.5.0): ACF fields of common types can be edited; see How SiteHome decides what is editable.
• Hosts that drop the Authorization header (0.3.0): the plugin reads SiteHome's credentials from its own header and reports whether they arrived.
• Settings → SiteHome with the connection steps.

It adds no tables and makes no outgoing requests. Removing the plugin deletes the save counter it kept on items; nothing else is stored.

Changes per version:

• 0.6.0: first WordPress.org release; ACF time and date/time fields.
• 0.5.1: review fixes for WordPress.org.
• 0.5.0: ACF fields on new items.
• 0.4.0: Advanced Custom Fields.
• 0.3.0: works on hosts that drop the Authorization header.
• 0.2.0: page builder detection.
• 0.1.0: revision check and connection steps.

Payload plugin

Official @payloadcms/plugin-mcp@3.92.0 with matching Payload packages, plus the two-file SiteHome metadata/upload extension. Register sitehomeSchema and sitehomeUpload, configure explicit content/media collections and enable both custom tools on the MCP key. Payload owns access, validation and hooks. There is no atomic revision guard; a concurrent change after the final check can still be overwritten. The historical @sitehome/payload-plugin setup applies only to existing legacy bindings, which are not automatically migrated. See Connect a Payload website.

Sanity

No plugin. SiteHome reads the website's deployed schema and publishes through Sanity's Actions API with revision checks. See Connect a Sanity website.