51–60 of 138 posts
In the documentation pages they have inexplicably moved the navigation links to the right side.
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.
Official Sass port. That's pretty big news.
The main reason I chose LESS was because of bootstrap support, I'm extremely happy with it and can't believe I didn't start with it before. I'll see how this port goes, but I've read some good stuff about SASS: http://css-tricks.com/sass-vs-less/ Any other points anyone can make for SASS against LESS?
For instance, combined with Compass, you can read image sizes and automatically pull in width and height for a class. Or you can more easily make sprite images via a mixin that knows the size of the image and how many rows/columns you have.
I've been using bootstrap-sass since it was targeting bootstrap 2.3. They've done a great job of keeping up with bootstrap development, so it's great to see them officially supported. It wouldn't shock me at all if Bootstrap eventually moved over to SASS officially in the future.
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?
Beyond that, the js portions of Bootstrap are nice, but they're certainly not unique.
My opinion of things like Bootstrap and Foundation is that they're nice, but they serve a purpose that I think isn't appropriate for a lot of uses. I think if you need to put together something fast, they're great.
If you're investing tens or hundreds of thousands of dollars in design, I think it behooves you to build a lot of your components from scratch. I might take a few components from Bootstrap, but I can't really see it being my starting point.
As for an alternative, I think doing it yourself to suit your own needs is the alternative.
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…
Answer: Don't bother for large websites. Get normalize.css If you really need grids, you can get a lighter framework.
Pushed to CDN too http://www.jsdelivr.com/#!bootstrap
Curious what people's thoughts on using a CDN for these sorts of things (Bootstrap, JQuery etc) versus deploying it on their own sites. It's an extra DNS query - but thoughts on overall impact on performance?
When RC1 came out, the CDN version had a random dev build (90% broken) but on the page they linked to it as RC1.
I compared the downloaded version .vs CDN and the files were different.
So be careful, if company hosting CDN is not well known or has a good reputation you might screw your self.
In the documentation pages they have inexplicably moved the navigation links to the right side.
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.
Earlier quoted context omitted.
The main reason I chose LESS was because of bootstrap support, I'm extremely happy with it and can't believe I didn't start with it before. I'll see how this port goes, but I've read some good stuff about SASS: http://css-tricks.com/sass-vs-less/ Any other points anyone can make for SASS against LESS?
SASS is backed by Ruby, so you can take advantage of all of Ruby's power, including reading from the filesystem. For instance, combined with Compass, you can read image sizes and automatically pull in width and height for a class. Or you can more easily make sprite images via a mixin that knows the size of the image and how many rows/columns you have. I've been using bootstrap-sass since it was targeting bootstrap 2.…
* { box-sizing: border-box; }
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.