Use of Theme studio in Telligent 10.2 and higher version

We are in the process of upgrading the Telligent version from 8.5 to 10.x but we saw that Telligent 10.2 and higher version having new feature called theme Studio. we have following questions and looking for input.

1. What s the advantage of Theme studio, do we have any reference

2. what challenges we can face if we do not consider Telligent 10.2 or higher for migration and use 10.1.10 instead.


  • There is never a good reason to choose an older release of Community if you have the choice. The most recent version will always provide the latest features, performance, and bug fixes, as well as the longest support for that version. Upgrade safety and backwards compatibilility is a core principle of the platform. Content, configuration, themes, and widgets from one version will always continue to run in the next version. The platform API does not change, it just grows. For example, themes and widgets from 9 will run in 10.1. And themes and widgets from 10.1 will continue to run just fine in 10.3. In my opinion, it is actually riskier to use an older version if you have the option.

    10.2 does introduce Theme Studio. Theme Studio is the most significant evolution of the theming platform since the introduction of scripted widgets in 6.0. At a high level, Theme Studio aims to make Community both more approachable for developers to customize and create themes as well as for community managers to configure and brand those themes without the need for custom code. It does this in a few ways:

    Theme Studio development environement: Theme Studio introduces a new theme development environment in administration, which looks and behaves similar to Widget Studio, enabling the editing and management of site, blog, and group themes.

    Platform updates: Theme Studio introduces many new platform features, most notably theme configuration. A theme can now define configuration in the same syntax as widgets, enabling the theme to be configured and branded by community managers, similar to how widgets are configured. Theme configuration can include any properties and data types that widgets could use. Additionally, themes can define palettes -- pre-selected groupings of configuration options available for selection by community managers. Theme configuration data is then available via velocity and LESS APIs to the theme's implementation in Theme Studio as well as to widgets running in the context of the theme. Additionally, all other platform APIs are also available to themes.

    Configuration UI: A theme's configuration options are then exposed as a form in the front UI when configuring the use of a theme -- think colors, fonts, logos, responsive behaviors, or any other options you would like the theme to expose.

    While this is a significant change, it is fully backwards-compatible with pre-existing themes, which are automatically converted into the new Theme Studio format.

    Hope this helps!