After playing around with Bootstrap, I realized what a huge boon it was to my projects (programmer lacking in design skills). One thing I like about it is I don't have to pick colors. It does the border, button, text, and nav-bar colors for me. I don't trust myself to pick my own colors! I would really like a way to preview or be able to pick some other colors other people have made. Maybe you could expose a perma-link to a set of config options so they are easy to share.
I'm also amazed at how often I spot it now. Seems like it's everywhere.
I second the entire comment -- well, excluding the programmer lacking design skills.
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.
Use sites like http://www.colourlovers.com/ to get inspiration for colors. If you are a programmer you should spend some time studying the color theory - much of it is based on math and you can actually often calculate which colors will work together.
Agreed, I use it in all my projects now and it is a huge time saver. If nothing else, not having to futz around with form elements more than makes up for the added overhead.
I totally agree. I've been wondering for 15 years why every website has to have a special custom design anyway. With native apps, custom design almost always works against them, as opposed to the OS's default, familiar design.
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 am really not trying to stir a pot here. I am truly looking to learn. But the whole idea of bootstrap seems to go against other stuff I used to read about how to use css. I understood that your markup should be semantic and detached from you layout and style as much as possible. But when you use the bootstrap grid to arrange your page, you are absolutely mixing content and layout.
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?
It's still a good idea to separate markup and styling. In the interest of getting things that look decent out the door quickly it's often necessary to postpone ideological purity.
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.
There's an entire ecosystem coalescing around Bootstrap and I love it. It's the framework for the coders who are design challenged. I know more and more people like me who are incorporating it in every project they build. In time it will raise the minimum level design bar for the entire web.
Cool idea, in addition to the color picker you might want to let it change the current page live via DOM manipulation so you can see what it will look like before you download it.
What? No top bar customization? That is the biggest giveaway for Bootstrap and the easiest way to differentiate your site.
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)
I don't get it. What does this tool accomplish that isn't accomplished by putting the collected color definitions in a second style sheet and "cascading" it with the standard bootstrap.css? (I'm really asking not being sarcastic.)
A lot of people can't/don't use LESS, which means that a lot of precompiled rules have to be overriden in a tiresome way. For instance if you change the grid sizes you have to adjust a couple different CSS attributes. This tool generates everything in a precomputed easy to digest manner.
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.
If you can afford to be working with a bit of a moving target, don't waste your time with the current version of BS. The 2.0-wip branch is vastly more improved.
Excellent stuff! You may want to keep an eye out as Bootstrap 2 is probably going to come out any day now if the Issues tracker on Github is any indicator.
This is awesome! But I want to be able to save my preferences on it, either by permalinking them (useful-ish) OR in localStorage (better) or both (whoa yeah party)
So it could have a 'save to localStorage' button, then a list of your previous saved configurations in a side panel?
Using Rails and Twitter Bootstrap? Check out this extraction I put together from a personal project that makes it super easy to generate Bootstrap-style forms: https://github.com/potenza/form-bootstrap
A huge benefit to this tool would be instant change feedback. Specifically, given that this site uses bootstrap, it would be nice to see the changes you put in to the various input fields change the css settings for the editor itself.
[+] [-] Periodic|14 years ago|reply
I'm also amazed at how often I spot it now. Seems like it's everywhere.
[+] [-] ineedtosleep|14 years ago|reply
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.
[+] [-] iconfinder|14 years ago|reply
[+] [-] mgcross|14 years ago|reply
[+] [-] pault|14 years ago|reply
[+] [-] kennu|14 years ago|reply
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.
[+] [-] infocaptor|14 years ago|reply
I will be converting my other sites all to bootstrap. But with slight color changes it can provide a difference but consistency
[+] [-] sopooneo|14 years ago|reply
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?
[+] [-] cstejerean|14 years ago|reply
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.
[+] [-] mmahemoff|14 years ago|reply
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.
[+] [-] rmason|14 years ago|reply
[+] [-] andrewhillman|14 years ago|reply
[+] [-] j45|14 years ago|reply
[+] [-] pault|14 years ago|reply
[+] [-] nicpottier|14 years ago|reply
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)
[+] [-] bravolima|14 years ago|reply
http://groups.google.com/group/twitter-bootstrap/browse_thre...
The author wrote it in one evening which makes it even more impressive.
[+] [-] princeverma|14 years ago|reply
[+] [-] cfontes|14 years ago|reply
[+] [-] tstegart|14 years ago|reply
[+] [-] pgroves|14 years ago|reply
[+] [-] tlack|14 years ago|reply
[+] [-] mdda|14 years ago|reply
[+] [-] fourspace|14 years ago|reply
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...
[+] [-] politician|14 years ago|reply
[+] [-] latchkey|14 years ago|reply
[+] [-] Griever|14 years ago|reply
[+] [-] simonhamp|14 years ago|reply
If you do build anything using Bootstrap, please feel free to submit to Built With Bootstrap:
http://builtwithbootstrap.com/submit
[+] [-] peterhunt|14 years ago|reply
[+] [-] josscrowcroft|14 years ago|reply
So it could have a 'save to localStorage' button, then a list of your previous saved configurations in a side panel?
Excellent work!
[+] [-] josscrowcroft|14 years ago|reply
[+] [-] sjp3|14 years ago|reply
[+] [-] sdoowpilihp|14 years ago|reply
[+] [-] clyfe|14 years ago|reply