Core’s component and design-token APIs are presentation contracts, not replacements for booking services. Theme-owned renderers receive normalized read-only data and return markup; financial and availability decisions remain authoritative in Core/Pro.
Inspect the public catalogs
Use kimorapro_hb_component_catalog() and kimorapro_hb_design_token_schema() before implementing a consumer. Probe their separate contract versions rather than assuming they equal the global Theme Contract version.
| Function | Current argument order |
|---|---|
kimorapro_hb_register_design_tokens |
owner, tokens, contractVersion, priority |
kimorapro_hb_register_component_renderer |
component, renderer, contractVersion, priority |
kimorapro_hb_component_context |
component, data, settings |
kimorapro_hb_render_component |
component, data, settings |
Design-token registration uses the kimorapro_hb_theme_register_design_tokens action. Component registration uses kimorapro_hb_theme_register_components. Each receives its own contract version. Tokens become ready before component registration; do not replace the lifecycle with a guessed early bootstrap priority.
Register complete declarations
A token set must include the schema’s required categories/values and use safe CSS scalars. It is one atomic theme-owned set, not a partial merge into invented defaults. Invalid owner/version/value rejects the set without replacing the previous valid declaration.
A component renderer has signature callable(array $context, string $contractVersion): string. Its envelope separates canonical data, normalized theme settings and presentation extensions. Unknown, unavailable, empty, throwing or non-string renderers fail safely to empty output.
Optional components need both capability and actual content; do not render an empty heading/wrapper because a premium plugin file exists. Themes should not instantiate the internal component/token system classes or query license internals.
Verify output and fallback
Escape theme-owned text/URLs, keep prepared financial values and machine attributes unchanged, and retain the owner’s form hooks. Test failed registration, missing content and Free-only behavior. Native fallback and CSS should remain usable without JavaScript enhancements.
See feature/navigation capabilities and template overrides when a full versioned surface is required.
