From 010cf397dfe1ab9c163ad48edc6904d31431c629 Mon Sep 17 00:00:00 2001 From: Cagatay Civici Date: Mon, 1 Apr 2024 15:02:15 +0300 Subject: [PATCH] Remove spacing --- doc/theming/styled/ArchitectureDoc.vue | 2 +- doc/theming/styled/configuration/OptionsDoc.vue | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/theming/styled/ArchitectureDoc.vue b/doc/theming/styled/ArchitectureDoc.vue index b7b60dee1..135fd020c 100644 --- a/doc/theming/styled/ArchitectureDoc.vue +++ b/doc/theming/styled/ArchitectureDoc.vue @@ -26,7 +26,7 @@

Best Practices

-

+

Use primitive tokens when defining the core color palette and semantic tokens to specify the common design elements such as focus ring, primary colors and surfaces. Components tokens should only be used when customizing a specific component. By defining your own design tokens as a custom preset, you'll be able to define your own style without touching CSS. Overriding the PrimeVue components using style classes is not a best practice and should be the last resort, design tokens are the suggested approach. diff --git a/doc/theming/styled/configuration/OptionsDoc.vue b/doc/theming/styled/configuration/OptionsDoc.vue index 7fb414d6e..4d0984e3d 100644 --- a/doc/theming/styled/configuration/OptionsDoc.vue +++ b/doc/theming/styled/configuration/OptionsDoc.vue @@ -9,7 +9,7 @@ class selector such as .app-dark and toggle this class at the document root. See the dark mode toggle section for an example.

cssLayer

-

+

Defines whether the styles should be defined inside a CSS layer named primevue or not. A CSS layer would be handy to declare a custom cascade layer for easier customization. The default is false. View the CSS layer section for an example usage.