71–80 of 138 posts
When are they going to add something like Foundation's block grid? That really comes in handy. (Note: I use both Foundation and Bootstrap). Block grid docs - http://foundation.zurb.com/docs/components/block_grid.html
Earlier quoted context omitted.
We'll see how it goes—if enough folks complain, we can revisit :). I wanted the content to be in the absolute forefront with this update. That meant not affixing the top navbar and downplaying the side nav. I think it's super helpful, but again, I'm open to reversing things again if it'd be better for more folks.
It's almost a web standard that navigation links are on the left.
Earlier quoted context omitted.
Answer: Don't bother for large websites. Get normalize.css If you really need grids, you can get a lighter framework.
This is the answer I've been hoping to hear.
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...
Question: If you were developing a large, content-driven site, would you bother with Bootstrap? Bootstrap seemed a bit like overkill when I had to use it in my old job. The CSS and markup seemed excessive, and the strict JS was kind of a pain to deal with. I know I can get something that looks half-decent up and running quickly with it, but if I'm not planning to take any visual design from it, is there much of an ad…
Question: If you were developing a large, content-driven site, would you bother with Bootstrap? Bootstrap seemed a bit like overkill when I had to use it in my old job. The CSS and markup seemed excessive, and the strict JS was kind of a pain to deal with. I know I can get something that looks half-decent up and running quickly with it, but if I'm not planning to take any visual design from it, is there much of an ad…
What's a good alternative?
Bootstrap has made my life monumentally easier for developing internal apps, yet I still feel like something isn't perfect. When developing mobile pages, I feel that the responsive interface is still not mobile-friendly enough for CRUD apps. I've played with RatchetUI (Which has Bootstrap members on the team), Semantic-UI, and Foundation, but the more-widespread adoption of Bootstrap keeps dragging me back in. I gues…
Defining all 4 screen sizes gets tedious. That aside, The new landing page on http://getbootstrap.com/ looks great
I've got to disagree, I think just having to add col size classes to divs to change how it's laid out on mobile/tablets/large monitors has helped tremendously, with 2.x it felt like we just had to hope it all worked out.
When are they going to add something like Foundation's block grid? That really comes in handy. (Note: I use both Foundation and Bootstrap). Block grid docs - http://foundation.zurb.com/docs/components/block_grid.html
Unless I am missing something, but I was able to easily reproduce it with current bootstrap styles: http://jsfiddle.net/MgcDU/8706/
...and they still haven't moved to "sanity" by adding/supporting: * { box-sizing: border-box; } the line that I start all my CSS with nowadays. Quote from their docs: > Some third party software, including Google Maps and Google Custom Search Engine, conflict with Bootstrap due to * { box-sizing: border-box; }, a rule which makes it so padding does not affect the final computed width of an element.
Earlier quoted context omitted.
This is the answer I've been hoping to hear.
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 reco…