Docs: use correctly breakpoints as prefixes for utility classes, and docs content#42347
Merged
julien-deramond merged 6 commits intov6-devfrom Apr 22, 2026
Merged
Conversation
julien-deramond
force-pushed
the
v6-dev-jd-docs-refactor-use-of-breakpoints
branch
from
a3e3738 to
92289c3
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.
Reported in https://github.com/orgs/twbs/discussions/42337
Description
This PR changes the way we use the breakpoints in our pages, in the content, or in the utility classes.
I've also found some issues fixed in 9952ec1 while checking everywhere how these utilities have been used elsewhere in the docs.
Live previews