-
Notifications
You must be signed in to change notification settings - Fork 0
Current Scope
This describes the launch candidate. Destination WordPress capabilities and advertised REST routes remain authoritative.
| Area | Focused workflow | Boundary |
|---|---|---|
| Content | Search, paginate, save filters, create/edit source, review public/scheduled writes, compare/recover revisions, trash | Posts/pages plus editable, viewable REST-enabled types supporting title/editor and a standard writable schema; no visual block editor or featured-image picker |
| Comments | Search/paginate and moderate | Not a complete discussion editor |
| Media | Search/paginate and edit attachment metadata | No binary upload workflow |
| Users | Search/paginate, create users, edit supported fields/roles | Destination permission checks apply |
| Plugins | Inspect, install from WordPress.org, activate/deactivate | No universal update/rollback system |
| Settings | Site identity, timezone, date/time, week start | Only exposed Core settings |
| Design | Read block-theme resources | Advanced writes through Explorer, not the Site Editor |
| Explorer | Advertised routes and JSON methods; confirm mutations | Size limits; no binary file transfer or new endpoints |
| Agency | Client, tags, plan, notes, favorites | Private per hub user |
| Fleet | Sites, Inbox, indexed Search, Workspaces, Activity, Support | Cached summaries, not continuous monitoring |
Content/media/comments/users load one page of 12 records. Full post/page source loads only when opened. Table sorting applies to the current page; search and pagination query WordPress.
Saved work views store only filter configuration, at most twelve per user/site. This-week filters use the destination's week start and named or fixed-offset timezone. Revision history loads twelve rows per page and selected source on demand; recovery loads title/content/supported excerpt into the editor, preserving status, date, slug, and the original conflict fingerprint. Public or scheduled writes require a ten-minute review bound to the exact fields, user, hub, and connection. This is not autosave or atomic rollback; Core still has no compare-and-swap write.
Status becomes due after five minutes, metadata/search after one hour, and Site Health after six hours. WP-Cron is traffic-driven. Scheduled passes have an approximately 40-second budget and resume later; failures back off up to six hours. Manual checks bypass cadence and cost more.
Incomplete health checks retain last-known findings, update only verified partial results, and show a stale/unverified warning. Attempt time is separate from last complete success; failed health checks become eligible to retry after five minutes. They do not erase findings or reset the successful-health timestamp.
Search uses an encrypted incremental index on the hub, not a live request to every site per query. Workspaces open up to eight sites; larger groups remain available in Sites.
No Fleet target agent/endpoints, OAuth server, hosted control plane, classic fallback, backups, malware scanning, uptime service, or functionality without an API is included. See Load testing and Launch checklist.