You customize the web form with a profile. A profile bundles branding, functionality, and styling, and you apply it by passing its profileId when you create a web form (or by marking one profile as the default).
Start with Profiles - the model to understand how a profile is put together and, crucially, how the choice of styling (aspect vs theme) decides which UI generation your users see.
-
Profiles - the model - the profile object, how to apply it, and the
aspect(2.0) vstheme(2.1) split. -
Branding - logo, favicon, intro text, footer attribution.
-
Functionality and Navigation- which elements are shown and how the flow behaves.
-
Language and Localization - locale selection and custom title/subtitle overrides.
-
Theme (the 2.1 UI look) - colors, dark mode, typography, components for the new UI.
-
Styling with
aspect(deprecated) - the older styling model you migrate from.