Documentation Category
Developer Reference
Extend Hotel Booking and Aurelia through supported, versioned contracts without coupling to private implementation details.
Articles
Use the Email Customization Contract
Use the Free email presentation API, filters, layout providers and protected slots, with Pro profile precedence, fallback diagnostics and queue behavior.
Respect Core, Pro and theme ownership
Core owns the shared booking domain and public presentation boundary; Pro owns optional gated implementations; the theme owns rendering. A shared PHP namespace or…
Consume the public Theme Contract
The public Theme Contract connects Core/Pro-owned behavior to theme presentation. Current Core reports version 1.12.0 through kimorapro_hb_theme_contract_version(); themes should use exported functions and documented…
Override only catalogued presentation templates
Core's public catalog defines which template identities and exact versions a theme can override. Copy the current supported template surface, not a private partial,…
Use public components and design tokens
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…
Read public feature and language capabilities
Themes need safe presentation capabilities, not access to Pro's license or internal feature registry. Core exposes feature helpers separately from the small language-navigation facade.
Extend online payment gateways through Pro’s contract
The current online-gateway interface and manager are shipped in Pro, even though their PHP namespace is shared with Core. An extension must not assume…
Implement the public tax-rule provider contract
Core's current interface is KimoraPro\HotelBooking\Contracts\TaxRuleProviderInterface. Its two methods are id(): string and activeRules(TaxCalculationContext $context): array; the context class is KimoraPro\HotelBooking\Tax\TaxCalculationContext.
Use the external-inventory block write contract
Core exposes a provider-neutral inventory write boundary for authorized add-ons. It is not a public unauthenticated endpoint or a theme API for editing reservations.
Use documented hooks and versioned payloads
A hook is a supported extension point only within its documented ownership, arguments and lifecycle. Finding an action or class in source does not…
Preserve schema ownership and historical integrity
Core owns its shared database schema and upgrade path; Pro owns supplemental migrations for its features. Themes do not create or alter booking tables.…
Separate package metadata from compatibility evidence
A version/header, a compatibility declaration, a matching archive and a successful runtime test answer different questions. A release should identify all four instead of…
