Public Site Runtime Became a Dedicated Product Surface

A dedicated public-site runtime separates custom theme development from admin-only editing work, providing a clearer home for routes, assets, and content.

Custom theme work has been tightly coupled to admin-only editing. Basker now has a dedicated public-site runtime for custom themes, so visitor-facing site behaviour is separated from admin-only editing work.

Why the separation matters

Customer themes now have a clearer home for routes, assets, previews, and content rendering. Without this separation, custom theme work is tightly coupled to the CMS and hard to reason about independently.

The foundation for custom themes

This is the architectural foundation that subsequent custom theme work builds on. All subsequent custom theme capabilities depend on this dedicated runtime being in place.