I don't want to build on it. My customers don't care that it looks like other sites, they just want something that looks professional and is easy to use, something which Bootstrap 2 does way better than I could do alone, and for which I am eternally grateful.
My customers range from a little to really non technical, so I think that "making them think" about what might be a button and what might be a label is a regression.
So if I want to upgrade, it's not just "encouragement" to customize, it's a necessity, and I consider it added work since I did not have to do it with the previous version of Bootstrap.
Hopefully, the theme mentioned in the article will suit my needs.
> With that said, well done everyone that helped on the project! Great work! :)
I can agree with that! I am very thankful for Bootstrap.
As tsurantino said in another comment, see here: http://getbootstrap.com/examples/theme/
http://getbootstrap.com/2.3.2/base-css.html#buttons compared to http://getbootstrap.com/examples/theme/
It was kind of them to make the extra effort though, for those of us who are happier with the older look and feel. Just a bit more like actual buttons, and it'd be perfect.
Well then, get a theme. That's the point of something that's meant to be a framework. You're not the only person using it and it's easier for you to download a theme than it is for people that don't use it as-is to reverse engineer the whole thing.
I'm personally a big fan of the opens-as-you-scroll sidebar navigation. Really cool for single-page apps!
And v3 will come with a v2 template.
http://getbootstrap.com/ http://getbootstrap.com/2.3.2/
The first is infinitely more confusing to the eye. There's no heirarchy; I don't know where to look. The second is clean while still giving me a sense of where I need to go to accomplish what I'd like to accomplish.
That being said, Bootstrap is supposed to be a starting point, not the final style. Going flat means less work for us developers when we start styling their components.
Bootstrap 3 looks old and Bootstrap 2 looks new.
Can you explain what this low-contrast thing is all about? Why would anyone think this was a good idea, except perhaps for UI elements that were explicitly disabled.
Concerned web devs are trying to raise awareness about it:
My justification for keeping the interface low contrast is to emphasize content. Keep in mind that getbootstrap.com is designed for web designers and developers—most of whom will be familiar with traditional web design. Menus are in obvious places and don't need to be called out.
Take the alternative to the extreme: if we need color to show us clickable elements should we have flashing underlines? Gifs that move arrows back and forth?
I can certainly see that. Do you count "main body text" as 'content' in your designs?
I can imagine myself working with a web design until I was sick of seeing lorem ipsum. This might lead me to under-value 'content' from the perspective of the reader. You think such a phenomenon happens with web designers?
Or could it be that Apple did some kind of brainwave analysis on rats (or users :-) and determined that low-contrast was better for some purpose, then the design community just cargoculted it?
I make an effort to never use placeholder text that doesn't at least closely resemble the real (or intended) content. This might just be me, but I'm pretty sure it's common amongst better designers: building something around fake data is much harder than building something 'real'.
> You think such a phenomenon happens with web designers?
Absolutely.
> brainwave analysis on rats (or users :-)
If Art and HCI are on opposing ends of a spectrum of interface design I've always been a bit closer to art—so my experience with testing ends at formal user interviews and guerrilla-coffee-shop tests. It's not a stretch to imagine the big tech companies doing brainwave analysis (and I'd be thrilled to participate at any level, it's seriously cool stuff).
> design community just cargoculted it?
Like any community, designers react to the trends of their peers, but a competent designer can defend pretty much any decision, which makes it hard to tell the difference between 'doing something familiar but wrong' and 'following trends that are right'.
I'd be curious how you'd react to something like this http://cl.ly/image/3A3O3Y2w2Y3i vs. http://cl.ly/image/40431N2q470M
The old page is pretty gross, IMO. If the current page is like an auditorium so quiet you're straining to hear something then the old page is like an auditorium where everyone is jabbering away. On the old design I see contrast in weight, size, alignment, and color, and that's just above the fold.
And agreed on your points. I'm looking forward to no longer having to override superfluous elements for the sake of customization.
I hope everyone catches that part of the post. It's very important, I think, based on the previous HN thread comments.
I've been quite surprised at how many people are in an uproar about v3 being flat. People have been saying things like "it's a dumb trend", "horrible UX", "so ugly", etc. For a skeleton starter template like this, flat is good. Having the design flat encourages you to build on it or theme it to your OWN style so all of the sites using Bootstrap don't end up looking the same (like they have in past versions). It was also annoying in past versions when you had to declare no gradients, or reverse engineer things to lose the "default theme". Making it flat now allows you to build up, where past versions made you go backwards first, then build the theme the way you wanted. I hope more people realize that rational now they have specifically called it out.
With that said, well done everyone that helped on the project! Great work! :)