Architecture overview
Follow a page from theme markup through editing, validation, draft storage, and public rendering.
Watch the video
Chapters and transcript Captions are included.
Plain HTML with a theme-owned design#
A Kindly-built page stores ordinary HTML in WordPress post_content. The theme owns its stylesheets, design choices, header, footer, and component library. Kindly Edit adds a direct editing interface to the live page rather than converting every element into a separate block record.
- Theme and HTMLDesign choices, components, and page content
- Editor and inspectorSelections, controls, and undoable changes
- Authenticated savePermissions, revision checks, and validation
- Private draftSaved work awaiting publication
- Publish and historyContent promotion and recorded revisions
- Public renderingDynamic content, styles, and interactions
The diagram describes ownership and flow; each stage has its own permission and conflict checks.
Editor entry#
Signed-in users open an editable page with ?edit. The entry and editor modules check access, page mode, and the license gate. The main editor attaches a shadow-root interface to the page, identifies editable sections and elements, and tracks selections and undoable changes.
Native element settings are registered separately from the main editor. Content, Style, Layout, and Advanced controls write semantic HTML, classes, allowed inline styles, or serialized data-ke-* settings. Generated editing UI is removed during serialization.
Persistence#
Save creates an editor draft. Publish promotes content and related metadata, records a revision, and updates the public page. Revision tokens and save guards prevent a stale session from silently overwriting newer work. Shared parts and other source records retain their own ownership and publication rules.
The REST layer and the automation abilities share lower-level validation and save functions. Automation does not get an unrestricted alternate content store.
Public render pipeline#
The server resolves shared content, dynamic fields and loops, conditions, responsive styles, and approved element code. Native browser scripts initialize interactions on the resulting markup. Visitors do not need the editing UI.
Boundaries#
Theme configuration describes available design choices. Sanitization validates saved content. Capability checks authorize actions. Signed element code has a separate trust model. A license controls editor availability. These mechanisms solve different problems and should not be substituted for one another.
See the source map for every shipped runtime file and the module reference for functions and hooks.