Skip to content

docs: remove Bootstrap 5 references in Bootstrap 6 docs#42133

Draft
Copilot wants to merge 2 commits intov6-devfrom
copilot/remove-bootstrap-5-references
Draft

docs: remove Bootstrap 5 references in Bootstrap 6 docs#42133
Copilot wants to merge 2 commits intov6-devfrom
copilot/remove-bootstrap-5-references

Conversation

Copy link
Contributor

Copilot AI commented Mar 8, 2026

Several doc pages and components carried over "Bootstrap 5"-specific phrasing that is incorrect now that this branch targets v6.

Changes

  • Home components — removed "Bootstrap 5" brand qualifier from feature descriptions (CSSVariables.astro, ComponentUtilities.astro)
  • Footer — updated Stack Overflow community link tag from bootstrap-5 to bootstrap-6
  • ShortcodesJsDataAttributes.mdx: "As of Bootstrap 5.2.0" → "As of v5.2.0"
  • Accessibility docs — "Bootstrap 5's .visually-hidden-focusable" → "Bootstrap's .visually-hidden-focusable"
  • CSS variables docs — removed "Bootstrap 5" qualifier from component variables section; dropped stale "as of v5.2.0" note for navbar CSS variables
  • About page — rewrote History section so Bootstrap 5 is framed as a prior release and Bootstrap 6 is correctly described as the latest
  • CSS Grid docs — removed "as of v5.1.0" from opt-in callout; replaced "With Bootstrap 5, we've added" with present-tense phrasing

Intentionally preserved: footer "Bootstrap 5" project link (points to v5-dev branch), javascript.mdx "(Bootstrap 5)" annotation on BootstrapVueNext (reflects actual library compatibility), and historical prose in customize/overview.mdx that explicitly contrasts v5 and v6 behavior.

Original prompt

Find remaining references to Bootstrap 5 in our docs so we can edit them out.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: mdo <98681+mdo@users.noreply.github.com>
Copilot AI changed the title [WIP] Remove remaining references to Bootstrap 5 in documentation docs: remove Bootstrap 5 references in Bootstrap 6 docs Mar 8, 2026
Copilot finished work on behalf of mdo March 8, 2026 18:14
<h2 class="display-5 mb-3 fw-semibold lh-sm">Build and extend in real-time with CSS&nbsp;variables</h2>
<p class="lead fw-normal">
Bootstrap 5 is evolving with each release to better utilize CSS variables for global theme styles, individual
Bootstrap is evolving with each release to better utilize CSS variables for global theme styles, individual
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure it worth keeping this information as it was the specific context of adding these CSS vars in Bootstrap 5. It's been a "long time" they're here already.

As options can be passed via data attributes or JavaScript, you can append an option name to `data-bs-`, as in `data-bs-animation="{value}"`. Make sure to change the case type of the option name from “_camelCase_” to “_kebab-case_” when passing the options via data attributes. For example, use `data-bs-custom-class="beautifier"` instead of `data-bs-customClass="beautifier"`.

As of Bootstrap 5.2.0, all components support an **experimental** reserved data attribute `data-bs-config` that can house simple component configuration as a JSON string. When an element has `data-bs-config='{"delay":0, "title":123}'` and `data-bs-title="456"` attributes, the final `title` value will be `456` and the separate data attributes will override values given on `data-bs-config`. In addition, existing data attributes are able to house JSON values like `data-bs-delay='{"show":0,"hide":150}'`.
As of v5.2.0, all components support an **experimental** reserved data attribute `data-bs-config` that can house simple component configuration as a JSON string. When an element has `data-bs-config='{"delay":0, "title":123}'` and `data-bs-title="456"` attributes, the final `title` value will be `456` and the separate data attributes will override values given on `data-bs-config`. In addition, existing data attributes are able to house JSON values like `data-bs-delay='{"show":0,"hide":150}'`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could possibly remove the "As of v5.2.0" and remove the "experimental" word if it's still il v6.


<Callout type="warning">
**Heads up—our CSS Grid system is experimental and opt-in as of v5.1.0!** We included it in our documentation’s CSS to demonstrate it for you, but it’s disabled by default. Keep reading to learn how to enable it in your projects.
**Heads up—our CSS Grid system is experimental and opt-in!** We included it in our documentation’s CSS to demonstrate it for you, but it’s disabled by default. Keep reading to learn how to enable it in your projects.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably no more experimental as v5.1 was a long time ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants