Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twitter Bootstrap v1.4.0 Released

github.com

Post reply on HN
Print view View original

1–10 of 28 posts

Re: Twitter Bootstrap v1.4.0 Released

#2

Post by fuzionmonkey »

I'm impressed with Bootstrap.

It's really comprehensive and covers a lot more than other frameworks. I feel like with Bootstrap you could really crank out a web app, without having to do much presentationally.

The navigational aids also seem really helpful and the default typography and whatnot does look quite nice.

Re: Twitter Bootstrap v1.4.0 Released

#5

Post by travisfischer »

I'm excited about the form states in this release as well as the bug fixes.

As a generalist developer who does a little bit of everything but has a hard time with the design side of things, I'm loving using Twitter Bootstrap on some of my personal projects. One example where I've used it is http://smacktweets.com. The header bar alone, while extremely simple, is so much better than what I probably would have done on my own.

Twitter Bootstrap gives you great looking design elements with very very little effort. If you are good with the design side of things it's probably overkill and heavier weight than you want in a boilerplate if you are going to customize everything anyways.

Skeleton (http://getskeleton.com/) is another great boiler plate that I have also enjoyed using on all kinds of projects. It is really just a boilerplate and doesn't have all the pretty design elements that bootstrap has.

Just wanted to say thanks for putting this out and for the community continuing development on it. I'm really enjoying it.

Re: Twitter Bootstrap v1.4.0 Released

#6

Post by jonmc12 »

Recently I walked into project that used Twitter bootstrap for the initial CSS. A prototype was built, relying on the bootstrap CSS, and from that point on it has been hassle to work with the CSS.

I'm really not sure I understand the strategy of dumping so many styles into the global name space. Basically, all of us have been working around the styling as we implement features.. a major refactor is in order and we will likely be ditching bootstrap.

Just a warning if you plan to build beyond the styles provided by bootstrap, it is not straightforward. Really, the entire set of styles should be contained within its own namespace or some other meaningful semantic convention.

Am I missing something? What is intended after 'boot'? am I really supposed to replace these global styles manually?

Re: Twitter Bootstrap v1.4.0 Released

#7

Post by cwilson »

I'm really loving how fast they are pushing updates and just using Bootstrap in general. I've already used it for my startups new website (http://www.sponsorfied.com), which turned out pretty awesome, and the time I saved by using Bootstrap was pretty incredible.

I'm definitely using it for any side projects or sites I need to toss up without spending days on them.

Re: Twitter Bootstrap v1.4.0 Released

#8

Post by lukeholder »

jonmc12 wrote: post #6

Recently I walked into project that used Twitter bootstrap for the initial CSS. A prototype was built, relying on the bootstrap CSS, and from that point on it has been hassle to work with the CSS. I'm really not sure I understand the strategy of dumping so many styles into the global name space. Basically, all of us have been working around the styling as we implement features.. a major refactor is in order and we wi…

I suppose this is where you rely on the cascading thing - place a @import at the bottom of your bootstrap for your overrides.

Using a framework favors convention over configuration for the benefit of speed.

I especially like it because the team has a central set of documentation for the UI to use - that means if we override a style, if they followed the convention, everything works out better.

I do agree using a namespace would help though.

Re: Twitter Bootstrap v1.4.0 Released

#9

Post by pg_bot »

jonmc12 wrote: post #6

Recently I walked into project that used Twitter bootstrap for the initial CSS. A prototype was built, relying on the bootstrap CSS, and from that point on it has been hassle to work with the CSS. I'm really not sure I understand the strategy of dumping so many styles into the global name space. Basically, all of us have been working around the styling as we implement features.. a major refactor is in order and we wi…

I found that it was much easier to work with bootstrap if you just download the long form css version. Although it is a larger file, it is more straightforward since you can see all of the css for each element and then customize accordingly. The point of bootstrap is that it provides some nice defaults for you to work with for all elements, so you can build simple apps quickly. It is the role of the developer to customize the defaults when they do not suit the needs of the project. It honestly isn't that hard if you know a decent amount of css to quickly customize the classes to suit your own needs.
Post reply on HN