Skip to content

Releases: irisable/wp-title-layer

WP Title Layer 1.0.0-rc.1

Pre-release

Choose a tag to compare

@irisable irisable released this 29 Aug 11:31

WP Title Layer 1.0.0-rc.1 is the first public release candidate for external validation. It freezes the current subtitle, Series, Season, Sequence, structure, template, migration, and REST contracts without introducing a new data model.

Highlights

  • Canonical subtitles while keeping the native WordPress post title authoritative.
  • One ordered or unordered Series per post, with optional seasons and stable public Season IDs.
  • Sequence management for every ordered Series, independent of optional book-like structure tracks.
  • Series-wide or season-scoped introductions, main articles, epilogues, and appendices.
  • Theme-aware title rendering, structured Series archives, navigation, and verified Kadence integration.
  • Searchable Series workflows, Series health checks, Rank Math variables, and Simplified Chinese localization.
  • Conservative, non-destructive migration from Secondary Title and a verified ACF subtitle field. ACF is not a runtime dependency.
  • A documented REST contract for external publishers such as WP Publisher.

Compatibility and verification

  • WordPress 6.5 or later.
  • PHP 7.4 or later.
  • Public CI run #1 passed 95 contract checks and the complete source/package matrix on WordPress 6.5 with PHP 7.4 and WordPress 7.1 with PHP 8.3.
  • Each WordPress endpoint passed 827 integration checks, 111 Sequence Manager checks, and 61 book-structure checks.
  • Official Kadence 1.5.2 passed 40 adapter checks; Rank Math 1.0.276 passed 32 integration checks.
  • See the RC acceptance record for tested and still-unverified manual interactions.

Install

Download wp-title-layer-1.0.0-rc.1.zip below. Do not use GitHub's automatically generated source-code archives as the WordPress installation package.

SHA-256:

a0c5f19168c0f8cb64512a9fe9633002e7e2574bf76409ed8566277d3f3ba3b3

This is a pre-release, not the final 1.0.0 stable release. Existing sites should back up first and complete the focused manual acceptance checks before treating the candidate as production-stable.