...
To accomplish this, we provide custom theming as part of the standard on-boarding experience. The process involves several members of the team: a dedicated service team member, a product owner to manage the delivery and timelines and facilitate the process, and sometimes a front end developer to provide technical support via the Purchase Team support channel on Slack if needed.
Theming has evolved considerably over time. The first iteration of theming involved creating custom theme directories for each resort and writing custom CSS for each resorts theme. Theme Designer V1 improved the process by implementing custom CSS variables, limiting the theme options, and generating the CSS files via the stand alone Theme Designer app. Theme Designer v2 moved the stand alone app into the browser, allowing real time theme updates. It also did away with the individual theme directories for each resort, and moved the theme files to storage containers on Azure. This enabled theme updates to be done by the CS team without the need to deploy code by using the Theme Designer App.
Cloud Theming.
Our Cloud architectures front end (PUI) requires the use of the Theme Designer App to configure the theming, so any resorts onboarding to Cloud will require the use of Theme Designer. Theme Designer CSS can co-exist with legacy theme CSS to support the slow migration of resorts from their Legacy theme to the Theme Designer theme. This means that resorts can use our cloud infrastructure and a Theme Designer CSS file without using the actual Theme Designer Theme.
Theme Version Support.
While we do still support our legacy themes to a very limited degree (P1 fixes only), the CS team now uses AW Theme Designer v2 for the theming process so that they can expedite the entire onboarding experience and make theme updates without needing to involve engineering.