Kindly EditDocumentationTry the editor

Services and deployment boundaries

How the WordPress plugin, help service, update service, account portal, and browser demo fit together.

Components#

Component Responsibility Primary state
WordPress plugin Editing, validation, drafts, publication, and public page rendering WordPress posts, metadata, options, revisions, uploads
Help Worker Bounded contextual guidance and validated proposed actions Request context; license checks
Update Worker License checks, site activations, release manifests, package downloads D1 records and R2 package objects
Website Worker Public assets, account sessions, sandbox checkout integration, and Try routing D1 account records; static assets
Try it demo A private copy of the sample site on try.kindlyedit.com, one per visit Copy tables and files, deleted after 20 idle minutes or 4 hours

The plugin continues to render public pages when an external license service is unavailable. Opening the editor, downloading an update, asking for remote help, signing into the account portal, and making a payment are separate operations with separate failure modes.

Source scope#

The plugin release package contains the WordPress runtime. Supporting Worker source lives alongside the plugin repository or in the website project and is deployed independently. A plugin version number alone does not identify the exact deployed Worker version.

The service pages describe the inspected source snapshot. They do not claim that every service endpoint was exercised against production as part of writing the documentation. Deployment version IDs, account identifiers, secrets, and private operational records are not part of the public reference.

Deployment changes#

Treat a Worker code deployment, database migration, package publication, and plugin update as different changes. Rolling back Worker code does not restore D1 data or remove a published R2 object. A published plugin package is immutable; distribute a correction under a new version.

Failure isolation#

Check the component that owns the failed operation. A successful website response does not establish that WordPress saved a draft. A valid license response does not establish that email arrived. A successful webhook acknowledgment does not establish that an unrelated form action succeeded.

About this page

Documents Kindly Edit 0.9.16. Source: cantata-edit.php, server/help-worker/index.js, server/updates-worker/src/index.js, website/src/index.js. Theme choices and account permissions can change which controls appear.

Type a word or phrase to search the full documentation.