Research sources

Initial primary sources informing the feasibility assessment. Last reviewed 2026-08-22.

WordPress application and data APIs

• REST API Handbook — describes using WordPress data to build new admin and front-end experiences.
• REST API endpoint reference — core entities including posts, revisions, media, templates, navigation, and blocks.
• REST API authentication — cookie authentication, nonces, capabilities, and application passwords.
• WordPress Core Data — entity records, autosaves, revisions, permissions, undo, and persistence actions.
• Heartbeat API — near-real-time polling that can participate in editor presence and locking behavior.

Editor and rendering platform

• `@wordpress/block-editor` — public components for creating a custom block editor.
• Building a custom block editor — example use of BlockEditorProvider and a custom application shell.
• `parse_blocks()` — parses serialized block content into a block tree.
• `render_block` filter — filters each rendered block with access to parsed block data.
• Rendered Blocks REST endpoint — authoritative server rendering for registered dynamic blocks.
• Block API versions — iframe-editor behavior and compatibility requirements.

Structured content and constrained design

• Block Bindings — connects block attributes to metadata, post/term data, and pattern overrides.
• Block Locking API — move, remove, edit, and content-only restrictions.
• Introduction to Patterns — synced and unsynced pattern behavior.
• Synced Pattern overrides — editable instance content while preserving synchronized design.
• `theme.json` global settings and styles — design tokens, control restrictions, and block style variations.
• Block stylesheets — per-block theme styles.

Current Core direction

• WordPress 7.0 Field Guide — modernized admin, pattern editing, expanded contentOnly, PHP-only block registration, DataViews/DataForm, and Block Bindings changes.
• WordPress 7.0 “Armstrong” — release overview.
• DataViews and DataForm in WordPress 7.0 — current declarative data UI capabilities.
• Client-Side Abilities API in WordPress 7.0 — discoverable, annotated actions that may inform future agent integration.

Related product experiment

• OpenStation repository — demonstrates an opt-in WordPress admin shell built as a plugin using public hooks, native windows, iframes, REST endpoints, and a same-origin message bridge.
• OpenStation plugin page — user-facing positioning and current feature overview.

Research caveat

Core capabilities demonstrate feasibility; they do not determine the WPS UX. Internal or unstable Gutenberg APIs should not become accidental foundations without explicit compatibility testing and a version strategy.