[harisenbon]

Question about how these UI Kits are made:

Generally when I'm building a UI on top of bootstrap, I import all the LESS files into my project, and then compile them together with my project LESS files.

This lets me, for example, change the brand-primary color, or the base font size, etc, without having to override every component that might use that variable.

However, this UI Kit, as well as a number of other kits I've seen take in the pre-compiled Bootstrap CSS and override each item individually.

Is this the preferred way to do UI Kits? If so, what's the reasoning behind it? We build a lot of themes and UIKits for internal use, and would love to know if we're doing it wrong (tm).

[axelut]

There are 2 ways of working with Bootstrap. 1: the one that you specified where you change the variables directly in LESS/SASS (BS4). You need to know LESS/SASS for those changes. And 2: the one where you don't know LESS/SASS/CSS and you just want a different design for the default bootstrap. You download a UI Kit that has a new design and it is also containing new elements/example pages. Using the UI Kit/Theme/Template, you don't have to dig deeper into the variables if you don't want or you don't know how to do that. You just start to work with the backend and you are covered on the front end. Now the reason for us, here I'm talking just about our company, don't know why other do it in this way or another way, we want to overwrite the bootstrap and keep bootstrap as a separate file so we can easily migrate from v3.3.0 to v3.3.5 or from v3.3.5 to v4 alpha 4,5,6 etc, without doing major changes in our UI Kit. Makes sense?

[boraturan]

+1 on this