Hacker News Reader

Comment by pseut | Hacker News Reader

1. It's Saturday night.

2. It still looks like bootstrap. Telling people, "use bootstrap, but quickly change the fonts and colors and maybe add some images" isn't helpful. I wouldn't mind an article outlining how to use LESS to make bootstrap not look like bootstrap (which would involve, at a minimum, not using a 12-column grid, because I associate that with bootstrap more than anything else). And that seems like something developers should be interested in.

3. There are an ungodly number of blog posts that say, "use bootstrap, but change the fonts etc so that it doesn't look like bootstrap." The specific details: "use textures" for example, made the example site look worse, so it's hard to see what this article added.

View on HN

A comment like that is not helpful; bootstrap is not a bad design and would be a lot better than what you would see on most geek designed sites.

In other words, get of your high horse.

Didn't mean to come across as anti-bootstrap. I use it! It's the "tweak it" part of these articles I don't like.

Then I would like to extend my appologies for the harshness of my comment.

No worries, the comment let me know that I needed to clarify what I wrote earlier, so I appreciated it.

Can you really identify the number of columns being used by looking at a layout? And is Bootstrap the only one to use 12-columns?

I've used Bootstrap as a starting point for several apps and have modified the grid setup before, but it wasn't because I thought it looked like Bootstrap.

I probably can't guess the number of columns in the grid just by looking at the webpage, but tons of landing pages break up their explanation/details into 2 or 3 columns below the header, and (I suspect) that's a direct result of Bootstrap's 12 column grid.

And that's all fine, because it gives these pages a standard structure so that they're easy to navigate and I wouldn't suggest that people change it just for its own sake. If there's a good reason to change it, definitely do it, but otherwise leave it alone.

I'm not anti-bootstrap and, to my untrained eye, it encourages pretty good design. My only point is that it takes a lot more than changing fonts and colors to make a website look not-bootstrappy, so one should only make the changes and tweaks that have a specific purpose. Changing the colors to match other websites within the same organization makes sense, but changing the colors because, to quote the article, "that button and that menu still both look awfully Bootstrappy" doesn't make sense, unless you are a designer.

> 1. It's Saturday night.

Granted.

> 2. It still looks like bootstrap.

To you and me.

> I wouldn't mind an article outlining how to use LESS to make bootstrap not look like bootstrap (which would involve, at a minimum, not using a 12-column grid, because I associate that with bootstrap more than anything else). And that seems like something developers should be interested in.

Please write it.

Reply on news.ycombinator.com