4 ms·
I actually know exactly what you're talking about and here's what I do: - Put Bootstrap in a folder and import it as a framework in CodeKit. (Just like you.)
by aed 14y ago
I actually know exactly what you're talking about and here's what I do:
- Put Bootstrap in a folder and import it as a framework in CodeKit. (Just like you.)
- In my project folder, I create a LESS file for the project (e.g. project.less).
- At the very top of my project.less I add an import for bootstrap (@import "bootstrap.less")
- I define and customize all my LESS variables within the project.less without touching bootstrap.less.
Yes, this does mean that the variables are being define again. However, this won't matter because what you define in your project.less will override everything else.
- VaughnDTaylor 14y agoThis solution will work for me. Thanks! I suppose it makes no difference that the variables are defined twice? I guess I was just getting stuck on the metaphor of other frameworks (eg. JQuery UI) where my custom files are kept separate from the library. Make sense?
- juddlyon 14y agoI do the exact same thing and it makes for a nice, modular setup. I have a site.less that imports bootstrap.less and whatever other "legos" I need.
- ZeroGravitas 14y agoThe bootswatch project (basically themes for Bootstrap) uses a similar system, though they generally have two less files, one for overriding variables, and a second one for theme-specific additions. https://github.com/thomaspark/bootswatch/tree/gh-pages/swatchmaker https://github.com/thomaspark/bootswatch/tree/gh-pages/swatc...