A full-width hero section: a background image behind a headline, subtext and call-to-action links, aligned left, centre or right.
"sideEffects": ["**/*.css"] so a bundler can drop the package when its exports are unused. Packages that build class names depend on @behivetech/get-class-name (a real dependency, kept external) instead of bundling their own copy of the helper, so an app loads it once..meta.ts, .schema.ts and .migrations.ts modules in the package files, so the published index.ts resolves its imports.--hero-banner-scrim-opacity custom property. The default stays 0.4, so existing uses are unchanged; a site can raise it to keep the text readable over any photo.BHT__HeroBanner, PascalCase like every other component (it was BHT__hero-banner); child and modifier classes follow (BHT__HeroBanner__cta, BHT__HeroBanner--align-left). Nothing else changed. Styles that targeted the old class name from outside the component need the new one — though the convention is to add a modifier or prop to the component rather than style its classes from elsewhere.description from the README's first paragraph, and homepage plus a Docs: line in the README pointing at the package's page on https://bht-galaxy.vercel.app, all applied at publish time from one source. Seven READMEs that still said "TODO" have a summary; @behivetech/atoms.stat and @behivetech/cms.base-styles have a README at all; the hand-written props tables are gone from the READMEs, since the Props tab on the site is generated from the interface.pnpm add @behivetech/atoms.button. The versions already on GitHub Packages stay there; nothing in the packages changed.<name>.example.tsx (was <name>.composition.tsx), following template 0.4.0 of the component registry: the published files list and the docs site's Examples tab use the new name. No component code changed.registry/behivetech/<category>/<name> and builds with the template's shared env. Published output is the same code; the class-name helper is bundled into each package instead of being a runtime dependency on @behivetech/get-class-name, the tarball now ships README.md, the source, the compositions and a docs.json the docs site reads, and each package declares license: MIT.a7bf591: Restyle to Material Design 3. Colors, type, shape, elevation and motion now come from --md-sys-* tokens, and each one falls back to the pre-MD3 --color-* name. Hardcoded brand colors and filter: brightness() are gone, so components follow the theme in both light and dark.
Interaction
:focus-visible ring.Props and component sizes are unchanged.
Visible changes
--admin-sidebar-* variables.Fixes: these never matched and now work:
Specificity: modifier styles now use .BHT__X--mod.BHT__X (0-2-0). A single-class className override of a modifier-controlled property needs matching specificity to win.
f8c57db: Generate TypeScript declarations once per build instead of once per format.
dist/index.d.cts is no longer emitted. Nothing referenced it: each package's exports["."].types points at dist/index.d.ts, which is unchanged and still covers both the import and require conditions. There are no API, type, or runtime changes.
textarea, array and group schema field types, plus hint and the