4 ms·

Am I the only one that thinks v3 looks terrible? I like v2 because I could just whip out a little internal site/admin console/etc. and it looked as good or bet

Am I the only one that thinks v3 looks terrible? I like v2 because I could just whip out a little internal site/admin console/etc. and it looked as good or better than most other similar things without changing anything. I have some stuff out there with 5-10 custom CSS rules for the whole project. Now we've got v3 which has all sorts of wack colors and typography, like someone wanted to go "flat" but gave up halfway through.

elithrar 13y ago
> Now we've got v3 which has all sorts of wack colors and typography, like someone wanted to go "flat" but gave up halfway through. The idea of BS3 wasn't so much "flat" as it was a "remove gradients to allow easier customisation". Previously (in BC2) you had to override a ton of stuff to get "sane" buttons again. BS3 just gives you simple buttons that you can add to immediately. Same goes for the nav-bar. I much prefer it this way.
- efsavage 13y ago
  I can see that, I guess it's just going after a different use case than I was using it for (i.e. the decent designer-less site). It has no real value to me if I have to go through and style everything over again.
  - clone1018 13y ago
    Just head on over to Bootswatch and pick out your favorite theme, that's your new bootstrap :p My favorites so far are http://bootswatch.com/cerulean/ http://bootswatch.com/cerulean/
    - gbadman 13y ago
      Wow, thanks for reminding me of http://bootswatch.com http://bootswatch.com! I just checked it out again after having not looked for a while and I'm impressed with the v3-targeted swatches.
    - deleted 13y ago
      [deleted]
GoNB 13y ago
I see this reason a lot. Thing is, Bootstrap was never designed for your use case. It was always a framework to get started, meant for developers to build their designs upon. Think of Bootstrap as a model car kit. Bootstrap 2 was a Porsche that had just enough paint that people ran with it in their showcase, but that was never Bootstrap's intention. You were meant to complete the kit before showing off. Version 3 is a Tesla, but this time no paint.
- jafaku 13y ago
  > for developers to build their designs Don't you see a problem right there? In my opinion, it should at least come bundled with an optional style (the old Bootstrap2 style would be fine), so that we could at least use it for fast prototyping. In its current state, it's kind of useless since I'm gonna need a designer from day 1 anyway, because it looks terrible by default.
  - maaaats 13y ago
    > it should at least come bundled with an optional style (the old Bootstrap2 style would be fine) It will. :)
  - aram 13y ago
    Here's the corresponding issue on Github: https://github.com/twbs/bootstrap/issues/8706 https://github.com/twbs/bootstrap/issues/8706
markdotto 13y ago
v3 will ship with a v2-ish theme that you can optionally enable.
- joeblau 13y ago
  Is there a way to communicate that to users better? I don't think a lot of devs understand that it's easier to build up on a flat button as opposed to trying to overwrite stylesheets on a gradient button. Maybe something in the features for the final release that helps developers understand that it's not flat for flat design, it's flat because it's easier to build on top of.
  - markdotto 13y ago
    True, we could be louder about that. I'll get a tweet out about it shortly. To be honest I totally forgot about even mentioning it anywhere but in a few @ replies and issues on GitHub. And once we add the theme, it'll become clear :). Thanks for the feedback! <3

elithrar 13y ago

> Now we've got v3 which has all sorts of wack colors and typography, like someone wanted to go "flat" but gave up halfway through. The idea of BS3 wasn't so much "flat" as it was a "remove gradients to allow easier customisation". Previously (in BC2) you had to override a ton of stuff to get "sane" buttons again. BS3 just gives you simple buttons that you can add to immediately. Same goes for the nav-bar. I much prefer it this way.

efsavage 13y ago
I can see that, I guess it's just going after a different use case than I was using it for (i.e. the decent designer-less site). It has no real value to me if I have to go through and style everything over again.
- clone1018 13y ago
  Just head on over to Bootswatch and pick out your favorite theme, that's your new bootstrap :p My favorites so far are http://bootswatch.com/cerulean/ http://bootswatch.com/cerulean/
  - gbadman 13y ago
    Wow, thanks for reminding me of http://bootswatch.com http://bootswatch.com! I just checked it out again after having not looked for a while and I'm impressed with the v3-targeted swatches.
  - deleted 13y ago
    [deleted]

GoNB 13y ago

I see this reason a lot. Thing is, Bootstrap was never designed for your use case. It was always a framework to get started, meant for developers to build their designs upon. Think of Bootstrap as a model car kit. Bootstrap 2 was a Porsche that had just enough paint that people ran with it in their showcase, but that was never Bootstrap's intention. You were meant to complete the kit before showing off. Version 3 is a Tesla, but this time no paint.

jafaku 13y ago
> for developers to build their designs Don't you see a problem right there? In my opinion, it should at least come bundled with an optional style (the old Bootstrap2 style would be fine), so that we could at least use it for fast prototyping. In its current state, it's kind of useless since I'm gonna need a designer from day 1 anyway, because it looks terrible by default.
- maaaats 13y ago
  > it should at least come bundled with an optional style (the old Bootstrap2 style would be fine) It will. :)
- aram 13y ago
  Here's the corresponding issue on Github: https://github.com/twbs/bootstrap/issues/8706 https://github.com/twbs/bootstrap/issues/8706

markdotto 13y ago

v3 will ship with a v2-ish theme that you can optionally enable.

joeblau 13y ago
Is there a way to communicate that to users better? I don't think a lot of devs understand that it's easier to build up on a flat button as opposed to trying to overwrite stylesheets on a gradient button. Maybe something in the features for the final release that helps developers understand that it's not flat for flat design, it's flat because it's easier to build on top of.
- markdotto 13y ago
  True, we could be louder about that. I'll get a tweet out about it shortly. To be honest I totally forgot about even mentioning it anywhere but in a few @ replies and issues on GitHub. And once we add the theme, it'll become clear :). Thanks for the feedback! <3