{"id":218,"date":"2011-10-04T00:22:13","date_gmt":"2011-10-04T00:22:13","guid":{"rendered":"http:\/\/blog.alexandremagno.net\/?p=218"},"modified":"2011-10-04T00:22:13","modified_gmt":"2011-10-04T00:22:13","slug":"lets-get-started-with-bootstrap","status":"publish","type":"post","link":"https:\/\/alexandremagno.net\/en\/2011\/10\/04\/lets-get-started-with-bootstrap\/","title":{"rendered":"Let’s get started with Bootstrap"},"content":{"rendered":"

Since design guides to interaction patterns, we wish to define the pattens and consistency in a web application to reuse the highest design elements as possible. Not just that, the Twitter, with the bootstrap<\/a> goes one step further and develop a framework where contains all website elements, following the twitter style, and Open Source! They called bootstrap.<\/a><\/p>\n

What the main advantages to have the Bootstraping process at beginning of the project or use the twitter boostrap<\/a>? It seens so obvious: make a pattern for all design elements growing in a scale that the layout definition step are decrease in effort to in a ideal world they don’t exist anymore, cause the front-end developer would guess with the architect the right user experience, because the library is strong enough to supply all features in the application. Use the twitter bootstrap the way it is to prototyping is something really usefull, cause is simple, clean, agnostic and with all the CSS3 features.<\/p>\n

Other great advantage is to follow the same visual consistency across projects.<\/p>\n

The bootstrap<\/a> is organic, and according with new elements it’s growing and everything aims to go out to the limit. The minimum necessary to be bootstrap working:<\/p>\n