Custom Themes Can Now Be Tested In A Production-Like Environment
The custom-theme runtime can now be deployed for production-style testing, with tenant registry work, CDN routing, and serverless rendering support.
The custom-theme runtime can now be deployed for production-style testing. Tenant registry work, media upload fixes, CDN routing, and serverless rendering support make this a major step in the path to the first customer launch.
Closing the local-to-production gap
Basker can now test a real custom theme against tenant data outside a local development environment. This closes the gap that often causes surprises after launch: a theme that works locally but behaves differently under CDN routing, serverless rendering, or production media paths can now be validated before it matters.
Confidence before go-live
For teams approaching their first launch, the ability to verify theme behaviour in a production-like environment changes the risk profile of a handover. Problems that would previously surface on launch day can now be caught and resolved during the review period.