Docs: fix and expand customize/getting-started pages#42609
Merged
Conversation
- css-variables: drop the redundant dark mode root-variables section, note light-dark() resolution, add a component-token override example, remove the stale v5.2.0 reference - javascript: remove the duplicate React example callout - migration: mention the v5-to-v6 migration skill for AI coding agents - color-modes: document the actual v6 mechanism (light-dark() + color-scheme): system preference by default with data-bs-theme override, and correct the $color-mode-type default (media-query) - components: write the Theme variants section (--bs-theme-* tokens, .theme-* classes, usage examples) - rtl: highlight the changed line in Required HTML; restore the border around the live demo by wrapping it in bd-code-snippet - optimize: add a lean-Sass commented-import example, clarify the lean-JS side-effect import, and replace the Unused CSS stub with a working PurgeCSS setup for static HTML
mdo
force-pushed
the
mdo/v6-docs-misc-fixes
branch
from
ea97968 to
6e705e3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses a batch of miscellaneous docs problems across the getting-started and customize sections. Each item is scoped to a single page/section.
getting-started/css-variables
[data-bs-theme=dark] {…}block it matched no longer carries the root variable overrides (those now live in:rootvialight-dark()), so the section had nothing meaningful to show.--bs-alert-*) and removed the stale "as of v5.2.0" / "more component usage coming in the future" wording.getting-started/javascript
.btn-*markup, import map) — all accurate, no changes needed.guides/migration
skills/bootstrap-v5-v6-migrationskill for folks migrating with an AI coding agent.customize/color-modes
Documented the actual v6 color-mode mechanism, which the page was describing incorrectly (it still read like the v5.3 mixin-based approach):
light-dark()function pluscolor-scheme: light darkon:root.data-bs-themeoverridescolor-schemeto force a mode on<html>or any subtree. Both work together — no either/or.$color-mode-typedefault (it'smedia-query, the page claimeddata), and refreshed the How it works / Enable dark mode / Building with Sass / CSS variables copy accordingly.customize/components
@mdo-doplaceholder): the--bs-theme-*token table, the.theme-*classes generated from$theme-colors, and usage/override examples.customize/rtl
[!code highlight]) on the changed<html>line..bd-examplein thebd-code-snippetwrapper that<Example>normally provides.customize/optimize
custom-bootstrap.scssexample showing how to comment out@forwardentries per build.md:d-none-style classes, safelist for JS-toggled classes).Prettier and markdownlint both pass.
Not included here (flagged for a separate decision): dropping
customize/overviewin favor of a "Via CSS" page, and drafting a v4→v6 migration skill.