Each Kendo UI theme package includes the source files of the respective theme and, thus, provides options for you to modify and rebuild the theme as part of your build process.
For example, you can change the theme colors, remove the CSS of unused components, or use specific theme colors to style your application. The theme source files are located in the
scss folder of the theme package.
For the full list of variables that can be modified in a theme, refer to the article on each theme customization:
To build a custom theme by using the theme variables, apply either of the following approaches:
- (Recommended) Use the build process of your application (webpack/angular-cli)—This approach simplifies the upgrades to new component and theme package versions.
- Use the build process of the themes—This approach requires you to build the theme each time the theme packages are updated.
To preview all components with a specific theme applied and for utilizing versatile color swatches, use the ThemeBuilder application which provides an interface for theme customization.
If you use Angular 8, you have to upgrade to the latest version of the themes. For more information, refer to the article on keeping up to date.
Angular CLI supports the compilation of SCSS files. To compile the theme in your application, import the style files for the components in use.
// Import only the PanelBar and Grid styles. @import "~@progress/kendo-theme-default/scss/panelbar/_index.scss"; @import "~@progress/kendo-theme-default/scss/grid/_index.scss";
With this setup, you can customize theme variables directly in your application. For example, you can change the default accent color from orange to pink with the following lines:
$accent: #ff69b4; @import "~@progress/kendo-theme-default/scss/panelbar/_index.scss"; @import "~@progress/kendo-theme-default/scss/grid/_index.scss";
It is also possible to include all available component styles. However, this will significantly increase the build time and bundle the size of the application.
// styles.scss @import "~@progress/kendo-theme-default/dist/all.scss";
ng add schematics for the Kendo UI packages adds the precompiled CSS file to
angular.json. When you use the SCSS files, you have to remove these references.
The default Angular CLI configuration produces CSS that is not compatible with Internet Explorer v11. To provide support for Internet Explorer 9 to 11, remove
not from the last
not dead line of
src/browserslist. For more information, refer to the article on changing the target browsers for Autoprefixer.
> 0.5% last 2 versions Firefox ESR not dead IE 9-11
While including the Kendo UI themes in the styles of your application is convenient, it adds up to 30 seconds to the build time because the themes are compiled on each build. To reduce the duration of the build process in Angular CLI v8, install the fibers package by running the
npm install --save-dev fibers command.
While each Kendo UI theme has a dedicated NPM package (for example, @progress/kendo-theme-default), the source code for all themes is located in the kendo-themes GitHub repository which contains a build task that compiles the theme sources to CSS. To customize a theme, modify the source code of the theme and use the build task to produce a CSS file for your application. This approach avoids the need for setting up a build configuration when you compile SCSS but may be harder to maintain as the process has to be repeated each time a theme is updated.
To improve the development process, the individual GitHub repositories of each theme were merged into a single kendo-themes repository. The individual theme repositories are now archived.
A swatch is a set of variables which customizes the appearance of the theme.
- Each swatch is placed in a separate file. A theme may contain multiple swatches.
- Swatches are useful for creating multiple, persistent theme variations.
.cssoutput file can be shared across projects and requires no further processing.
To create a swatch:
- Clone the kendo-themes GitHub repository.
- (Windows only) Install the node-gyp prerequisites by running
npm install --global --production windows-build-toolsfrom an elevated PowerShell or, as Administrator, from the CMD.exe.
- Install the dependencies for all themes by running
npm install && npx lerna bootstrap.
- Switch the working directory to
- Create a
.scssswatch file in the
- Build the swatches for the theme by running
npm run swatches.
The following example creates a swatch for the Material theme in
// Variables. $primary-palette-name: blue; $secondary-palette-name: pink; $theme-type: light; // Import the theme file for the components you use. @import "../panelbar/_index.scss"; @import "../grid/_index.scss"; // Alternatively, include all components. // @import "../all.scss";
To create a custom theme by modifying the themes source code:
Clone the kendo-themes GitHub repository.
Install the dependencies for all themes by running
npm install && npx lerna bootstrap.
Customize the theme variables in the
Build the themes with the
npm run buildcommand to create the customized version of the themes in the
You might want to omit the styles for some components in the CSS output. To include only the styles that you need, run the
COMPONENTS='component1,component2' npm run buildcommand. For example, to create a CSS file that includes only the Grid and PanelBar styles, run
COMPONENTS='panelbar,grid' npm run build. The command creates the
dist/custom.cssfile which includes only the specified components.
After the build completes, use the compiled CSS.