Coverage and version notes
What this documentation covers, which release it describes, and how source coverage differs from runtime verification.
Release baseline#
The WordPress guides describe Kindly Edit 0.12.0 (November 16, 2026) and name the release where newer behavior arrived. The generated inventories and module references were extracted from 0.9.13 and have not been regenerated since. Supporting services are independently versioned source snapshots. The WordPress runtime source was compared with the downloadable release package on November 7, 2026. The shared runtime files matched. A theme, account capability, or enabled feature can change the available controls.
The walkthroughs are recorded in the Kindly Edit branded practice site on a released Kindly Edit build, and each watch page names the version it was recorded on. Footage is a local demonstration; it does not claim that every behavior is available on every installation.
Source coverage#
| Area | Coverage |
|---|---|
| Built-in block definitions | 62 individual element or section guides, including legacy presets |
| Native element Content settings | 37 registered groups and 99 top-level controls, including nested field definitions |
| REST interface | 46 route patterns with all registered methods, permission references, and argument schemas |
| WordPress Abilities | 20 abilities with complete registered input and output schemas |
| Server modules | 54 PHP module guides and 584 named function or method signatures |
| Runtime files | 168 repository runtime, service, and utility files mapped to documentation |
| Design and editing | Task guides for selection, text, media, links, layout, styles, responsive behavior, history, and publication |
| Site systems | Forms, uploads, templates, globals, dynamic content, loops, conditions, SEO, licensing, and updates |
| Developer contracts | Theme and component integration, CSS, JavaScript, PHP, native behaviors, CLI, hooks, storage, and errors |
A source-reference page explains the implementation surface; it is not a claim that every branch has been exercised in a browser. Generated inventories identify exact symbols and schemas. Task guides explain intended workflows. Recorded demonstrations show the particular actions visible in each video.
Scope boundaries#
Theme-provided components and third-party live sources vary by installation. Their registration contract is documented, but a particular site's private components are not reproduced here. WordPress core, a hosting provider, and external video, email, or payment services retain their own behavior and documentation.
Internal PHP and browser helpers are implementation details unless a documented integration contract says otherwise. Their names and signatures can change between releases. Public endpoints still enforce feature-specific validation beyond their registered schemas.
Maintaining the documentation#
For a release, refresh the block and element-settings registries, export the running REST and Abilities schemas, and rebuild the file and PHP inventories. Compare changed source with the corresponding guides. Check every internal link and heading anchor, then verify search, keyboard navigation, responsive layout, and any affected demos.
Update narration, captions, transcripts, and footage together when a workflow changes. Do not retain a successful old recording as evidence that a new release was tested.