From: Mark Otto Date: Mon, 9 Mar 2026 03:31:11 +0000 (-0700) Subject: Quick markup improvements for card (#42131) X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=194f9a02a3a3dbdf6799050331c80edf947d546d;p=thirdparty%2Fbootstrap.git Quick markup improvements for card (#42131) --- diff --git a/site/src/content/docs/components/card.mdx b/site/src/content/docs/components/card.mdx index c4e8a66137..7291364971 100644 --- a/site/src/content/docs/components/card.mdx +++ b/site/src/content/docs/components/card.mdx @@ -8,14 +8,14 @@ import { getData } from '@libs/data' Cards are flexible and extensible content containers. They include options for headers and footers, a wide variety of content, contextual background colors, and powerful display options. **Cards have no fixed width to start**, so they’ll naturally fill the full width of its parent element, or slot into your grid columns. This is easily customized with our various [sizing options](#width). - - +

Card title

Some quick example text to build on the card title and make up the bulk of the card’s content.

Go somewhere
- `} /> + + `} /> ## How it works @@ -31,6 +31,8 @@ Cards are built with as little markup and styles as possible, but still manage t - Cards can have nearly any content, including text, images, lists, and more. +- Our examples use `
`s for card elements, but you can use whatever semantic HTML makes sense for your content. Use `
` for cards that represent a thematic grouping of content, `
` for self-contained compositions like blog posts or news items, or keep using `
`s when no additional semantics are needed. + ## Content types Cards support a wide variety of content, including images, text, list groups, links, and more. Below are examples of what’s supported. @@ -56,7 +58,7 @@ Titles, text, and links within cards all have required class names for managing

Example card title

-
With a card subtitle
+

With a card subtitle

Some quick example text to build on the card title and make up the bulk of the card’s content.

Card link