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

Age	Commit message (Collapse)	Author	Files	Lines
2019-03-13	Switch to Hugo.	XhmikosR	1	-51/+0
	No more Ruby dependency and most important more than 10 times less build time (at least on Windows)!
2018-12-13	SVG accessibility fixes (#27826)	Patrick H. Lauke	1	-7/+1
	* SVG accessibility fixes - add `focusable="false"` to all SVGs, to stop IE from including the `<svg>` in its default focus cycle - completely hide decorative SVGs using `aria-hidden="true"` - add `role="img"` to meaningful/"content" SVGs, ensure they have an appropriate `<title>` and/or `aria-label` - simplify placeholder default title * Simplify usage of placeholder.svg in the docs - in most cases, no need for separate/redundant text and title (now that we make text itself part of the alternative text explicitly) - no need (expect in rare cirumstances) to describe the placeholder image (unless the look of the image is important/the actual content, as is the case with the image thumbnail class) * Simplify example.html rewriting of <svg> to <img> code sample - as the `alt` for the placeholder isn't really important, just add an ellipsis instead (otherwise, to be correct, we'd have to construct the whole "title+text" construct like we do now in the placeholder.svg itself * Change svgo configuration to retain role attribute and add/force focusable=false - regarding `focusable=false`, see https://github.com/svg/svgo/issues/1011 (which would be the "proper" SVGO fix) and the (hacky) solution https://github.com/svg/svgo/pull/817
2018-11-20	Reindent.	XhmikosR	1	-9/+11

2018-11-20	Fix placeholder image replacement.	m5o	1	-5/+22

2018-11-11	Replace `data-src` with `src="..."` in docs. (#27649)	XhmikosR	1	-1/+16

2018-10-22	Further ToC fixes.	XhmikosR	1	-1/+1

2018-10-20	Make use of jekyll-toc's `no_toc_section` class.	XhmikosR	1	-1/+1
	Requires jekyll-toc v0.8.0.
2018-07-11	Reorganize docs for easier deploys	Mark Otto	1	-0/+23
	With the current docs directory setup, I'm making too many mistakes and have to manually address path changes and directory moves on deploy. This makes for a frustrating experience developing locally and shipping releases. With this PR, we're basically back to the same setup from v3—duplicating the dist directory into our docs directory. Not the most ideal, but very straightforward for me as the release manager.