Codedication Schema Blocks

Changelog

1.2.0

• Fixed: the ValidGraph validation bridge now calls the correct API endpoint (validgraph.com/api/v1/...) — the previous URL (wp-json/validgraph) never resolved, so validation requests always failed.
• Fixed: the Website settings tab now reaches the output — the WebSite node emits description, inLanguage and author from the fields the tab already collected, each omitted when empty. Previously five fields were saved and previewed but never emitted.
• Changed: the Website tab’s “sameAs” field accepts several URLs instead of one, using the same repeater the Review block uses. Stored single URLs keep working and are converted on the next save; no migration needed. The publisher URL stays a fallback — when a site identity is configured, the WebSite node keeps referencing it instead.
• New: review authors can be attributed to the site identity — a new “Attribute to the site identity” toggle on the Review block makes Review.author reference the site Organization or Person node instead of an anonymous inline author, and the visible byline is resolved at render time, so renaming the identity in Settings updates published posts without re-saving them. Falls back to the inline author when no identity is configured, so a reference never dangles. Extensibility contract bumped to 1.7.0 — Schema_Graph::registered_identity_id() is now a public seam.
• Changed: review @ids are now stable across block reordering — each Review node derives its @id from the block’s own id ({permalink}#review-a1b2c3d4) instead of its position on the page, and duplicated blocks emit two nodes instead of silently merging into one. Reviews saved before this release keep their current ids; nothing is rewritten.
• New: book details on the Review block — when the reviewed item type is Book, a new “Book Details” section adds author, publisher, publication date, format, page count, ISBN and external identity URLs (OpenLibrary, Wikidata, Goodreads). The filled fields are emitted on itemReviewed (author, publisher, datePublished, bookFormat, numberOfPages, isbn, sameAs) and shown as a metadata line under the item name, so the markup describes visible content. Every field is optional and existing reviews are unchanged.
• New: author Person entities — the automatic Article node now carries an author referencing a Person node built from the post author’s WordPress profile (name, author archive URL, avatar, bio, website). Nodes are minted on demand with a stable, PII-free @id, deduplicated against the site Person identity via a new Site Identity “WordPress user” picker. Extensibility contract bumped to 1.5.0 — new Schema_Graph::ensure_author_person() seam (callable by addons) and cddc_schema_blocks_author_person enrichment filter for E-E-A-T fields.
• New: automatic Article schema — posts now emit an Article node ({permalink}#article) wired into the unified graph, with headline, dates, publisher, primary image, and category. A new Content settings tab maps each public post type to None, Article, or Blog posting (default: posts → Article). Extensibility contract bumped to 1.4.0 — new cddc_schema_blocks_page_content_type filter (per-post type overrides, e.g. NewsArticle) and main-entity election API (Schema_Graph::flag_main_entity()) so addon content nodes replace the automatic Article instead of competing with it.
• New: FAQ and Review schemas now emit an inLanguage property derived from the site language (BCP-47, e.g. en-US). No configuration needed; overridable via the cddc_schema_faq_output / cddc_schema_review_output filters.
• Changed: unified JSON-LD output — the page now prints one <script type="application/ld+json"> with a single @graph instead of two separate scripts. Adds WebPage (and primary image) anchor nodes linking site identity, WebSite, breadcrumbs, and block schemas together. Extensibility contract bumped to 1.3.0 — new cddc_schema_blocks_graph_nodes filter.
• Changed: the FAQ block’s {permalink}#faq node id is retired — its questions now live on the page’s WebPage node (@type: ["WebPage","FAQPage"], mainEntity). FAQ rich results were retired by Google (2026-05-07), so no SERP feature depends on the old id.

1.1.0

• New: Extensibility contract 1.1.0 — the shared schema-ui editor toolkit is now exposed to addons on window.cddcSchema.ui via the cddc-schema-ui script handle (SchemaBlockCard, SchemaFormSection, SchemaPreviewInline, DurationInput, and more).
• New: Extensibility contract 1.2.0 — added the cddc_schema_blocks_settings_url filter so a companion hosting the Settings screen elsewhere can correct internal links (admin notices, the plugins-list action link).
• New: “Settings” action link on the Plugins screen, next to Deactivate.
• New: WordPress Playground blueprint (.wordpress-org/blueprints/blueprint.json) powering the Live Preview button on the wp.org plugin directory.
• Fix: the site-wide BreadcrumbList is suppressed on pages containing an addon breadcrumb block with manual items, so a page never emits two BreadcrumbList schemas.
• Fix: the Review block’s reviewBody now falls back to the block’s rendered HTML when the attribute isn’t set explicitly.
• Removed: the dead load_optional_integrations() bootstrap and Admin_Integration companion-coupling code (unreachable without a package this plugin never ships) — the Settings screen registration is simpler and wp.org-review-clean as a result.

1.0.3

• New: FAQ summaries now show an animated +/× icon that rotates when an item opens. Pure CSS driven by the native details[open] state (no JS), mirrored in the editor and respecting prefers-reduced-motion.

1.0.2

• Fix: Review block now renders translatable labels through __() so strings reach the .pot and translations apply at render time.
• Compat: Tested up to WordPress 7.0.

1.0.1

• Fix (WordPress.org review): conflict admin notice no longer emits an inline <script> tag — the dismiss handler is now an enqueued asset (assets/admin/conflict-notice.js) wired via data-* attributes on the notice container. The notice is also gated to the plugin Settings page and plugins.php only.
• Fix (WordPress.org review): FAQ block render callback no longer echoes a WP_HTML_Tag_Processor-mutated HTML string. The wrapper <div> is composed from escape-aware core APIs, and per-<details> Interactivity API directives are now injected via a render_block filter scoped to FAQ-ancestor renders. Foreign data-wp-* directives on nested blocks are preserved.
• Fix: Settings page rendered empty when the centralized Codedication admin was active. The plugin now registers a “Settings” tab inside the centralized renderer and the React app hydrates from saved option values.
• Fix: useSlotFills crash on older @wordpress/components; the Advanced tab now derives its visibility from the internal fill bridge.
• Improvement: Completeness score redistributed to weigh Site Identity (75), Website (20) and Breadcrumbs (5) — previously only Site Identity counted, so the page could reach 100% while Website and Breadcrumbs were empty.
• New filter: cddc_schema_blocks_is_settings_screen lets integrations declare authoritatively when the React Settings app should be enqueued.
• Cleanup: removed dead code paths in Admin_Integration, dead utils/completeness-score.ts / utils/json-ld-preview.ts modules, the unused HelpTip component family and the divergent PHP Site_Schema::get_completeness_score() (the React UI is now the single source of truth for completeness).
• Fix: schema-conflict admin notice now links to the real settings screen (Admin_Integration::get_settings_url()) instead of guessing from class_exists(), so the link is correct in the fallback path where the shared admin package exists but its renderer is not yet available.

1.0.0

• Initial release
• FAQ Block with FAQPage schema
• FAQ Item child block
• Review Block with Review schema
• Support for 6 item types
• Settings page for block management
• Interactivity API for accordion