3 ms·
Or just don't use the parts of Bootstrap you don't need, it's fully modular. Four steps for pairing BS down to your bare essentials: 1. Clone the repo [0].
by SkyMarshal 13y ago
Or just don't use the parts of Bootstrap you don't need, it's fully modular.
Four steps for pairing BS down to your bare essentials:
1. Clone the repo [0].
2. Hide unneeded JS modules: Open ./Gruntfile.js [1], scroll down to `concat` task, delete or comment the JS files you don't need.
3. Hide unneeded CSS: Open ./less/bootstrap.less [2], delete or comment Less includes you don't need.
4. Run the `grunt` task to recompile it.
Voila, lightweight, stripped down Bootstrap with only the parts you care about, in less than 5m. The beauty of frontend build systems.
A side benefit is once you adapt a build system for your frontend, you can add all sorts of additional customizations [3] to it, BS just provides a nice initial setup for that.
[0]:https://github.com/twbs/bootstrap https://github.com/twbs/bootstrap
[1]:https://github.com/twbs/bootstrap/blob/master/Gruntfile.js https://github.com/twbs/bootstrap/blob/master/Gruntfile.js
[2]:https://github.com/twbs/bootstrap/blob/master/less/bootstrap.less https://github.com/twbs/bootstrap/blob/master/less/bootstrap...
[3]:http://gruntjs.com/plugins http://gruntjs.com/plugins
- LoonyPandora 13y agoOr even simpler, use the customizer [0] to download the bits you want. A few checkboxes and you're done. [0] http://getbootstrap.com/customize/ http://getbootstrap.com/customize/
- SkyMarshal 13y agoThat works too, though you don't get the reusable build system, just the compiled output of it.
- scarecrowbob 13y agoTrue... but often I get a feature request and so rather than adding another file, it's often easier for me to just uncomment something that was previously unneeded.