Providing a way to consistently style your app.
The Theme Builder provides a way to make stylistic changes that apply across your entire application, ensuring consistent styling throughout each user's Journey.
Like most Builders, the layout of the Theme Builder maps comfortably onto the general anatomy of the studio: to the immediate right of the Builder Bar is the Tree, to the right of which is the Stage, to the right of which is the Inspector:
In this document, we will discuss the broad functionality of each component of the Theme Builder and provide links to additional resources that provide a more detailed discussion of specific tools provided by it. This document is structured as follows:
The Tree is where you'll find an expandable and collapsible breakdown of the many Variants that can be edited within Theme Builder. What you select in the Tree determines what is displayed in the Stage and Inspector.
At the top level of the Tree is the Theme. You can only ever have one Theme in the Theme Builder at once, though it can be useful to name Themes when exporting them from and importing them to other applications, as this can help you keep track of precisely which theme you're working with at any given time.
Working at the Theme level of the Tree also allows you to set defaults that will impact the Variants of multiple Web Controls, such as the default color pallet and default fonts. Making these stylistic changes at the Theme level makes it easier to maintain consistent styling throughout your app and makes it less cumbersome to modify individual elements. The following example shows how changing the default color palette impacts Variants of multiple Web Controls at once:
The following example shows all of the different Variants of a Button Web Control. Note that all four Variants are displayed in the Stage, while the Inspector is left blank – there are no direct changes that can be made at the Web Control level:
If you want to add another Variant to a Web control, you can either duplicate an existing Variant to use as a base, or you can click on the '+' icon at the Theme level and select which Web Control you want to add a Variant to. For a more detailed dive into how to add Variants to Web Controls, check out Adding a Variant.
The following example shows how the Stage reflects changes being made to the boarder of a Button Variant in the Inspector:
The Inspector is where you'll actually define how Variants are styled. Exactly what styling options are available to you will depend on what you've selected in the Tree. Changes made in the Inspector will be immediately reflected in the Stage. You can also toggle over to the Activity Builder to see how your changes appear as part of your broader UI. (Remember: stylistic changes made to Variants apply immediately to all instances where that Variant was used in an app.)
The following example shows what it's like to toggle from the Activity Builder to the Theme Builder, make a style change – in this case, changing the font associated with the default brandPrimaryFont – and then see that stylistic change reflected after toggling back to the Activity Builder:
For a deeper dive into the sort of stylistic changes that can be made in the Inspector, check out Common Style Properties of Web Controls.
Working with Themes and Control Variants - Get into the nuts and bolts of how to make the most of Theme Builder.
Common Style Properties of Web Controls - Dive into the stylistic changes you can make to your Web Controls.
Styling with Themes - Discuss how to model Theme Build conceptually in order to get the most out of it.