Ask HN: Twitter Bootstrap for "everyone else"?
Has anyone actually done any research into this that they'd like to share? I know that it's in theory possible to resize it, but I'm a bit wary of how that would work out in practice.
Has anyone actually done any research into this that they'd like to share? I know that it's in theory possible to resize it, but I'm a bit wary of how that would work out in practice.
If icon size is an issue, you can try using Font Awesome: http://fortawesome.github.com/Font-Awesome/. It uses a font-face for the icons rather than sprites, so you can configure further in css by adjusting size and color, whereas bootstrap's icons are limited to black/white (plus some opacity). A potential gotcha with this approach is you need to be sure you can configure your web server to send the right content-type for the font files you'll send. I had to do some minor nginx configuration to get it right for certain browsers.
There are also pre-customized resources like bootswatch (http://bootswatch.com/) if you want to get a look at some of the possibilities.
And if you clone the bootstrap repo, you can fiddle around with the base LESS stylesheets to make quick changes that affect the full system (lots of stuff in variables.less: https://github.com/twitter/bootstrap/blob/master/less/variab...) of course.
I don't think the issues you listed are particularly significant unless you know that customization is going to be too costly in terms of time.
Thanks!
You can also generate custom css from the website. Just click the customize tab in the topbar. You can bump up @baseFontSize. 16px works very well. You might also want to increase the @baseLineHeight a bit as well.
For example, I used Bootstrap for my Chrome extension's web page (http://thejakeharding.com/philanthropist/). At first glance, you probably wouldn't realize Bootstrap was used, but really, Bootstrap is pretty much the only thing that was used for styling. All I did was tweak some variables.
Also, I mostly built the extension for myself so I could easily support one of my favorite podcasts. There are only about 10 other users and since I don't really plan on advertising the extension, I doubt the user-base will ever get big enough to warrant concern from Amazon.