This image shows the default Polaris theme, which is read-only. You create your own themes and styles to be used by experiences in your instance by either copying the Polaris or Coral theme or by copying a Theme Builder theme record. If you copy either the Polaris or Coral theme, you also must copy the styles under UX Theme Styles and make changes to those styles, as desired. At least one Core type
style must be defined.
Theme styles
When you configure a theme, you adjust the color schemes, fonts, and images of your applications. On the Theme Builder Theme form, you configure Order, Style, and Type settings.
Order
Style records with higher-order values override styles with lower values. The base system styles all have the order 0. If you meet the Applicability constraint, styles with higher values override the base system
styles. If not, the lower-value style is used.
Style
Style records define reusable styles that together comprise a theme. Core styles include color, shape and form, typography, and imagery. Variants are a different version of the theme, commonly different colors, that
users can select in preferences. The most common use of variants is for accessibility purposes, particularly to account for color blindness. If you decide to use a dark theme, consider selecting the Polaris or Coral
theme or create a dark alternate color palette in Theme Builder.
Type
Styles can be of either the Core type or the Variant type. Core styles are active by default. Users can choose from available variants from their Theme user preference, and those variant styles override the core style. Theme Builder doesn't automatically generate dark theme variants; however, you can create a dark alternate color palette with limited customization. For more information, see Add an alternate color palette. The Polaris and Coral themes include a Dark Theme variant that is available on instances with Next Experience enabled.