Skip to content

Changelog

This page tracks Section Editor Kit’s release history. There is no generated-from-git changelog here, and no versioned docs tree: the docs on this site track HEAD, a single living version, and this page is hand-curated rather than assembled from commit history. A release cadence (and a real multi-version history) starts once SEK ships its first post-1.0.0 update; until then, this page has one entry.

The version above is read from the plugin header (section-editor-kit.php); if you’re checking whether your install matches what these docs describe, that’s the number to compare against.

At this version, SEK is a config-driven section editor for WordPress: a React-driven admin UI (mounted per-post via a .sek-editor contract) for composing pages out of reusable, YAML-defined sections, backed by config-as-source-of-truth (no database drift: a section’s shape lives in a committed YAML file, not a serialized blob) and Blade/PHP template rendering on the front end. The docs on this site cover the full surface as it stands today:

  • Getting Started: installing the free plugin, wiring a theme’s .sek.yml, and building a first section end to end.
  • Core Concepts: the vocabulary (sections, fields, handles), reconciliation on mount, lost/inactive values, and global sections Premium.
  • Defining Sections, the developer track: config & YAML authoring, the field-type system, the Blade render pipeline, the sek CLI, the form-driven Config Editor admin UI, and global-sections authoring Premium.
  • Editing, the content-editor track: composing pages, editing values and conditional visibility, undo/redo and the section clipboard, working with lost values, and live preview.
  • Schema Evolution: changing a shipped section’s config safely, per-section migration rules, reconciliation in depth, and Mass Migration Premium for rolling a change out across every existing instance at once.
  • Reference: the exhaustive configuration, .sek.yml, JSON-Schema, and CLI references, plus the generated field-types catalogue covering all 43 field types at the time of writing and the REST endpoint reference (free and premium Premium, badged per route).

Premium-tier features throughout this site are marked with the badge shown above: it answers only whether a capability ships in the free or the premium download, nothing about how that split is implemented.

Once a release cadence starts, each dated release lands here as its own entry (version, date, and a short human-written summary of what changed), added above this line, newest first. This page will not grow a generated-from-git history; entries stay hand-curated.