How Twitter Paired Devs and Designers to Build Bootstrap
With the recent release of a demo version of Twitter Bootstrap 2.0, Mark Otto, one of the creators of Twitter Bootstrap, attests to the power of collaborative development in his blog post on 'A List Apart'. Otto, along with Jacob Thornton, were working with a group of Twitter employees . . .
This eventually resulted in the creation of Bootstrap, which currently has over 14,000 followers on GitHub. The response to Bootstrap has been mostly positive, with one commenter highlighting the cost effectiveness of using the application, and another writing that . . .
We’ve been working with Bootstrap since it first came out. Soon our new webapp (Richmetrics.com) will be released and it’s all based on Bootstrap. Heavily modified but still, the building blocks [are] in there. -- akebrattberg
Akebrattberg's heavy modification of Bootstrap is in line with the spirit of the open source, front end application "created to help designers and developers quickly and efficiently build awesome stuff online," writes Mark Otto.
The development of Bootstrap was based on a central philosophy of pairing designers with developers in order to maintain a steady focus on not only . . .
. . . how to use a component by why you should use that particular component in Bootstrap
In both the past development and current updating of Bootstrap, the team continues to follow steps of ideation, review, implementation, and documentation so that the project continues to maintain an awareness of usability thanks to the open-source community. According to Otto, "We only implement a new feature if it doesn't confuse users or unnecessarily inflate the framework."
Hopefully, future development of Bootstrap will respond to its desktop limitations (one commenter suggested that it's not "mobile/responsive/adaptive, etc." Otto does not mention this in his post, claiming instead that
You can get a hold of the demo version of Twitter Bootstrap v2.0 below.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)