Bootstrap, the short story of the most popular front-end library
Posted: Thu Jan 02, 2025 10:46 am
Today, more than 70% of websites and web applications incorporate the Bootstrap library. This adoption by web developers happened in the first hours of the official release of the first version of the library.
How did Bootstrap catch the attention of web developers when it was launched and how does it continue to seduce them today? What was the web development ecosystem like before its arrival? What features have been implemented in its different versions?
The rest of the article provides you with concise answers to all these questions, in short this article traces the history of Bootstrap.
Summary
Web design long before the advent of Bootstrap
The abundance of libraries in the world of web development is not new, well before Bootstrap there was a whole range of them, for example we can cite 1KB CSS GRID and SenCSS .
But all these libraries were unable to provide a code structure for developers to follow when developing a platform.
And since they were unable to provide a directive to follow and the developers each had their own approach to development, the result was that the work of the development teams was disharmonious and there was inconsistency in their work.
Companies were then faced with significant maintenance russia whatsapp data issues and as a result they were spending a lot to maintain their platform.
This situation, which exasperated both developers and companies, would be the origin of the history of Bootstrap.
Bootstrap was born from the initiative of two Twitter engineers
In 2010 , Marc OTTO, a Twitter employee , had the idea of creating a tool capable of harmonizing the work of his company's entire development team, because they were also facing the same problems.
Marc OTTO was joined by Jacob THORTON in the development of the project, because the latter had seen the usefulness of his colleague's project and had understood that the tool would allow them to minimize inconsistencies and would provide a framework grouping the elements and functions necessary for the development of an interface.
The project was born under the name Twitter Blueprint after several months of hard work by the two engineers. For a year the tool was used within the company and the entire development team and the company's management saw the value of the library created by OTTO and THORTON, because it had limited inconsistencies, had allowed an increase in productivity and had also solved many web design problems of the time.
How did Bootstrap catch the attention of web developers when it was launched and how does it continue to seduce them today? What was the web development ecosystem like before its arrival? What features have been implemented in its different versions?
The rest of the article provides you with concise answers to all these questions, in short this article traces the history of Bootstrap.
Summary
Web design long before the advent of Bootstrap
The abundance of libraries in the world of web development is not new, well before Bootstrap there was a whole range of them, for example we can cite 1KB CSS GRID and SenCSS .
But all these libraries were unable to provide a code structure for developers to follow when developing a platform.
And since they were unable to provide a directive to follow and the developers each had their own approach to development, the result was that the work of the development teams was disharmonious and there was inconsistency in their work.
Companies were then faced with significant maintenance russia whatsapp data issues and as a result they were spending a lot to maintain their platform.
This situation, which exasperated both developers and companies, would be the origin of the history of Bootstrap.
Bootstrap was born from the initiative of two Twitter engineers
In 2010 , Marc OTTO, a Twitter employee , had the idea of creating a tool capable of harmonizing the work of his company's entire development team, because they were also facing the same problems.
Marc OTTO was joined by Jacob THORTON in the development of the project, because the latter had seen the usefulness of his colleague's project and had understood that the tool would allow them to minimize inconsistencies and would provide a framework grouping the elements and functions necessary for the development of an interface.
The project was born under the name Twitter Blueprint after several months of hard work by the two engineers. For a year the tool was used within the company and the entire development team and the company's management saw the value of the library created by OTTO and THORTON, because it had limited inconsistencies, had allowed an increase in productivity and had also solved many web design problems of the time.