HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
twbs
bootstrap
MDX2011–2025
twbs / bootstrap

bootstrap

The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.

226Distinct people
252Mentions
2Explicit recommenders
175.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.

GitHub

Where it is used

What people are saying

Make works well for me... TMPDIR=$(BASEDIR)/tmp THEME=$(BASEDIR)/theme THEME_CSS=$(THEME)/css THEME_FONT=$(THEME)/fonts THEME_JS=$(THEME)/js VER_BOOTSTRAP=3.3.6…

Alexqw85 used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:56:55 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year252 dated mentions

Observed mentions: 2011-08-19 21:13:02 UTC to 2025-10-25 07:22:00 UTC.

02040602011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 11 mentions; 3 submissions, 8 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 59 mentions; 10 submissions, 49 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 56 mentions; 5 submissions, 51 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 18 mentions; 3 submissions, 15 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 16 mentions; 1 submissions, 15 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 25 mentions; 12 submissions, 13 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 25 mentions; 6 submissions, 19 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC1138
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC591049
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC56551
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC18315
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC16115
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC251213
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC25619
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC615
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC927
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC927
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC404
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC615

From the project README

An excerpt from the repository, fetched Nov 14, 2026.

Read the project’s introduction
Bootstrap Sleek, intuitive, and powerful front-end framework for faster and easier web development. Explore Bootstrap docs » Report bug · Request feature · Blog Bootstrap 6 Our default branch is for development of our Bootstrap 6 release. Head to the v5-dev branch to view the readme, documentation, and source code for Bootstrap 5. Table of contents Quick start Status What’s included Bugs and feature requests Documentation Contributing Community Versioning Creators Thanks Copyright and license Quick start Several quick start options are available: Download the latest release Clone the repo: git clone https://github.com/twbs/bootstrap.git Install with npm: npm install bootstrap@6.0.0-alpha.1 Install with yarn: yarn add bootstrap@6.0.0-alpha.1 Install with Bun: bun add bootstrap@6.0.0-alpha.1 Install with Composer: composer require twbs/bootstrap:6.0.0-alpha.1 Install with NuGet: CSS: Install-Package bootstrap Sass: Install-Package bootstrap.sass Read the Getting started page for information on the framework contents, templates, examples, and more. Status What’s included Within the download you’ll find the following directories and files, logically grouping common assets and providing both compiled and minified variations. Download contents bootstrap/ ├── css/ │ ├── bootstrap-grid.css │ ├── bootstrap-grid.css.map │ ├── bootstrap-grid.min.css │ ├── bootstrap-grid.min.css.map │ ├── bootstrap-reboot.css │ ├── bootstrap-reboot.css.map │ ├── bootstrap-reboot.min.css │ ├── bootstrap-reboot.min.css.map │ ├── bootstrap-utilities.css │ ├── bootstrap-utilities.css.map │ ├── bootstrap-utilities.min.css │ ├── bootstrap-utilities.min.css.map │ ├── bootstrap.css │ ├── bootstrap.css.map │ ├── bootstrap.min.css │ └── bootstrap.min.css.map └── js/ ├── bootstrap.bundle.js ├── bootstrap.bundle.js.map ├── bootstrap.bundle.min.js ├── bootstrap.bundle.min.js.map ├── bootstrap.js ├── bootstrap.js.map ├── bootstrap.min.js └── bootstrap.min.js.map We provide compiled CSS and JS (bootstrap.*), as well as compiled and minified CSS and JS (bootstrap.min.*). Source maps (bootstrap.*.map) are available for use with certain browsers' developer tools. Bundled JS files (bootstrap.bundle.js and minified bootstrap.bundle.min.js) include Floating UI and Vanilla Calendar Pro. All CSS files work for both LTR and RTL layouts thanks to logical properties—simply set dir="rtl" on your HTML element. Bugs and feature requests Have a bug or a feature request? Please first read the issue guidelines and search for existing and closed issues. If your problem or idea is not addressed yet, please open a new issue. Documentation Bootstrap’s documentation, included in this repo in the root directory, is built with Astro and publicly hosted on GitHub Pages at https://getbootstrap.com/. The docs may also be run locally. Documentation search is powered by Pagefind. Running documentation locally Run npm install to install the Node.js dependencies, including Astro (the site builder). Run npm run test (or a specific npm script) to rebuild distributed CSS and JavaScript files, as well as our docs assets. From the root /bootstrap directory, run npm run docs-serve in the command line. Open http://localhost:9001 in your browser, and voilà. Learn more about using Astro by reading its documentation. Documentation for previous releases You can find all our previous releases docs on https://getbootstrap.com/docs/versions/. Previous releases and their documentation are also available for download. Contributing Please read through our contributing guidelines. Included are directions for opening issues, coding standards, and notes on development. Moreover, if your pull request contains JavaScript patches or features, you must include relevant unit tests. All HTML and CSS should conform to the Code Guide, maintained by Mark Otto. Editor preferences are available in the editor config for easy use in common text editors. Read more and download plugins at https://editorconfig.org/. Community Get updates on Bootstrap’s development and chat with the project maintainers and community members. Follow @getbootstrap on X. Read and subscribe to The Official Bootstrap Blog. Ask questions and explore our GitHub Discussions. Discuss, ask questions, and more on the community Discord or Bootstrap subreddit. Chat with fellow Bootstrappers in IRC. On the irc.libera.chat server, in the #bootstrap channel. Implementation help may be found at Stack Overflow (tagged bootstrap-5). Developers should use the keyword bootstrap on packages which modify or add to the functionality of Bootstrap when distributing through npm or similar delivery mechanisms for maximum discoverability. Versioning For transparency into our release cycle and in striving to maintain backward compatibility, Bootstrap is maintained under the Semantic Versioning guidelines. Sometimes we screw up, but we adhere to those rules whenever possible. See the Releases section of our GitHub project for changelogs for each release version of Bootstrap. Release announcement posts on the official Bootstrap blog contain summaries of the most noteworthy changes made in each release. Creators Mark Otto https://x.com/mdo https://github.com/mdo Jacob Thornton https://x.com/fat https://github.com/fat Thanks Thanks to Netlify for providing us with Deploy Previews! Sponsors Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor] Backers Thank you to all our backers! 🙏 [Become a backer] Copyright and license Code and documentation copyright 2011-2026 the Bootstrap Authors. Code released under the MIT License. Docs released under Creative Commons.
Read the full README on GitHub

What Hacker News says

16 sources
From what I can see following a quick cursory glance at the commit history page for quite a large project (https://github.com/twbs/bootstrap/commits/master) it's somewhat difficult to jump to the last page (earliest in terms of when hey were made) of commits. That is unless I'm missing something obvious, of course. Sure, you can click older a bunch of times but it doesn't seem like there's a button to jump to the last page of commits. I guess you could clone the repo and look yourself using git log but this can be something of a hassle and probably wouldn't always be possible depending on the device (I'm thinking mobile devices, tablets etc). You could probably guess a large page number, use it in the commit history URL and chop it in half repeatedly until you don't get a 404 and then repeat from there to try and find the last page of com
Read the rest
mits. Ultimately this is an issue with how GitHub's commit history is designed though.
In Show HN: First Commit – find the first commit of any GitHub project
Take a look at Bootstrap Alpha 4: https://github.com/twbs/bootstrap/tree/v4-dev/scss I don't know if reading the source code is enough, but if you try incorporating it in projects, it's easier to see how well SCSS works in practice. I really enjoy how Bootstrap sets up conventions for typography and other variables: https://github.com/twbs/bootstrap/blob/v4-dev/scss/_variable... https://github.com/twbs/bootstrap/blob/v4-dev/scss/_type.scs... There's global variables for serif, sans-serif, and mono...When prototyping a site, I sometimes change my mind over whether or not to use serif or sans-serif...with SCSS, it's a matter of just switching $font-family-base to either $font-family-serif or $font-family-sans-serif: $font-family-sans-serif: "Helvetica Neue", Helvetica, Arial, font-family-sans-serifs-serif !default; $font-fam
Read the rest
ily-serif: Georgia, "Times New Roman", Times, serif !default; $font-family-monospace: Menlo, Monaco, Consolas, "Courier New", monospace !default; $font-family-base: $font-family-sans-serif !default; I usually set a $font-family-headings variable if I decide to use a third font for headings. All font-family names are set in this file and I never have to refer to them explicitly in any of my other CSS. The elegance of setting a base font size and then having h1-h6 be multiples of that number is also a delightful convenience. And this is just the bare minimum of ways that SCSS can aid in composability...though to be honest...besides variables and the ability to nest definitions within each other...I don't habitually use all of the other really nice features, yet.
In How to Pick a Front End Web Framework
Agreed here. It's tedious to change license later on. So that's why there's tools to push it along, it's not the first time [1] As a stop gap - they can implement a contributor clause starting immediately. They can also say future commits post-[ref] are <this license> until the prior code is sunsetted. Typically there is an uppercrust where a very high percentage of the contributions lay. I haven't looked at the code (played the game all the time back in HS) but I'd bet you 90% of the code contributions are with the top 5 committers. [1] https://github.com/twbs/bootstrap/issues/2054
In The Battle for Wesnoth needs help
As many noted, disabling pinch-/doubletap-zoom results in faster click events. It is hard to implement a scaling function if you designed your page using absolute pixels as units. With relative font-sizes (em,rem,vh,vw,wmax etc) you could just change the (absolute) font-size of the body tag to resize everything else. Scaling would then be easy to do in with a little JavasSript, a plugin or by just honoring the default body font-size the browser set. The problem is, that using em makes your styles more complex. They are difficult to use, because ems are relative to the parent element for font-size and to the element itself for other attributes. If you define a font-size in em for an element you have to know, where you are going to put this element on the page. Define the font-size for a list, put a list inside a list and you messed up your
Read the rest
design. Unfortunately the other relative units are not as well supported, so most websites just use pixels. Many websites use the Bootstrap framework these days and Bootstrap uses pixels, too. Here is a discussion about the topic in their issue tracker: https://github.com/twbs/bootstrap/issues/1943 Ultimately their solution is to drop IE8 support and use rem, which is relative to the body font-size, in version 4. I look forward to that. While people could still mess up the scaling by adding their own absolute font-size declarations, Bootstrap websites will then default to being easily scalable.
In Ask HN: Is non-adjustable mobile font size a real problem?
If you use SCSS and group your CSS by, e.g. a class in the body tag and additional nesting for components, or if your component-specific styles are loaded only when necessary (e.g. HTTP/2) then not much. The purpose of these techniques, or of prefixing your class names, is to avoid naming collisions. E.g. is your list supposed to have bullets? If you just say ul { list-style: none; } you've effectively said all lists shouldn't. But you might later say the opposite and not notice until your stylesheets are all compiled together and it's a race to see which one wins on every page. Or the other example posted (above, since this comment was downvoted for unknown reasons) where you move HTML around and your stylesheets aren't in sync. Of course, prefixing isn't for everyone -- e.g. https://github.com/twbs/bootstrap/issues/1235 -- some argue yo
Read the rest
u should know all the styles on your page and how they interact, even if using a "CSS framework" and so naming collisions is just one of the things you'll have to worry about -- if you namespace, what's to prevent a naming collision even with your namespaces? :) This is also where it might be useful to point to https://speakerdeck.com/vjeux/react-css-in-js
In Show HN: CSS Quality Guide
Hey I was in the same place as you about a year ago and these are a few of the things I did to practice: Pick a CSS framework and look through the source. Bootstrap is a great one (https://github.com/twbs/bootstrap/blob/master/dist/css/boots...). You can read through their documentation and find the styles in the source to see how it works (http://getbootstrap.com/). Whenever you see something cool on a website, Right Click -> Inspect Element and figure out how they did it. Google Chrome developer tools are really awesome for this. You can toggle existing styles, add styles, edit html, etc (https://developer.chrome.com/devtools/docs/elements-styles) For detailed explanations use Mozilla Developer Network (https://developer.mozilla.org/en-US/docs/Web/CSS). They have very comprehensive write ups for every style attribute. CSS Tricks has gre
Read the rest
at write ups for specific styles and sets of styles to achieve things like centering, layout, and pretty much everything else you can think of (https://css-tricks.com/) The Codrops CSS Reference is also very, very detailed (http://tympanus.net/codrops/css_reference/) Like many other people have said, if you think up a design you can use jsfiddle, jsbin, coderpen or any in browser editor to quickly try and style something up. For larger CSS code bases you'll need to keep things readable and easily understandable for yourself and others. My team follows the Medium CSS/LESS Style Guide. It's a really excellent way to keep your code organized when you start working in larger code bases. https://medium.com/@fat/mediums-css-is-actually-pretty-fucki... Good luck! Edit I forgot to mention reading up on media queries. Media queries are extremely important for when you get into responsive design and dealing with content layout across all sorts of different screen sizes. Google has a very good write up on this (https://developers.google.com/web/fundamentals/layouts/rwd-f...) as well as CSS Tricks (https://css-tricks.com/snippets/css/media-queries-for-standa...)
In Ask HN: How do I get better at CSS?

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.