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.
True... 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.
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
[1]:https://github.com/twbs/bootstrap/blob/master/Gruntfile.js
[2]:https://github.com/twbs/bootstrap/blob/master/less/bootstrap...
[3]:http://gruntjs.com/plugins