Repository navigation
Contract change type: additive
Added
- Core quote and pull-quote blocks follow the
spectre-uisp-quoterecipe
on the front end and in the editor, with two registered block styles:
Accent rule (thick accent leading edge) and Statement (large text
under a decorative quote mark). Bold text in the citation renders as the
name; the rest renders muted as role and organization. The accent colour
comes fromtheme.jsonsettings.custom.quote.accent
(--wp--custom--quote--accent), so a child theme re-points it without
redeclaring a--sp-*property. - Core table blocks follow the
sp-tablerecipe, including the header row,
caption, footer row, and the Stripes style. Computed styles match an
sp-tablewith the same data. - README.md "Core Block Styles" and a Child Themes table pointing at the
component options (sp-textweight/leading/variant="accent",
accent/accentOutlinebuttons,sp-steppertone,sp-quote,
sp-stat, splitsp-section-head,sp-table) that replace styling
[data-sp-text-native]or.sp-btninternals.
Fixed
- Post content inside
sp-prosenow follows thelayout.prose.flowrhythm
(wider gaps around headings, quotes, figures, and rules). The unlayered
sp-content-flow16px gap overrode it before, and core's figure and
pull-quote margins plus spectre-ui 5.5.0's.sp-prose blockquotemargin
reset would otherwise collapse quote and figure spacing. - Removed the argument-less
editor-color-paletteandeditor-font-sizes
theme supports.theme.jsonalready supplies both, and WordPress 7.1
printed aforeach()warning for them.
Changed
- ESLint ignores built JavaScript bundles copied into nested downstream child
themes. Those minified outputs are linted from source in their owning
repositories and otherwise produce false errors when validating this repo. - Updated Vite from 8.3.3 to 8.3.4.
- Raised the Node.js engine floor to
>=24.18.0to match the WordPress
Playground runtime pulled in by@wordpress/env, which otherwise emits
EBADENGINEwarnings on install. CI and the WordPress smoke test now run on
Node 24 only.