Last Updated: February 25, 2016
· duiker101

Drop Bootstrap

Bootstrap is a really good product but you should not forget what is the real purpose of bootstrap: making a website quickly.
Because of this Bootstrap is not what you should use when you want to create the website for your Startup, it is something you should use at an hackathon or to put together an MVP. In both cases if the development should go any further Bootstrap should be dropped in favour of something more flexible and personalizable, other way you will end with a website that looks like too many others, with low personalization possibilities and that is now too advanced to modify easily.

A good alternative might be Zurb Foundation http://foundation.zurb.com
Or better, if it's just a grid you need,which is in the end the most important thing in Bootstrap that does not need personalization, look into something made specifically for that:


Or best solution of all, create something unique for you, so that you might learn something new, and you will also know you product better.

Bootstrap & c. are great but do not let them make you lazy and take all the fun out of creating something unique!

8 Responses
Add your response


I'm not entirely sure I agree with you on this, to me Bootstrap should be used as a base, with a few nifty features included. A CSS framework (like bootstrap, zurb, etc) should be used as a base for you to expand on. They are there to help the aid of development, not to completely do everything for you.

That is where people make the mistake in my opinion. You still need a lot of custom CSS, Javascript, etc, to make a good website even if you are using a Library.

over 1 year ago ·

@darkmantiscs But then, why not developing your own? Instead of just creating your own design,which might be easier because you might already have you way of working, you will have also to learn how the framework you are using works to then modify it. Having a base it's fine but Bootstrap add to much to be just a base, it's something already there that you should destroy to rebuild a part on your own.

Don't get me wrong, I am not against CSS Frameworks, I just think that it should be used in the correct context.

over 1 year ago ·

I disagree. I believe you are confusing the Boostrap framework with the skills of most developers/designers who use Bootstrap. What you are probably seeing are a million "Bootstrapped" sites that all look the same, and concluding that Bootstrap is creating a million look-a-likes. Nope, it's the developer/designer behind the site that is creating the look-a-like.

It is entirely possible (and desirable, in my opinion) to start with Bootstrap, tweak the variables file, override CSS classes, and end up with the highly customized site you are seeking.

Example: Bootstrap supports dropdown menus. Why go out of my way to create the semantics for my own dropdown menu? The Bootstrap folks have thought through the best way to structure a dropdown, make it cross-browser compatible, and make it interactive with javascript. If I want to tweak the color of the dropdown's border, background, drop shadow, etc, it's a piece of cake!

The same applies for typography, modals, buttons, form elements, progress bars, etc. If you are seeking a well-designed site (not Bootstrap's look and feel), think of Bootstrap as a "patterns" library.

over 1 year ago ·

@duiker101 I think that if your going to create your own that there is still a use for the premade CSS libraries. Just because they contain all the facilities to create a generic site, they should be used only as a framework which you expand to customise to create your own feel and look.

You should create your own style sheets, JavaScript functions and design.

This does not mean to say I'm against creating it all from scratch because I also think that has its benefits.

My overall synopsis is why try and recreate the wheel if you have nothing better to add to it.

over 1 year ago ·

When build a Python webapp, I usually start with something very simple, like Flask, and set up a file for each logical page in the site. Over time, as the feature set grows and the requirements are better defined, I refactor that code piece by piece into a module that eventually comprises all of the reusable business logic for the application.

I use Bootstrap the same way. It allows me to very quickly put up an initial site, then start to work implementing the (design) features my users want. As the site matures, more and more of the CSS and Javascript is moved to site-level files, and Bootstrap's features are used less. Eventually, a kind of equilibrium is reached where the site's grid layout is Bootstrap, and most everything else is either skinned to fit the design, or re-implemented in another way.

If you have a mature site, you'd need a very pressing reason to "switch to Bootstrap". If you're building a site, Bootstrap handles much of the work for you and allows you to focus on delivering a product. No one is forcing you to stay with the pre-defined styles.

over 1 year ago ·

@lyndsysimon 1 ... nicely said.
Bootstrap is there as the foundation, you can always add and customize it the way you want.

over 1 year ago ·

You have a good point of course. But I think you don't need to drop bootstrap, you just need a good graphic designer, some LESS or SASS skills and of course CSS skills and you can make anything with bootstrap. As far as the grid system is concerned, I think it's better than most of the alternatives. I also think that in the race between Twitter Bootstrap and Zurb Foundation, TB wins at the moment.

over 1 year ago ·

I just wanted to draw everyone's attention to what http://cssgrid.net now redirects to. Love it.

over 1 year ago ·