Developer Reference

Understand Free and Pro ownership Map Hotel Booking Core, Pro, Aurelia and the update service so extensions stay inside the correct ownership and license boundary. → Consume the public theme contract Use the versioned Hotel Booking theme contract, context envelopes and lifecycle hooks without mutating canonical business data. → Use the template override contract Create only catalogued, version-matched Hotel Booking template overrides and preserve safe fallback when a child or parent candidate is invalid. → Register components and design tokens Build theme-owned components from normalized context and map validated design tokens without shipping a plugin default skin. → Use feature and Language Navigation contracts Query presentation capabilities and language switch URLs through provider-neutral contracts without exposing entitlements or vendor APIs. → Integrate payment gateways Register a payment gateway through the public extension API while preserving server verification, amount matching and idempotent ledger ownership. → Register a tax provider Extend the Tax Rule Provider contract without changing calculation order, rounding, inclusive pricing or immutable booking snapshots. → Handle external inventory blocks Use the provider-neutral External Inventory Block contract for iCal occupancy while keeping blocks read-only and inside the Free inventory path. → Use hooks, filters and versioning Subscribe to documented actions and filters with stable signatures, explicit ownership and semantic-version compatibility rules. → Protect schema migrations and data integrity Plan additive migrations, locks, snapshots and rollback behavior without treating documentation or themes as a database authority. → Validate package updates and compatibility metadata Publish verifiable package identity, checksums and compatibility metadata while keeping update transport and entitlement ownership separate. →