CSS Customisation


This page explores the steps to publish CSS if there are any CSS Customization/changes. While customising, if any changes are made In the CSS folder it has to be compiled and published to npm.


Currently, the CSS is published in npm as @egovernments/digit-ui-css

Refer to the NPM link here - digit-ui-css.

So any changes to the CSS folder locally must be published in different organisations and in the same or different package name. For example - @xyz/digit-ui-css and version 1.0.0 then the following changes have to be made in the code to reflect in the digit-ui

index.html - file location


The style sheet link must be updated as follows,

<link rel="stylesheet" href="https://unpkg.com/@xyz/digit-ui-css@1.0.0/dist/index.css"/>

Use either of the following commands to publish the CSS

  • In the frontend/micro-ui/web/micro-ui-internals folder run yarn run publish:css or

  • In the frontend/micro-ui/web/micro-ui-internals/packages/css folder run yarn run publish --access public

There are two ways to customize the CSS -

  1. Override the required CSS only without changing in the CSS folder and making changes only in the custom CSS folder. Both CSS will be present in the index.html the order of the package mentioned in the HTML determines which CSS needs to be taken ie the box mentioned in the last will have more precedence. example of overriding CSS as follow - index.html

  2. Overwrite the complete existing CSS.

Note: If there is overwriting of the complete CSS, future upgrades will need manual work to take the upgrade/difference changes.

Reference doc for publishing any package to npm -

Last updated

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.