Re:Why we love Twitter Bootstrap and why you should too
by lowboy on Thursday February 28, 2013 @01:30AM
(#5297399)
Agreed. Most of the time you end up with a smaller file as it's easier to comment out the various modules as you're going as opposed to downloading customized builds from the website as you work.
Also, if Sass/Compass is more your cup of tea, there's a well-maintained port of Bootstrap[0].
Re:Why we love Twitter Bootstrap and why you should too
by autoreverse on Thursday February 28, 2013 @01:07AM
(#5297329)
Because sometimes LESS is more (learning curve)
Re:Why we love Twitter Bootstrap and why you should too
by dolphenstein on Thursday February 28, 2013 @01:08AM
(#5297332)
Easy until you try to upgrade.
Re:Why we love Twitter Bootstrap and why you should too
by lowboy on Thursday February 28, 2013 @01:27AM
(#5297383)
It makes the upgrade process easier if you stick to only making changes in their variables.less file[0], or even better creating a copy of it and including that instead in bootstrap.less. Heck, you can even just create your own top-level myproject.less file and copy over the includes you need using bootstrap.less[1] as a template.
[0]: https://github.com/twitter/bootstrap/blob/master/less/variab...
[1]: https://github.com/twitter/bootstrap/blob/master/less/bootst...
Re:Why we love Twitter Bootstrap and why you should too
by deservingend on Thursday February 28, 2013 @07:05AM
(#5298285)
Just import bootstrap.less into your own project's main less file and go from there.
I thought the whole point was that since it's LESS, you can change things up really easily.