Is bootstrap really worth it?

[koeksGHT]

How is PHP dead and slow?

Did I miss the Memo?

Haters gonna hate, Facebook just took it and developed their own version

 

[Nerhzelok]

In what way does it freak you out? It's not working yet (just saying).

The icons just aren't sitting properly in the rounded blue element. See image, I fixed the right one:


Don't mean to be nitpicky, but things like this just stick out to me like a sore thumb. It's a bit of a hassle, I'd spend hours fixing
small things like this which is quite frustrating and generally a waste of time for not much gain.

 

[Pixelbender]

Browser and version please? Thanks

The icons just aren't sitting properly in the rounded blue element. See image, I fixed the right one:
View attachment 368489

Don't mean to be nitpicky, but things like this just stick out to me like a sore thumb. It's a bit of a hassle, I'd spend hours fixing
small things like this which is quite frustrating and generally a waste of time for not much gain.

 

[_kabal_]

latest versions of chrome, FireFox Developer Edition, Edge, and IE 11

So every major browser

 

[Pixelbender]

If that's the case, please visit our site in a very old outdated browser, please. :crylaugh:

We'll fix, thanks.

latest versions of chrome, FireFox Developer Edition, Edge, and IE 11

So every major browser

 

[Pixelbender]

Should be fixed. Thanks.

If that's the case, please visit our site in a very old outdated browser, please. :crylaugh:

We'll fix, thanks.

 

[Darko]

is it just me or does bootstrap make web design too easy:wtf:

No, it inspires you to be creative or just be average.

It is very hard to be proficient in both the front and backend. As mainly a backend dev, no one cares if I went and manually designed everything. They just want it to look pretty and be responsive, the logic behind the scenes is what counts.

Bootstrap makes development easy. Why shouldn't it? Who has time to slave away on making a site responsive? There is nothing average about Bootstrap.

Web design and web development are two very different things. Using bootstrap doesn't make you a designer, and neither does it make you a developer.

Bootstrap isn't going to make your website look beautiful, that's not it's purpose. It's purpose is to allow you to focus on development and functionality while providing you with easy to use classes so that you don't have to worry about screen sizes and responsiveness and browser quirks etc. It's implementation of grids, LESS and mixins make development efficient, and straightforward.

No one says you need to use the entire framework and build your site with it. You can specifically use it only for navs, or grids, or modals, or forms etc. That's why you can customize it.

The reason why all bootstrap sites look the same is because almost all of them use the free themes they find on google. Look at Wordpress. Almost all the free themes look the same.

Bootstrap comes with scaffolding to make sure your site looks the same across all browsers as well as behave the same. It's up to you whether or not you want to include the bootstrap theme style sheet.

You most certainly don't need to know JQuery to use Boostrap.

 

[MrGray]

Bootstrap is very worthwhile as long as you take the time to learn how the scaffolding works and to customize the CSS themes. It's when you use all the out of the box samples that you end up with a generic cookie cutter site that looks no different from a million other Bootstrap based sites.

 

[flippakitten]

The reason why all bootstrap sites look the same is because almost all of them use the free themes they find on google. Look at Wordpress. Almost all the free themes look the same.

Yep, 100% agreed but if a company just wants some form of web presence to show contact numbers and some basic stuff, why not the freebies. "Ouma's homemade Jam" doesn't need a R5k website but needs to have the same feel.

I am busy with a project where I initially coded all responsiveness CSS from scratch. It worked mostly but I don't have 20 devices to test it on. Decided after too many hours of "fixing" I re-coded the frontend into Bootstrap, haven't looked back.
Customized it to look like the original design but now works seamlessly across devices.

You most certainly don't need to know JQuery to use Boostrap.

You don't at all but jQuery is good to know anyway but no need for it. Bootstrap you basically just need to know how to add multiple classes to an element.

 

[skimread]

Is bootstrap worth it?

this picture best describes

 

[profeet]

Yep, 100% agreed but if a company just wants some form of web presence to show contact numbers and some basic stuff, why not the freebies. "Ouma's homemade Jam" doesn't need a R5k website but needs to have the same feel.

I am busy with a project where I initially coded all responsiveness CSS from scratch. It worked mostly but I don't have 20 devices to test it on. Decided after too many hours of "fixing" I re-coded the frontend into Bootstrap, haven't looked back.
Customized it to look like the original design but now works seamlessly across devices.

Hows the subpixels treating you? try to zoom in and out; see if stuff stays in their places...

 

[rward]

Bootstrap makes development easy.

Web design and web development are two very different things. Using bootstrap doesn't make you a designer, and neither does it make you a developer.

Bootstrap isn't going to make your website look beautiful, that's not it's purpose. It's purpose is to allow you to focus on development and functionality while providing you with easy to use classes so that you don't have to worry about screen sizes and responsiveness and browser quirks etc. It's implementation of grids, LESS and mixins make development efficient, and straightforward.

I really wish more people would read and comprehend this.

 

[rward]

I am busy with a project where I initially coded all responsiveness CSS from scratch. It worked mostly but I don't have 20 devices to test it on.

I'm sincerly curious to know how you structured your breakpoints?

Did you create a breakpoint for each device?
or did you use a fluid method?

I'm unsure why you need 20 devices to test, or is it to test the browser engine?

 

[Darko]

I really wish more people would read and comprehend this.

Spread it far and wide!

 

[flippakitten]

I'm sincerly curious to know how you structured your breakpoints?

Did you create a breakpoint for each device?
or did you use a fluid method?

I'm unsure why you need 20 devices to test, or is it to test the browser engine?

Started by ditching the mobile first idea cause that's literally the easiest part of making a website, image text, image text... scroll scroll scroll

I have 2 mobile devices, a Mac and a Windows machine (dragging chrome to test resizing) and basically tested until it worked correctly using mostly breakpoints but also a bit of the fluid thingy (the ?ver=1 is if you ever get that caching issue just change the ver number and it loads the new stylesheet).
<link rel='stylesheet' media='screen and (min-width:981px) and (max-width: 1030px)' href='css/style-mobile-large.css?ver=1' />
<link rel='stylesheet' media='screen and (min-width:790px) and (max-width: 980px)' href='css/style-mobile.css?ver=1' />
<link rel='stylesheet' media='screen and (min-width:490px) and (max-width: 789px)' href='css/style-mobile-medium.css?ver=1' />
<link rel='stylesheet' media='screen and (min-width:1px) and max-width: 489px)' href='css/style-mobile-small.css?ver=1' />

I initially had a PHP library to decide what to use where but that caused huge nightmares in updating things.

 

[Pixelbender]

A stylesheet for every breakpoint? Man, that sounds like maintenance.

Started by ditching the mobile first idea cause that's literally the easiest part of making a website, image text, image text... scroll scroll scroll

I have 2 mobile devices, a Mac and a Windows machine (dragging chrome to test resizing) and basically tested until it worked correctly using mostly breakpoints but also a bit of the fluid thingy (the ?ver=1 is if you ever get that caching issue just change the ver number and it loads the new stylesheet).
<link rel='stylesheet' media='screen and (min-width:981px) and (max-width: 1030px)' href='css/style-mobile-large.css?ver=1' />
<link rel='stylesheet' media='screen and (min-width:790px) and (max-width: 980px)' href='css/style-mobile.css?ver=1' />
<link rel='stylesheet' media='screen and (min-width:490px) and (max-width: 789px)' href='css/style-mobile-medium.css?ver=1' />
<link rel='stylesheet' media='screen and (min-width:1px) and max-width: 489px)' href='css/style-mobile-small.css?ver=1' />

I initially had a PHP library to decide what to use where but that caused huge nightmares in updating things.

 

[flippakitten]

A stylesheet for every breakpoint? Man, that sounds like maintenance.

The stylesheets are tiny max 10 classes per sheet.
It's needed so that viewing that viewing on a computer or tablet with a decent resolution doesn't feel like just a bigger version of mobile.

Mobile first is something that I feel was invented by dev houses so they don't need to do more work and can roll out more sites that all look the same.

 

[rward]

Started by ditching the mobile first idea cause that's literally the easiest part of making a website, image text, image text... scroll scroll scroll

I have 2 mobile devices, a Mac and a Windows machine (dragging chrome to test resizing) and basically tested until it worked correctly using mostly breakpoints but also a bit of the fluid thingy (the ?ver=1 is if you ever get that caching issue just change the ver number and it loads the new stylesheet).
<link rel='stylesheet' media='screen and (min-width:981px) and (max-width: 1030px)' href='css/style-mobile-large.css?ver=1' />
<link rel='stylesheet' media='screen and (min-width:790px) and (max-width: 980px)' href='css/style-mobile.css?ver=1' />
<link rel='stylesheet' media='screen and (min-width:490px) and (max-width: 789px)' href='css/style-mobile-medium.css?ver=1' />
<link rel='stylesheet' media='screen and (min-width:1px) and max-width: 489px)' href='css/style-mobile-small.css?ver=1' />

I initially had a PHP library to decide what to use where but that caused huge nightmares in updating things.

Thanks for sharing,
I also use a similar "shrink it till it breaks, add a breakpoint and make it look good" approach.

 

[Thor]

The stylesheets are tiny max 10 classes per sheet.
It's needed so that viewing that viewing on a computer or tablet with a decent resolution doesn't feel like just a bigger version of mobile.

Mobile first is something that I feel was invented by dev houses so they don't need to do more work and can roll out more sites that all look the same.

Nope.

You can combine all three those stylesheets into one and use media queries especially of it's only 10 classes per query

 

[C4Cat]

The stylesheets are tiny max 10 classes per sheet.
It's needed so that viewing that viewing on a computer or tablet with a decent resolution doesn't feel like just a bigger version of mobile.

Mobile first is something that I feel was invented by dev houses so they don't need to do more work and can roll out more sites that all look the same.

I think there are many advantages to a mobile first design strategy, but it definitely suits certain sites (content rich) more than others. I'm not sure how mobile first design leads to more sites that all look the same?