Skip to content

Commit 44791cf

Browse files
authored
Merge branch 'main' into docs/component-renderer-update-function
2 parents 93f8f14 + a82e1f0 commit 44791cf

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/styling/index.adoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,11 @@ The Vaadin 24 way of loading styles through the [annotationname]`@Theme` annotat
4646

4747
== Themes
4848

49-
By default, Vaadin components are rendered with their minimalistic built-in <<themes/base#, base styles>>, which are a good starting point if you want to customize the look and feel extensively. Vaadin also ships with two themes, <<themes/aura#, Aura>> and <<themes/lumo#, Lumo>>, that provide a more polished look and feel for Vaadin components.
49+
Vaadin components come bundled only with minimalistic, built-in base styles, on top of which the application can load one of the two Vaadin themes, <<themes/aura#, Aura>> or <<themes/lumo#, Lumo>>, which provide a more polished look and feel.
50+
51+
If no [interfacename]`AppShellConfigurator` is defined for the application, the Aura theme will be loaded automatically. Otherwise either theme needs to be loaded explicitly using the [annotationname]`@StyleSheet` annotation.
52+
53+
While both themes are highly customizable, you can also choose to implement your own custom styling directly on top of the <<themes/base#, base styles>> in order to avoid having to override the styling provided by the theme.
5054

5155
[cols="^.^1, ^.^1, ^.^1"]
5256
|===

0 commit comments

Comments
 (0)