I'm also amazed at how often I spot it now. Seems like it's everywhere.
As a developer with a decent amount of design skills, what I love is that their defaults are extremely easy to customise and extend where necessary.
> I'm also amazed at how often I spot it now. Seems like it's everywhere.
I also see it everywhere, which is the main impetus for me to come up with a completely customised version that reflects my design style. Hopefully more people do the same instead of just using it straight off of a clone.
Maybe in the future, something like Bootstrap will become the default way that web browsers render websites, and we can just get rid of most of the boilerplate CSS.
I will be converting my other sites all to bootstrap. But with slight color changes it can provide a difference but consistency
For me, I always thought actually fully separating markup and layout/styling was a pipe dream, and unless you're going to absolutely fill your page with id's and classes (a la zen garden) and spend enormous time tweaking things, then a major overhaul will require changing markup anyway, so why bother? But that seemed to fly in the face of advice I was reading. But using a grid seems to fly in the face of that old advice too. So what's the deal? Do people no longer think markup and styling/layout should be separated? Or was I just misinterpreting what I read in the past?
If your idea proves successful then over time you will need to evolve away from bootstrap anyway, and you can get cleaner markup and style along the way.
If your idea proves unsuccessful, good thing you didn't waste too much time on a pure semantic markup.
Still, the clue is in the name. "Bootstrap" your app, then faff it into pure web standards over time, should the app prove popular.
Less time wasted on an app you don't know will fly.
That said, a Bootstrap generator that generates LESS, which in turn generates CSS? Seems overengineered. Almost all of these variables are in variables.less anyway. I'd hope that anyone setting up Bootstrap has the skills to edit this one file.
https://github.com/twitter/bootstrap/blob/master/lib/variabl...
So it could have a 'save to localStorage' button, then a list of your previous saved configurations in a side panel?
Excellent work!
Once you add that then you'll have something super useful. I've customized the top bar color for a few different sites and it is a bit painful. (there was an open bug about making it easier, haven't checked it lately though)
http://groups.google.com/group/twitter-bootstrap/browse_thre...
The author wrote it in one evening which makes it even more impressive.
If you do build anything using Bootstrap, please feel free to submit to Built With Bootstrap:
To whit, over the past two weeks I completely redid a support application using Bootstrap and my output CSS totals ~250 lines, whereas before it was somewhere around ~2600 when it was all said and done. My current .js file has two functions in it. I think we've found a winner here.
Another benefit is that a developer not well-versed in the front-end is easily able to build a basic, functioning front-end to an app with small learning curve, and I'm going to assume that they'll be able to work on an app that already has it. Or so I hope, because after twelve years, I'm a little sick and tired of writing said code.