diff options
Diffstat (limited to '')
| -rw-r--r-- | site/content/docs/5.3/extend/approach.md (renamed from site/content/docs/5.2/extend/approach.md) | 6 | ||||
| -rw-r--r-- | site/content/docs/5.3/extend/icons.md (renamed from site/content/docs/5.2/extend/icons.md) | 0 |
2 files changed, 3 insertions, 3 deletions
diff --git a/site/content/docs/5.2/extend/approach.md b/site/content/docs/5.3/extend/approach.md index 4a4cc72..392aef4 100644 --- a/site/content/docs/5.2/extend/approach.md +++ b/site/content/docs/5.3/extend/approach.md @@ -4,7 +4,7 @@ title: Approach description: Learn about the guiding principles, strategies, and techniques used to build and maintain Bootstrap so you can more easily customize and extend it yourself. group: extend aliases: - - "/docs/5.2/extend/" + - "/docs/5.3/extend/" --- While the getting started pages provide an introductory tour of the project and what it offers, this document focuses on _why_ we do the things we do in Bootstrap. It explains our philosophy to building on the web so that others can learn from us, contribute with us, and help us improve. @@ -18,7 +18,7 @@ We'll dive into each of these more throughout, but at a high level, here's what - Components should be responsive and mobile-first - Components should be built with a base class and extended via modifier classes - Component states should obey a common z-index scale -- Whenever possible, prefer a HTML and CSS implementation over JavaScript +- Whenever possible, prefer an HTML and CSS implementation over JavaScript - Whenever possible, use utilities over custom styles - Whenever possible, avoid enforcing strict HTML requirements (children selectors) @@ -65,7 +65,7 @@ This principle is our first-class JavaScript API using `data` attributes. You do Lastly, our styles build on the fundamental behaviors of common web elements. Whenever possible, we prefer to use what the browser provides. For example, you can put a `.btn` class on nearly any element, but most elements don't provide any semantic value or browser functionality. So instead, we use `<button>`s and `<a>`s. -The same goes for more complex components. While we *could* write our own form validation plugin to add classes to a parent element based on an input's state, thereby allowing us to style the text say red, we prefer using the `:valid`/`:invalid` pseudo-elements every browser provides us. +The same goes for more complex components. While we _could_ write our own form validation plugin to add classes to a parent element based on an input's state, thereby allowing us to style the text say red, we prefer using the `:valid`/`:invalid` pseudo-elements every browser provides us. ## Utilities diff --git a/site/content/docs/5.2/extend/icons.md b/site/content/docs/5.3/extend/icons.md index 1e26503..1e26503 100644 --- a/site/content/docs/5.2/extend/icons.md +++ b/site/content/docs/5.3/extend/icons.md |