<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Idea React documentation</title><link>https://idea-react.pages.dev/</link><description>Idea React documentation with full plain-text page content.</description><language>en</language><item><title>Idea React</title><link>https://idea-react.pages.dev/</link><guid isPermaLink="true">https://idea-react.pages.dev/</guid><description>A TypeScript-first collection of advanced React components, powered by MobX. From dialogs and notifications to live code, editors, and timelines, Idea React brings the building blocks together so you can focus on your application. Get to know Idea React. Read AGENTS.md Explore component source Read API reference Currently v Built by the idea2app community. Join the discussion and help shape what comes next.</description></item><item><title>Motion</title><link>https://idea-react.pages.dev/utilities/motion/</link><guid isPermaLink="true">https://idea-react.pages.dev/utilities/motion/</guid><description>Motion Disable or apply CSS transitions and animations on individual elements with motion utilities. Bootstrap animates many components with CSS transitions and animations. The motion utilities let you disable that motion on a single element ( .transition-none , .animation-none ) or apply a small predefined animation ( .animation-shake , .animation-pop ). Transition Add .transition-none to set transition: none , so property changes apply instantly rather than animating. Hover both buttons below: the default one eases its hover color change, while the second snaps instantly. Default No hover transition Animation Disable an animation Add .animation-none to set animation: none , which stops any running keyframe animation such as a spinner. Shake Add .animation-shake to play a brief horizontal shake once. It pairs well with invalid form feedback—apply it to a field or toggle it when validation fails to draw attention to what needs fixing. Pop Add .animation-pop to scale an element in with a slight overshoot. It works well for content that appears dynamically, such as a badge whose count just updated. New Reduced motion .transition-none and .animation-none always apply, regardless of a user's motion preference. Bootstrap already respects prefers-reduced-motion for its built-in transitions, and automatically disables the decorative .animation-shake and .animation-pop effects when reduced motion is preferred. CSS Components declare motion through duration and timing tokens. For example, the .fade class uses --bs-transition-fade-duration and --bs-transition-fade-timing ; .collapse uses --bs-transition-collapse-property , --bs-transition-collapse-duration , and --bs-transition-collapse-timing . Dialog, drawer, and menu share an easing token at the root level, so one override can restyle all three. Fade wrapper Bootstrap's .fade class applies an opacity transition. Add .show to make the content visible. Idea React's Fade wrapper applies these classes to its child without adding a DOM element. Set in to show the child. When in is false or omitted, the child remains mounted but is transparent and still occupies its layout space. This content fades in using Bootstrap's CSS transition. Fade only applies CSS classes; it does not mount or unmount its child or manage enter/exit callbacks. Use it when the visibility state is already owned by your component or model. Override the fade duration and easing with the Bootstrap CSS tokens: .custom-fade { --bs-transition-fade-duration: 300ms; --bs-transition-fade-timing: ease-in-out; } A slower fade transition.</description></item><item><title>Aspect ratio</title><link>https://idea-react.pages.dev/utilities/aspect-ratio/</link><guid isPermaLink="true">https://idea-react.pages.dev/utilities/aspect-ratio/</guid><description>Aspect ratio Make elements maintain specific aspect ratios. Perfect for handling videos, slideshow embeds, and more based on the width of the parent. Idea React provides the Ratio wrapper for Bootstrap's aspect-ratio utilities. Set aspectRatio to auto , 1x1 , 4x3 , 16x9 , or 21x9 , and use as to apply the utility directly to an element such as an iframe . The default is 1x1 . Ratio supports embedded media and other elements through its as prop. Example Apply a ratio to an embedded video. The Ratio root is the iframe itself, so the browser sizes it according to the selected aspect ratio. Swap aspectRatio for another predefined value: Custom ratios Pass a CSS aspect ratio such as &quot;2 / 1&quot; to aspectRatio for a custom ratio. The wrapper uses Bootstrap's --bs-ratio custom property and the ratio-auto utility. You can also override that property at breakpoints in your own CSS. 2×1 For example, define a breakpoint-specific ratio in your stylesheet: .custom-ratio { --bs-ratio: 4 / 3; } @media (min-width: 768px) { .custom-ratio { --bs-ratio: 2 / 1; } } Apply the class along with aspectRatio=&quot;auto&quot; : 4×3, then 2×1</description></item><item><title>Grid system</title><link>https://idea-react.pages.dev/layout/grid/</link><guid isPermaLink="true">https://idea-react.pages.dev/layout/grid/</guid><description>Grid system Use our powerful mobile-first flexbox grid to build layouts of all shapes and sizes thanks to a twelve column system, six default responsive tiers, CSS custom properties, and dozens of predefined classes. Idea React provides the Container , Row , and Col wrappers for these examples. Set fluid to true for a full-width container or pass a breakpoint to make it responsive. Use the xs , sm , md , lg , xl , and 2xl props on Row and Col . Example Bootstrap's grid system uses a series of containers, rows, and columns to layout and align content. It's built with flexbox and is fully responsive. Below is an example and an in-depth explanation for how the grid system comes together. Column Column Column The above example creates three equal-width columns across all devices and viewports using the default Col sizing. The Container centers them in the page. How it works Breaking it down, here's how the grid system comes together: Our grid supports six responsive breakpoints. Breakpoints are based on min-width media queries, meaning a breakpoint prop affects that breakpoint and all those above it (e.g., sm={4} on Col applies from sm upward). Use responsive props to control container and column sizing and behavior. Containers center and horizontally pad your content. Use Container with its default sizing, set fluid for full width, or pass a breakpoint such as fluid=&quot;md&quot; for responsive container sizing. Rows are wrappers for columns. Each column has horizontal padding (called a gutter) for controlling the space between them. This padding is then counteracted on the rows with negative margins to ensure the content in your columns is visually aligned down the left side. Set responsive column counts with Row props; use gutter utilities through className to change the spacing of your content. Columns are incredibly flexible. There are 12 template columns available per row, allowing you to create different combinations of elements that span any number of columns. Set a Col breakpoint prop (for example xs={4} ) to span a number of columns. Widths are set in percentages so you always have the same relative sizing. Gutters are also responsive and customizable. Pass gutter utilities through Row 's className to adjust horizontal, vertical, or all gutters at each breakpoint, including removing gutters entirely. Customize the grid with Props, utilities, and CSS custom properties. Use the layout components for semantic markup, responsive Props for column sizes, and gutter utilities for spacing. No preprocessor configuration is required. Be aware of the limitations and bugs around flexbox, like the inability to use some HTML elements as flex containers. Grid options Bootstrap's grid system can adapt across all six default breakpoints, and any breakpoints you customize. The six default grid tiers are as follows: Extra small (xs) Small (sm) Medium (md) Large (lg) Extra large (xl) Extra extra large (2xl) As noted above, each of these breakpoints have their own container, unique class prefix, and modifiers. Here's how the grid changes across these breakpoints: xs sm md lg xl 2xl Container max-width None (auto) 540px 720px 960px 1200px 1440px Class prefix .col- .sm:col- .md:col- .lg:col- .xl:col- .2xl:col- of columns 12 Gutter width 1.5rem (.75rem on left and right) Custom gutters Yes Nestable Yes Column ordering Yes Auto-layout columns Utilize breakpoint-specific column classes for easy column sizing without an explicit numbered class like .sm:col-6 . Equal-width For example, here are two grid layouts that apply to every device and viewport, from xs to 2xl . Add any number of unit-less classes for each breakpoint you need and every column will be the same width. 1 of 2 2 of 2 1 of 3 2 of 3 3 of 3 Setting one column width Auto-layout for flexbox grid columns also means you can set the width of one column and have the sibling columns automatically resize around it. You may use predefined grid classes, grid mixins, or inline widths. Note that the other columns will resize no matter the width of the center column. 1 of 3 2 of 3 (wider) 3 of 3 1 of 3 2 of 3 (wider) 3 of 3 Variable width content Use the auto value on a breakpoint prop to size columns based on the natural width of their content. 1 of 3 Variable width content 3 of 3 1 of 3 Variable width content 3 of 3 Responsive classes Bootstrap's grid includes six tiers of predefined classes for building complex responsive layouts. Customize the size of your columns on extra small, small, medium, large, or extra large devices however you see fit. All breakpoints For grids that are the same from the smallest of devices to the largest, use the xs prop or leave it out for an equal-width column. col col col col col-8 col-4 Stacked to horizontal Using a single set of sm props, you can create a basic grid system that starts out stacked and becomes horizontal at the small breakpoint ( sm ). sm:col-8 sm:col-4 sm:col sm:col sm:col Mix and match Don't want your columns to simply stack in some grid tiers? Use a combination of different props for each tier as needed. See the example below for a better idea of how it all works. .md:col-8 .col-6 .col-6 Offsets and ordering Pass a responsive object to a Col breakpoint prop to combine a column span with an offset or visual order. Each option is independent, so you can also set only an offset or order at a breakpoint. Order accepts a number, &quot;first&quot; , or &quot;last&quot; . Unordered column Offset and reordered column Offset auto-layout column First on small screens and up Row columns Set xs , sm , md , lg , xl , or 2xl on Row to control the number of columns at each breakpoint. This is a shortcut for setting each column's width; use xs=&quot;auto&quot; to give columns their natural width. Column Column Column Column Column Column Column Column Column Column Column Column Column Column Column Column Nesting To nest your content with the default grid, add a new Row and set of columns within an existing column. Nested rows should include a set of columns that add up to 12 or fewer (it is not required that you use all 12 available columns). Level 1: .sm:col-3 CSS Use Container , Row , and Col Props to select responsive layouts from the compiled stylesheet. Adjust spacing with gutter utilities and scope any additional CSS custom property overrides to your layout. See the upstream grid CSS for the underlying layout reference.</description></item><item><title>Guides</title><link>https://idea-react.pages.dev/guides/</link><guid isPermaLink="true">https://idea-react.pages.dev/guides/</guid><description>Guides Install Idea React, then choose a guide to integrate it into your project. Guide Description Install Install the npm package or load Bootstrap CSS from a supported CDN. Approach Understand styling, component patterns, and View Model architecture. Migration Replace removed components and update imports from earlier releases. Parcel Configure a Parcel React app to compile TypeScript and stage-3 decorators. Vite Configure a Vite app with SWC. Webpack Bundle a React app and compile MobX stage-3 decorators with Babel. Next.js Create a statically exported Next.js app with Idea React. Ecosystem Explore the open-source projects that work alongside Idea React.</description></item><item><title>Bootstrap and Webpack</title><link>https://idea-react.pages.dev/guides/webpack/</link><guid isPermaLink="true">https://idea-react.pages.dev/guides/webpack/</guid><description>Bootstrap and Webpack What is Webpack? Webpack is a JavaScript module bundler that combines application modules and their dependencies into browser-ready assets. This guide sets up a React and TypeScript application and configures Babel to compile the ECMAScript decorators (stage-3) used by MobX. Setup Create a project folder and initialize its package manifest: mkdir my-project cd my-project pnpm init Install Idea React and its runtime peers, plus Webpack, Babel, and the CSS loader chain: pnpm add idea-react@next react react-dom mobx mobx-react bootstrap pnpm add -D webpack webpack-cli webpack-dev-server html-webpack-plugin pnpm add -D babel-loader @babel/core @babel/preset-env @babel/preset-react pnpm add -D @babel/preset-typescript @babel/plugin-proposal-decorators pnpm add -D css-loader style-loader Use idea-react without @next after a stable release. Project structure Create Babel and Webpack configuration files and a TypeScript React entry point: my-project/ ├── babel.config.json ├── package.json ├── src/ │ ├── index.html │ └── main.tsx └── webpack.config.cjs Configure Webpack Set up the development server, HTML template, TSX transpilation, and CSS loaders in webpack.config.cjs : const path = require('node:path'); const HtmlWebpackPlugin = require('html-webpack-plugin'); module.exports = { mode: 'development', entry: './src/main.tsx', output: { filename: 'main.js', path: path.resolve(__dirname, 'dist'), clean: true }, devServer: { static: path.resolve(__dirname, 'dist'), port: 8080, hot: true }, plugins: [new HtmlWebpackPlugin({ template: './src/index.html' })], module: { rules: [ { test: /\.[jt]sx?$/, exclude: /node_modules/, use: 'babel-loader' }, { test: /\.css$/i, use: ['style-loader', 'css-loader'] } ] }, resolve: { extensions: ['.tsx', '.ts', '.jsx', '.js'] } }; Add development and production scripts in package.json : { &quot;scripts&quot;: { &quot;start&quot;: &quot;webpack serve&quot;, &quot;build&quot;: &quot;webpack build --mode=production&quot; } } Create src/index.html with a mount point for React: &lt;!doctype html> &lt;html lang=&quot;en&quot;> &lt;head> &lt;meta charset=&quot;utf-8&quot; /> &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1&quot; /> &lt;title>Idea React with Webpack&lt;/title> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/idea-react@next/dist/index.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap-icons@1.13.2/font/bootstrap-icons.css&quot; /> &lt;/head> &lt;body> &lt;div id=&quot;root&quot;>&lt;/div> &lt;/body> &lt;/html> Run the local server: pnpm start Import Bootstrap Use Babel's decorators plugin to compile the standard decorator syntax supported by TypeScript 5 and used by MobX. Select the stage-3 2023-11 proposal version and do not enable TypeScript's legacy experimentalDecorators mode. Put this in babel.config.json : { &quot;assumptions&quot;: { &quot;setPublicClassFields&quot;: false }, &quot;presets&quot;: [ [&quot;@babel/preset-env&quot;, { &quot;targets&quot;: &quot;defaults&quot; }], [&quot;@babel/preset-react&quot;, { &quot;runtime&quot;: &quot;automatic&quot; }], &quot;@babel/preset-typescript&quot; ], &quot;plugins&quot;: [[&quot;@babel/plugin-proposal-decorators&quot;, { &quot;version&quot;: &quot;2023-11&quot; }]] } The class-field assumption preserves the standard field behavior required by MobX decorators. The HTML page loads the Idea React stylesheet from the CDN. Import Bootstrap's compiled stylesheet and a component from Idea React's public package entry point in src/main.tsx : import 'bootstrap/dist/css/bootstrap.min.css'; import { createRoot } from 'react-dom/client'; import { Button } from 'idea-react'; createRoot(document.getElementById('root')!).render( &lt;Button variant=&quot;solid&quot; theme=&quot;primary&quot;> Hello, Idea React and Webpack! &lt;/Button> ); The CSS loader chain handles both stylesheets. Idea React's React wrappers provide component behavior, so Bootstrap's JavaScript bundle is not needed. Create the production bundle with: pnpm build Production optimizations Depending on the deployment and Content Security Policy, production builds can extract styles and data-URI SVGs into static assets. Extracting CSS style-loader inserts CSS into the page at runtime. To emit a separate stylesheet, install mini-css-extract-plugin : pnpm add -D mini-css-extract-plugin In the production Webpack configuration, add the plugin and replace style-loader in the CSS rule: const MiniCssExtractPlugin = require('mini-css-extract-plugin'); module.exports = { plugins: [new HtmlWebpackPlugin({ template: './src/index.html' }), new MiniCssExtractPlugin()], module: { rules: [ { test: /\.css$/i, use: [MiniCssExtractPlugin.loader, 'css-loader'] } ] } }; Keep style-loader in the development configuration. The extraction plugin writes a separate CSS asset for production; confirm the generated HTML includes its stylesheet link. Extracting SVG files Bootstrap CSS can contain inline SVG data URIs. If the deployment's Content Security Policy blocks data: images, use Webpack's asset modules to emit those SVGs as files: { mimetype: 'image/svg+xml', scheme: 'data', type: 'asset/resource', generator: { filename: 'icons/[hash].svg' } }</description></item><item><title>Bootstrap and Vite</title><link>https://idea-react.pages.dev/guides/vite/</link><guid isPermaLink="true">https://idea-react.pages.dev/guides/vite/</guid><description>Bootstrap and Vite What is Vite? Vite is a frontend build tool focused on a fast development server and optimized production bundles. This guide uses Vite with React, TypeScript, and the SWC transform settings used by the Idea React documentation site. Setup Create a project directory and initialize its package manifest: mkdir my-project cd my-project pnpm init Install Idea React and its runtime peers, along with Vite and the SWC-based TypeScript transformer: pnpm add idea-react@next react react-dom mobx mobx-react pnpm add -D vite unplugin-swc @swc/core typescript @types/react @types/react-dom Use idea-react without @next after a stable release. Project structure Create an HTML entry point, a React module, and the Vite and SWC configuration files: my-project/ ├── index.html ├── package.json ├── src/ │ └── main.tsx ├── swc.config.mts └── vite.config.ts Configure Vite Register the SWC plugin in vite.config.ts : import swc from 'unplugin-swc'; import { defineConfig } from 'vite'; import { swcOptions } from './swc.config.mts'; export default defineConfig({ plugins: [swc.vite({ ...swcOptions, tsconfigFile: false })] }); SWC compiles TypeScript, TSX, and the ECMAScript decorator (stage-3) used by MobX; these options transform source files rather than type-checking them. Add swc.config.mts : export const swcOptions = { jsc: { target: 'es2015', parser: { syntax: 'typescript', tsx: true, decorators: true }, transform: { decoratorVersion: '2022-03', useDefineForClassFields: true, react: { runtime: 'automatic' } } } }; In index.html , add the mount point, load the Bootstrap styles, and point to the TSX module: &lt;!doctype html> &lt;html lang=&quot;en&quot;> &lt;head> &lt;meta charset=&quot;utf-8&quot; /> &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1&quot; /> &lt;title>Idea React with Vite&lt;/title> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap@6.0.0-alpha.1/dist/css/bootstrap.min.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap-icons@1.13.2/font/bootstrap-icons.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/idea-react@next/dist/index.css&quot; /> &lt;/head> &lt;body> &lt;div id=&quot;root&quot;>&lt;/div> &lt;script type=&quot;module&quot; src=&quot;/src/main.tsx&quot;>&lt;/script> &lt;/body> &lt;/html> Add scripts to package.json : { &quot;scripts&quot;: { &quot;dev&quot;: &quot;vite&quot;, &quot;build&quot;: &quot;vite build&quot;, &quot;preview&quot;: &quot;vite preview&quot; } } Run the development server or build the application: pnpm dev pnpm build pnpm preview Import Bootstrap The stylesheets loaded by index.html provide the compiled Bootstrap and Idea React component styles. Import the library from its public package entry point in src/main.tsx : import { createRoot } from 'react-dom/client'; import { Button, Container } from 'idea-react'; createRoot(document.getElementById('root')!).render( &lt;Container> &lt;h1>Hello, Idea React and Vite!&lt;/h1> &lt;Button variant=&quot;solid&quot; theme=&quot;primary&quot;> Get started &lt;/Button> &lt;/Container> ); Idea React's React components provide their own behavior, so importing Bootstrap's JavaScript bundle is unnecessary. Starter template To skip the manual setup, start from Vite-React-MobX-Bootstrap-ts , a React project scaffold based on TypeScript, MobX and Bootstrap, powered by Vite. Its live demo shows the result.</description></item><item><title>Bootstrap and Parcel</title><link>https://idea-react.pages.dev/guides/parcel/</link><guid isPermaLink="true">https://idea-react.pages.dev/guides/parcel/</guid><description>Bootstrap and Parcel What is Parcel? Parcel is a web application bundler designed to simplify development with zero-configuration defaults. It supports the TypeScript and TSX files used by Idea React. Setup This guide starts a Parcel project from scratch. Install Node.js and use a terminal to create the project directory and initialize its package manifest: mkdir my-project cd my-project pnpm init Add Parcel and its TypeScript transformer as development dependencies, then install Idea React and its peer dependencies: pnpm add -D parcel @parcel/config-default @parcel/transformer-typescript-tsc typescript pnpm add idea-react@next react react-dom mobx mobx-react Use idea-react without @next after a stable release. Project structure Create the HTML entry point, a TSX module, and the Parcel and TypeScript configuration files: my-project/ ├── .parcelrc ├── package.json ├── tsconfig.json └── src/ ├── index.html └── main.tsx Configure Parcel Parcel can serve an HTML entry directly. Its TypeScript transformer compiles TS and TSX, including the standard stage-3 decorators used by MobX. Configure .parcelrc to use the TypeScript compiler transformer: { &quot;extends&quot;: &quot;@parcel/config-default&quot;, &quot;transformers&quot;: { &quot;*.{ts,tsx}&quot;: [&quot;@parcel/transformer-typescript-tsc&quot;] } } Set TypeScript to emit automatic React JSX and preserve standard class-field semantics in tsconfig.json : { &quot;compilerOptions&quot;: { &quot;target&quot;: &quot;ES2020&quot;, &quot;module&quot;: &quot;ES2020&quot;, &quot;moduleResolution&quot;: &quot;bundler&quot;, &quot;useDefineForClassFields&quot;: true, &quot;jsx&quot;: &quot;react-jsx&quot; } } useDefineForClassFields preserves the field semantics required by MobX's stage-3 decorators. For the complete set of repository options. Point Parcel to the HTML entry in package.json and add development and production scripts: { &quot;source&quot;: &quot;src/index.html&quot;, &quot;scripts&quot;: { &quot;dev&quot;: &quot;parcel --open&quot;, &quot;build&quot;: &quot;parcel build --public-url .&quot; } } In src/index.html , provide a mount point and the Bootstrap, Bootstrap Icons, and Idea React stylesheets: &lt;!doctype html> &lt;html lang=&quot;en&quot;> &lt;head> &lt;meta charset=&quot;utf-8&quot; /> &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1&quot; /> &lt;title>Idea React with Parcel&lt;/title> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap@6.0.0-alpha.1/dist/css/bootstrap.min.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap-icons@1.13.2/font/bootstrap-icons.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/idea-react@next/dist/index.css&quot; /> &lt;/head> &lt;body> &lt;div id=&quot;root&quot;>&lt;/div> &lt;script type=&quot;module&quot; src=&quot;./main.tsx&quot;>&lt;/script> &lt;/body> &lt;/html> Start the development server and create a static build with: pnpm dev pnpm build Import Bootstrap The CDN links above provide the compiled component styles. Import Idea React from its public package entry point in src/main.tsx : import { createRoot } from 'react-dom/client'; import { Button } from 'idea-react'; createRoot(document.getElementById('root')!).render( &lt;Button variant=&quot;solid&quot; theme=&quot;primary&quot;> Hello, Idea React and Parcel! &lt;/Button> ); Idea React's React components provide their own behavior, so importing Bootstrap's JavaScript bundle is unnecessary. For a ready-to-use project scaffold, clone the React, MobX, and Bootstrap template and adapt it to your application: cd my-project git init pnpx git-utility download https://github.com/idea2app/React-MobX-Bootstrap-ts master pnpm install</description></item><item><title>Next.js</title><link>https://idea-react.pages.dev/guides/next/</link><guid isPermaLink="true">https://idea-react.pages.dev/guides/next/</guid><description>Next.js Create a statically exported Next.js application with Idea React. This guide uses ViNext, a Vite implementation of the Next.js application model, and follows the documentation site's SWC decorator transform and static-export configuration. Setup Create a project and install Idea React with its React and MobX peers: mkdir my-project cd my-project pnpm init pnpm add idea-react@next react react-dom mobx mobx-react vinext pnpm add -D vite unplugin-swc @swc/core typescript @types/react @types/react-dom Use idea-react without @next after a stable release. Project structure Create an App Router route, a shared root layout, and Vite and SWC configuration: my-project/ ├── app/ │ ├── layout.tsx │ └── page.tsx ├── next.config.ts ├── package.json ├── swc.config.mts └── vite.config.ts Configure Next.js Register ViNext, the Vite implementation used in this guide, and SWC in vite.config.ts : import swc from 'unplugin-swc'; import vinext from 'vinext'; import { defineConfig } from 'vite'; import { swcOptions } from './swc.config.mts'; export default defineConfig({ plugins: [swc.vite({ ...swcOptions, tsconfigFile: false }), vinext()] }); SWC compiles the TypeScript, TSX, and ECMAScript decorator (stage-3) used by MobX. This config transforms source files; it does not type-check them. Add swc.config.mts : export const swcOptions = { jsc: { target: 'es2015', parser: { syntax: 'typescript', tsx: true, decorators: true }, transform: { decoratorVersion: '2022-03', useDefineForClassFields: true, react: { runtime: 'automatic' } } } }; ViNext reads the Next.js-compatible options from next.config.ts . Set output to export to produce a site that can be served without a Node.js process: const nextConfig = { output: 'export', trailingSlash: true }; export default nextConfig; Add development, build, and preview scripts to package.json : { &quot;scripts&quot;: { &quot;dev&quot;: &quot;vite dev&quot;, &quot;build&quot;: &quot;vite build&quot;, &quot;start&quot;: &quot;vite preview&quot; } } Create the application Load Bootstrap CSS, Bootstrap Icons, and the Idea React stylesheet from the shared layout: import { PropsWithChildren } from 'react'; export default function RootLayout({ children }: PropsWithChildren) { return ( &lt;html lang=&quot;en&quot;> &lt;head> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap@6.0.0-alpha.1/dist/css/bootstrap.min.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap-icons@1.13.2/font/bootstrap-icons.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/idea-react@next/dist/index.css&quot; /> &lt;/head> &lt;body>{children}&lt;/body> &lt;/html> ); } Render a library component from app/page.tsx : import { Button, Container } from 'idea-react'; export default function Page() { return ( &lt;Container> &lt;h1>Hello, Idea React and Next.js!&lt;/h1> &lt;Button variant=&quot;solid&quot; theme=&quot;primary&quot;> Get started &lt;/Button> &lt;/Container> ); } The React components handle their own behavior, so Bootstrap's JavaScript bundle is not required. Build and deploy Run the app locally, build it, then preview the generated site: pnpm dev pnpm build pnpm start Deploy the static files from dist/client/ to a static host. If the site is served from a subdirectory, configure a matching base path and verify that asset and route URLs include it.</description></item><item><title>Migration</title><link>https://idea-react.pages.dev/guides/migration/</link><guid isPermaLink="true">https://idea-react.pages.dev/guides/migration/</guid><description>Migration Import public components from idea-react rather than internal source paths. v1 to v2 Removed APIs Data-backed Table, List and Form components moved to MobX RESTful table , while Open Map and its model moved to Open React Map . These are migrations, not drop-in replacements: v1 API v2 migration FilePicker Use file components in MobX RESTful table ; check its current uploader API for prop changes FileUploader Use file components in MobX RESTful table ; check its current uploader API for prop changes MultipleFileUploader Use file components in MobX RESTful table ; check its current uploader API for prop changes FilterInput Use searchable input facilities in MobX RESTful table IdeaForm Use Form and the current REST form APIs in MobX RESTful table IdeaInfo Use data-display facilities in MobX RESTful table IdeaTable Use the current REST table APIs in MobX RESTful table PaginationBar Use the pager in MobX RESTful table , or Pagination for presentation only ScrollBoundary Use the scroll boundary/list components in MobX RESTful table AddressPicker Build an application-level location picker with Open React Map MapData Rework location data for Open React Map ; the old embedded-map message API is not retained OpenMap Migrate the component and its map, coordinate, marker and location types to Open React Map Added components Countdown HorizontalMarquee LiveTSX ScrollNav ShareBox TextTruncate Time Timeline Toast UserRank VerticalMarquee ZodiacBar Dialog input The Promise-based dialog model gained a typed input parameter. Pass optional input to open(input) ; existing calls to open() remain valid. In v3, the model is named DialogBox . v2 to v3 Removed components v2 component v3 alternative Select Combobox , or FormSelect for a native select Option ComboboxOption Editor React Bootstrap Editor for HTML editing; use an Editor.js integration for blocks EditorHTML MarkdownView only after converting the Editor.js data to Markdown MarkdownView accepts Markdown text; it does not convert or render Editor.js block data. The recommended React Bootstrap Editor edits HTML, not Editor.js block data. Install it separately: npm install react-bootstrap-editor Existing Editor.js documents require explicit conversion or an application-owned Editor.js integration. Renamed APIs v2 API v3 API Dialog DialogBox DialogClose DialogBoxClose DialogProps DialogBoxProps Bootstrap CSS Idea React v2 uses Bootstrap 5; v3 targets Bootstrap 6. Replace the Bootstrap 5 stylesheet with the Bootstrap 6 stylesheet used by your application. Idea React components do not bundle third-party CSS, so load both Bootstrap and the library stylesheet in the document head: &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap@6.0.0-alpha.1/dist/css/bootstrap.min.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/idea-react/dist/style.css&quot; /> Bootstrap utility names and component styles may differ between major versions; update custom classes and selectors along with the stylesheet. React-Bootstrap v2 to Idea React v3 React-Bootstrap v2 targets Bootstrap 5, while Idea React v3 targets Bootstrap 6. The table lists only component and prop names that differ; same-named components are omitted. React-Bootstrap v2 API Idea React v3 API Modal Dialog Modal.Header DialogHeader Modal.Title DialogTitle Modal.Body DialogBody Modal.Footer DialogFooter Modal.show / Modal.onHide Dialog.open / Dialog.onClose Offcanvas Drawer Offcanvas.Header DrawerHeader Offcanvas.Title DrawerTitle Offcanvas.Body DrawerBody Offcanvas.show / Offcanvas.onHide Drawer.open / Drawer.onDismiss Dropdown Menu Dropdown.show / Dropdown.onToggle Menu manages its open state; Menu.onOpenChange reports changes Dropdown.Toggle Menu.label and Menu.toggleProps Dropdown.Item MenuItem Dropdown.Divider MenuDivider Dropdown.Header MenuHeader Form.Control FormControl Form.Control.size / Form.Select.size FormControl.controlSize / FormSelect.controlSize Form.Select FormSelect Form.Check FormCheck Form.Check with type=&quot;switch&quot; FormSwitch Form.Group FormGroup or FormField Form.Label FormLabel ProgressBar Progress ProgressBar.now Progress.value Idea React uses flat named exports instead of React-Bootstrap's nested component properties. A Modal 's show / onHide pair does not transfer directly: control Dialog with open and update it from onClose . See the Dialog and Form guides for current props and examples. Dependencies and stylesheets Remove React-Bootstrap and install Idea React with the required peer dependencies: npm uninstall react-bootstrap npm install idea-react mobx mobx-react react react-dom react-element-to-jsx-string web-utility Load Bootstrap 6 and Idea React CSS separately; replace any Bootstrap 5 stylesheet with the Bootstrap 6 version: &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap@6.0.0-alpha.1/dist/css/bootstrap.min.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/idea-react/dist/style.css&quot; /> If the application uses Icon , also load the Bootstrap Icons font stylesheet.</description></item><item><title>Install</title><link>https://idea-react.pages.dev/guides/install/</link><guid isPermaLink="true">https://idea-react.pages.dev/guides/install/</guid><description>Install Install Idea React from an NPM ecosystem package manager and load Bootstrap's CSS from either jsDelivr or unpkg . Install Add Idea React and its React and MobX peer dependencies to your project: npm install idea-react@next react react-dom mobx mobx-react Equivalent commands are available for other NPM ecosystem package managers: pnpm add idea-react@next react react-dom mobx mobx-react yarn add idea-react@next react react-dom mobx mobx-react bun add idea-react@next react react-dom mobx mobx-react The current prerelease is published on the next dist-tag. After a stable release, install idea-react without @next . React and React DOM render the components; MobX and MobX React are required by stateful components. CodeBlock and LiveTSX also require the react-element-to-jsx-string peer dependency. Import components from the package's public entry point: import { FC } from 'react'; import { Button } from 'idea-react'; export const SaveButton: FC = () => ( &lt;Button variant=&quot;solid&quot; theme=&quot;primary&quot;> Save &lt;/Button> ); CDN Use the version-pinned Bootstrap stylesheet from either supported CDN provider. Bootstrap's CSS provides the design tokens and styles used by Idea React; the component package's stylesheet adds its own component styles. Bootstrap's JavaScript bundle is not required. Provider Stylesheet jsDelivr bootstrap.min.css unpkg bootstrap.min.css Add Bootstrap, Bootstrap Icons, and Idea React styles to the document &lt;head> : &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap@6.0.0-alpha.1/dist/css/bootstrap.min.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap-icons@1.13.2/font/bootstrap-icons.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/idea-react@next/dist/index.css&quot; /> Keep the Bootstrap CSS version aligned with the version supported by Idea React. If you choose jsDelivr instead, use the same Bootstrap version and change the stylesheet URL to the jsDelivr entry in the table.</description></item><item><title>Ecosystem</title><link>https://idea-react.pages.dev/guides/ecosystem/</link><guid isPermaLink="true">https://idea-react.pages.dev/guides/ecosystem/</guid><description>Ecosystem Idea React works alongside a family of open-source libraries and project scaffolds from the same organization. Each entry links to its source code and GitHub topics, and shows the latest NPM release when the project is published as a package. Project Topics NPM Description</description></item><item><title>Approach</title><link>https://idea-react.pages.dev/guides/approach/</link><guid isPermaLink="true">https://idea-react.pages.dev/guides/approach/</guid><description>Approach Understand the principles behind Idea React so you can compose, customize, and extend its components without taking over their internal behavior. Start with the installation guide for dependencies and stylesheets, then use this guide when building your own components. CSS Idea React uses Bootstrap for its visual foundation and React with MobX for interactive behavior. Keep styling, rendering, and business decisions separate rather than building a second styling system or attaching a second JavaScript controller to the same component. Prefer CSS custom properties for visual customization and Bootstrap utilities for layout, spacing, typography, and responsive behavior. Keep remaining application styles in CSS Modules. The library uses LESS internally, but does not expose a consumer-facing LESS customization API. Future customization needs should be met with public CSS variables first. Third-party component styles are not bundled into the library. Load Bootstrap, any required icon font or widget stylesheet, and Idea React's own styles once in your document's shared head: &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap@6.0.0-alpha.1/dist/css/bootstrap.min.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/bootstrap-icons@1.13.2/font/bootstrap-icons.css&quot; /> &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/idea-react@next/dist/index.css&quot; /> Only add optional third-party styles when your application uses the corresponding component. Keep stylesheet versions aligned with the installed packages. Do not initialize Idea React components with Bootstrap's JavaScript plugins: React and the component's model already own their state and lifecycle. Examples Override a Bootstrap token in your application's stylesheet instead of duplicating a component's CSS rules: :root { --bs-border-radius: 0.75rem; } Compose public components and use their Props for component appearance. Reserve className for utilities and your own styles rather than manually adding Bootstrap component classes: import { FC } from 'react'; import { Button, Stack } from 'idea-react'; export const Actions: FC = () => ( &lt;Stack className=&quot;gap-2&quot; direction=&quot;horizontal&quot;> &lt;Button variant=&quot;solid&quot; theme=&quot;primary&quot;> Save &lt;/Button> &lt;Button variant=&quot;outline&quot; theme=&quot;secondary&quot;> Cancel &lt;/Button> &lt;/Stack> ); Modern essentials Responsive design Build for small screens first, then add layout changes at larger breakpoints. Bootstrap 6 uses prefix-responsive utilities such as lg:d-flex , not Bootstrap 5's suffix-responsive spelling. Prefer the library's layout components when they express the same intent; see the grid guide . HTML5 doctype and viewport Use the HTML5 doctype and a responsive viewport. Framework applications should put the equivalent metadata in their root layout rather than repeating it in individual components. &lt;!doctype html> &lt;html lang=&quot;en&quot;> &lt;head> &lt;meta charset=&quot;utf-8&quot; /> &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1&quot; /> &lt;title>My Idea React application&lt;/title> &lt;/head> &lt;body>&lt;/body> &lt;/html> Box sizing and Reboot Bootstrap's global border-box sizing includes padding and borders in an element's declared dimensions. Its Reboot styles normalize common HTML elements across browsers. Account for these defaults when integrating an existing design; do not add another global reset without checking how the two interact. Browser support The Bootstrap 6 visual foundation depends on modern browser features. Check Bootstrap's browsers and devices guidance alongside the requirements of React and any optional widgets you use. Transpiling TypeScript or decorators does not polyfill browser APIs or CSS. Guiding principles Responsive by default Keep content usable on narrow screens, with keyboard navigation and touch input. Preserve focus, accessible names, and reduced-motion behavior when composing or extending interactive components. Verify layouts in a real browser: a DOM test environment does not measure scrolling or responsive geometry like a browser does. Composition and semantic HTML Import public APIs from idea-react , not repository source paths or unpublished package internals. Reuse an existing component before adding a wrapper with the same job. Single-root components support as to change their root element or component while forwarding the target's attributes. Preserve the original semantics, events, and capabilities when replacing an element. For example, render a navigational action as a link rather than making a button imitate one: import { FC } from 'react'; import { Button } from 'idea-react'; export const InstallLink: FC = () => ( &lt;Button as=&quot;a&quot; href=&quot;../install/&quot; variant=&quot;solid&quot; theme=&quot;primary&quot;> Install Idea React &lt;/Button> ); Fragments do not need an extra wrapper just to support as . A class component's ref refers to its instance, not automatically to its root DOM element. Layering Use the existing overlay components and their stacking conventions instead of competing with arbitrarily large z-index values. CSS stacking contexts and clipping ancestors still matter; test menus, dialogs, tooltips, and other overlays together. HTML and CSS before JavaScript Use native elements for their semantics, anchors for navigation, and CSS for layout, stacking, and static visual states. Do not create observable state just to reproduce something CSS already expresses. Put browser-dependent interaction in the smallest client boundary and leave static presentation server-renderable. Utilities before custom styles Prefer Bootstrap 6 utilities to repeated CSS declarations. Keep remaining styles scoped with CSS Modules, and use Icon with an appropriate font stylesheet instead of drawing a separate icon component. Decorative icons should be hidden from assistive technology; icon-only controls still need accessible names. Component and callback conventions Pass text through children rather than adding a second prop for the same content. Expose native form-control attributes at the component's top level; forward attributes you do not need to transform. Reuse existing prop types with Pick , Omit , or intersections. Use PropsWithChildren for content-bearing components. Give optional Props defaults in destructuring. Extract complicated JSX conditions and large rendering blocks into named values or focused rendering methods. Use arrow instance methods for React event handlers and pass compatible existing callbacks directly. Avoid creating forwarding closures during rendering. When a handler adds behavior, call the external callback first, then run the component's own logic. Use (...) => unknown when the external callback's return value is ignored. Component patterns Choose the smallest pattern that fits the component. These are patterns for application-owned components, not additional base classes you must introduce. Stateful examples use MobX stage-3 decorators. Configure your compiler using the Vite guide or the equivalent setup for your bundler; do not mix these examples with legacy decorators or manual makeObservable initialization. In an RSC application, put 'use client' at the top of modules containing interactive class components, not around an otherwise static page tree. Props-only presentation A function component is enough when rendering depends only on Props: import { FC, PropsWithChildren } from 'react'; export type GreetingProps = PropsWithChildren&lt;{ className?: string }>; export const Greeting: FC&lt;GreetingProps> = ({ className = '', children }) => ( &lt;p className={className}>{children}&lt;/p> ); Greeting.displayName = 'Greeting'; Small local state Keep a small amount of component-specific state on an observed class. There is no need to create a separate model just to hold one counter: import { action, observable } from 'mobx'; import { observer } from 'mobx-react'; import { Component } from 'react'; import { Button } from 'idea-react'; @observer export class LocalCounter extends Component { static displayName = 'LocalCounter'; @observable accessor count = 0; @action increment = () => { this.count++; }; render() { return &lt;Button onClick={this.increment}>Count: {this.count}&lt;/Button>; } } Model-backed behavior Move cohesive business rules and reusable state into a model as the behavior grows. The View creates or receives the model, renders observable values, and forwards interactions: import { action, observable } from 'mobx'; import { observer } from 'mobx-react'; import { Component } from 'react'; import { Button } from 'idea-react'; export class CounterModel { @observable accessor count = 0; @action increment = () => { this.count++; }; } @observer export class ModelCounter extends Component { static displayName = 'ModelCounter'; store = new CounterModel(); render() { const { store } = this; return &lt;Button onClick={store.increment}>Count: {store.count}&lt;/Button>; } } An event method that only forwards to a model action does not need another action boundary. After await , however, subsequent observable updates need their own action: call a separate action method or an action() -wrapped instance function. An action before await does not cover the continuation. Prop reactions and event delegation When behavior must react to changing Props, ObservedComponent and its @reaction decorator from MobX React helper provide observable Props and lifecycle-managed reactions. Add the helper as a direct application dependency if you use it: pnpm add mobx-react-helper This example resets local selection when resetKey changes. One table handler delegates clicks to semantic buttons, so keyboard activation continues to work without per-row event closures: import { action, observable } from 'mobx'; import { observer } from 'mobx-react'; import { ObservedComponent, reaction } from 'mobx-react-helper'; import { MouseEvent } from 'react'; import { Button, Table } from 'idea-react'; export interface ChoiceTableProps { resetKey: string; onSelect?: (value: string) => unknown; } @observer export class ChoiceTable extends ObservedComponent&lt;ChoiceTableProps> { static displayName = 'ChoiceTable'; @observable accessor selected = ''; @reaction(({ observedProps: { resetKey } }) => resetKey) @action resetSelection() { this.selected = ''; } @action select = (value: string) => { this.selected = value; }; handleClick = ({ target, currentTarget }: MouseEvent&lt;HTMLTableElement>) => { if (!(target instanceof Element)) return; const button = target.closest&lt;HTMLButtonElement>('button[data-choice]'); const { choice } = button?.dataset || {}; if (!choice) return; this.props.onSelect?.(choice); this.select(choice); }; renderChoice = (value: string) => ( &lt;tr key={value}> &lt;td> &lt;Button data-choice={value} active={this.selected === value}> {value} &lt;/Button> &lt;/td> &lt;/tr> ); render() { return ( &lt;Table onClick={this.handleClick}> &lt;caption>Choose an item&lt;/caption> &lt;tbody>{['One', 'Two', 'Three', 'Four'].map(this.renderChoice)}&lt;/tbody> &lt;/Table> ); } } Read observedProps inside reactive derivations. If you override the helper's lifecycle methods, call the superclass methods so its synchronization and cleanup still run. Complex component architecture Use MVC, MVVM, or MVP as a guide to responsibilities, not as a requirement to add layers. For a complex interactive component, make a cohesive View Model the business hub: Part Owns Does not own View Model creation and prop synchronization, rendering, input forwarding, lifecycle wiring Business policy, page selection, asynchronous business workflows View Model / Store Business rules, asynchronous workflows, numerical calculations, observable state and execution plans DOM access, layout measurement, browser event registration DOM adapter Numerical layout snapshots, requested DOM effects, measurement and completion feedback Querying the entire model or choosing business state One-way state and operation flow flowchart TD accTitle: Component state and operation flow accDescr: Inputs and numerical DOM measurements feed the View Model. Observable state drives rendering and DOM effects, which report completion and layout changes. Input[&quot;User input / Props / browser facts&quot;] --> Model[&quot;View Model&quot;] Measure[&quot;DOM measurement&quot;] -->|Numerical snapshot| Model Model --> State[&quot;Observable state / execution plan&quot;] State --> View[&quot;View rendering&quot;] State --> Effects[&quot;DOM executor / CSS&quot;] View -->|Mount / layout invalidation| Measure Effects -->|Completion / interruption facts| Model Effects -->|Layout invalidation| Measure observer renders display state. A MobX reaction can consume an execution plan and request a DOM effect. The adapter reports facts through explicit callbacks, which become the next model input; it does not obtain the whole Store and make a competing business decision. Prefer reusing framework composition, decorators, or an existing model to scattering the same behavior across event handlers and Hooks. Pure functions are appropriate for focused, stateless transformations, not as a replacement for cohesive business models. Measurement and execution An application-owned adapter might expose a numerical snapshot and accept a data-only plan: export interface LayoutSnapshot { positions: readonly number[]; maximum: number; } export interface MotionPlan { left: number; smooth: boolean; } The model decides which position is reachable and whether movement is appropriate. The adapter measures elements and performs the requested browser operation; it does not choose the active item. Measurement and execution can share an ordinary class with distinct methods instead of requiring a new class for each responsibility. For example, Carousel turns layout measurements into reachable pages and chooses its loop, wrap, or stop behavior in its model. A state-observed motion plan drives its DOM executor. Fade mode instead uses rendered state and CSS. Application code uses the public Carousel API; its internal measurement and animation classes are not extra package entry points. Measure after mount, before a transition, or when layout is invalidated, and reuse snapshots. Interrupt and remeasure when necessary rather than interleaving layout reads and writes every frame. An executor or CSS can animate between state changes without forcing React to rerender on every animation frame. Lifecycle and asynchronous work Initialize declarative state and disposer fields with class properties. Start browser effects only after client mount, not in constructors or server rendering. Dispose reactions, observers, listeners, timers, and animation resources on unmount. When replacing a model or changing modes, release old effects and preserve relevant selection and playback intent. Unrelated Props changes should not restart a valid timer or subscription. Check that the instance and current operation are still valid before applying an asynchronous result; an old completion must not overwrite newer state or reconnect a destroyed instance. Let errors propagate unless the application has meaningful recovery. Centralize unhandled asynchronous error reporting at the application root, with listener registration and removal tied to its lifecycle. Use finally for resource release or loading-state reset, not to swallow failures. Updates after asynchronous work still need an action boundary. Keep numerical model rules independently testable. Use real-browser checks for layout, keyboard and touch interaction, reduced motion, interruption, and cleanup. The goal is fewer duplicated decisions and clearer ownership, not the fewest files or an abstraction for every mode. Community Join the project's GitHub Discussions to ask questions, exchange ideas, and discuss improvements. For related libraries and application starters, explore the ecosystem guide . Keep application extensions outside library internals so they can evolve without depending on unpublished paths.</description></item><item><title>Forms</title><link>https://idea-react.pages.dev/forms/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/</guid><description>Forms Examples and usage guidelines for form control styles, layout options, and custom components for creating a wide variety of forms. Overview Idea React's form components build on Bootstrap's form styles and provide a consistent API for rendering controls across browsers and devices. For further customization, pass a CSS Module class through className . The CSS reference sections show custom property defaults from the published stylesheet; no preprocessor configuration is required. Be sure to use an appropriate type attribute on all inputs (e.g., email for email address or number for numerical information) to take advantage of newer input controls like email verification, number selection, and more. Here’s a quick example using the form components. Keep reading for component props, form layout, and more. Email address We’ll never share your email with anyone else. Password Check me out Submit Disabled forms Set the disabled prop on FormControl to prevent user interaction and give it a disabled appearance. &lt;FormControl id=&quot;disabledInput&quot; type=&quot;text&quot; placeholder=&quot;Disabled input here...&quot; disabled /> Add the native disabled attribute to a fieldset to disable all nested controls. Browsers treat native inputs, selects, and buttons inside a disabled fieldset as disabled, preventing keyboard and mouse interaction. This does not disable custom links styled as buttons. Use Button 's disabled prop for button-like links; it removes navigation and updates keyboard focus and accessibility state. Disabled fieldset example Disabled input Disabled select menu Disabled select Can’t check this Submit Accessibility Ensure that all form controls have an appropriate accessible name so assistive technologies can convey their purpose. Use FormLabel for form controls, or descriptive content for buttons. When a visible FormLabel or button text is not appropriate, provide an accessible name by: Pointing to an existing element with aria-labelledby Providing a title attribute Explicitly setting the accessible name on an element using aria-label Do not rely on placeholder as a control's accessible name; it is only a fallback in some assistive technology and disappears when the control has a value. While aria-label can provide an accessible name, a visible label is generally best for accessibility and usability. CSS Variables Some form variables are set at the root level to be re-used and extended by individual form components, but you’ll most often see variables set at the form control level. Root variables include --bs-btn-input-* , which are shared with buttons , and --bs-control-* variables. .example { --bs-control-checked-bg: var(--bs-primary-base); --bs-control-checked-border-color: var(--bs-control-checked-bg); --bs-control-active-bg: var(--bs-primary-base); --bs-control-active-border-color: var(--bs-control-active-bg); --bs-control-disabled-bg: var(--bs-bg-3); --bs-control-disabled-opacity: 0.65; --bs-control-transition-duration: 0.15s; --bs-control-transition-timing: cubic-bezier(0.34, 1.56, 0.64, 1); --bs-btn-input-fg: var(--bs-fg-body); --bs-btn-input-bg: var(--bs-bg-body); --bs-btn-input-gap: 0.375rem; --bs-btn-input-min-height: 2.375rem; --bs-btn-input-padding-y: 0.375rem; --bs-btn-input-padding-x: 0.75rem; --bs-btn-input-font-size: var(--bs-body-font-size); --bs-btn-input-font-weight: var(--bs-font-weight-normal); --bs-btn-input-line-height: var(--bs-body-line-height); --bs-btn-input-border-radius: var(--bs-radius-5); --bs-btn-input-xs-gap: var(--bs-spacer-1); --bs-btn-input-xs-min-height: 1.5rem; --bs-btn-input-xs-padding-y: 0.125rem; --bs-btn-input-xs-padding-x: 0.5rem; --bs-btn-input-xs-font-size: var(--bs-font-size-xs); --bs-btn-input-xs-line-height: 1.125; --bs-btn-input-xs-border-radius: var(--bs-radius-5); --bs-btn-input-sm-gap: 0.375rem; --bs-btn-input-sm-min-height: 2rem; --bs-btn-input-sm-padding-y: 0.25rem; --bs-btn-input-sm-padding-x: 0.625rem; --bs-btn-input-sm-font-size: var(--bs-font-size-sm); --bs-btn-input-sm-line-height: var(--bs-line-height-sm); --bs-btn-input-sm-border-radius: var(--bs-radius-5); --bs-btn-input-lg-gap: 0.375rem; --bs-btn-input-lg-min-height: 2.75rem; --bs-btn-input-lg-padding-y: 0.5rem; --bs-btn-input-lg-padding-x: 1rem; --bs-btn-input-lg-font-size: var(--bs-font-size-md); --bs-btn-input-lg-line-height: var(--bs-line-height-md); --bs-btn-input-lg-border-radius: var(--bs-radius-7); }</description></item><item><title>Validation</title><link>https://idea-react.pages.dev/forms/validation/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/validation/</guid><description>Validation Provide valuable, actionable feedback to your users with HTML5 form validation, via browser default behaviors or custom styles and JavaScript. How it works The form wrappers support native client-side validation and component-based feedback: Client-side validation uses CSS pseudo-classes scoped behind the data-bs-validate attribute. Pass it to ValidationForm to opt in to :user-invalid styling—validation styles only appear after the user interacts with a control (e.g., typing and blurring, or attempting to submit), so required fields don’t show up as invalid on page load. By default, client-side validation only shows invalid styling. To also show success styling for valid fields, set data-bs-validate=&quot;valid&quot; on ValidationForm . Server-side validation uses the validation prop on form controls to indicate field state without requiring user interaction. All modern browsers support the constraint validation API , a series of JavaScript methods for validating form controls. Feedback messages may utilize the browser defaults (different for each browser, and unstylable via CSS) or our custom feedback styles with additional HTML and CSS. You may provide custom validity messages with setCustomValidity in JavaScript. With that in mind, consider the following demos for our custom form validation styles, optional server-side classes, and browser defaults. Custom styles For custom validation messages, pass data-bs-validate and noValidate to ValidationForm . The first opts in to :user-invalid styling, while the second disables browser-default feedback tooltips. Custom feedback styles apply colors, borders, and focus styles to better communicate field state. Set data-bs-validate=&quot;valid&quot; to also show success styling on valid fields. Add required to each control and use FormFeedback for field-specific messages. Set its type prop to valid for success feedback. For accessibility, add aria-describedby to each form control, pointing to the id of its feedback message. This ensures screen readers announce the error when the user focuses an invalid field. The ValidationForm example below also sets aria-invalid on each control at submit time and clears it as users correct their input. For example, try to submit the form below; our ValidationForm wrapper will intercept submission and relay feedback to you. Name Full name is required Donation amount $ Please enter a donation amount Address Please enter a mailing address City Please provide a city State Choose… ... Please select a state Zip Required Shipping method Standard Arrives in 5-7 business days. Express Arrives in 2-3 business days. Subscribe to newsletter Submit form ValidationForm wraps the library’s Form with the upstream validation handlers. It also prevents navigation on successful submission so the demo remains on this page. In an application, replace that demo-only prevention with your submission flow. Browser defaults Not interested in custom validation feedback messages or writing JavaScript to change form behaviors? All good, you can use the browser defaults. Try submitting the form below. Depending on your browser and OS, you’ll see a slightly different style of feedback. While these feedback styles cannot be styled with CSS, you can still customize the feedback text through JavaScript. Name Donation amount $ Address City State Choose… ... Zip Shipping method Standard Arrives in 5-7 business days. Express Arrives in 2-3 business days. Subscribe to newsletter Submit form Server-side We recommend using client-side validation, but for server-side validation set each control's validation prop to invalid or valid . Pair it with FormFeedback to display the corresponding message. For invalid fields, ensure that the invalid feedback/error message is associated with the relevant form field using aria-describedby (noting that this attribute allows more than one id to be referenced, in case the field already points to additional form text). Name Looks great! Full name is required Donation amount $ Looks great! Please enter a donation amount Address Looks great! Please enter a mailing address City Please provide a city State Choose… ... Please select a state Zip Required Shipping method Standard Arrives in 5-7 business days. Express Arrives in 2-3 business days. Subscribe to newsletter Submit form Supported elements Validation styles work with the form wrappers: FormControl , FormTextArea , FormSelect , Checkbox , Radio , FormSwitch , FormRange , FormFloatingLabel , FormAdornment , and ChipInput . Combobox also supports validation props. For input groups, place the group and its feedback inside FormField . Textarea Please enter a message in the textarea. Checkbox Check this checkbox Example invalid feedback text Radio Toggle this radio Or toggle this other radio More example invalid feedback text Switch Toggle this switch Example invalid switch feedback Select Open this select menu One Two Three Example invalid select feedback File input Example invalid form file feedback Range Example invalid range feedback Email address Example invalid floating label feedback Adorned input Example invalid adorned input feedback Input group @ Please choose a username Tags Example Please add at least one tag Tooltips If your form layout allows it, you can swap the .{valid|invalid}-feedback classes for .{valid|invalid}-tooltip classes to display validation feedback in a styled tooltip. These tooltips build on the base .tooltip styles, so you’ll need to have those included in your compiled CSS as well. We don’t recommend using tooltips for checkboxes, radios, and switches because their placement is not reliable or consistent in most cases. You can also use a combination of feedback text and tooltips in your forms. This example functions the same as the custom styles example . Click the submit button to see the validation tooltips. Name Full name is required Donation amount $ Please enter a donation amount Address Please enter a mailing address City Please provide a city State Choose… ... Please select a state Zip Required Shipping method Standard Arrives in 5-7 business days. Please select a shipping method Express Arrives in 2-3 business days. Subscribe to newsletter Submit form</description></item><item><title>Switch</title><link>https://idea-react.pages.dev/forms/switch/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/switch/</guid><description>Switch FormSwitch wraps a native checkbox input in a customizable toggle component. Basic switch Switches work by layering an invisible checkbox over the custom switch indicator. This preserves interactivity while giving you a completely customizable layer underneath. FormSwitch supplies role=&quot;switch&quot; on the checkbox. Pass native input attributes such as id , name , disabled , and defaultChecked directly to FormSwitch . With form field Wrap FormSwitch in a FormField layout wrapper and add your label. The grid layout places the switch and label side by side. Default switch Theme colors Modify the appearance of switches by adding the theme prop to the .switch element. This will set the checked background and border color to the theme color. Example primary switch Example accent switch Example secondary switch Example success switch Example danger switch Example warning switch Example info switch Example dark switch Example light switch Example inverse switch Disabled Set the disabled prop on FormSwitch ; its label is automatically styled in a lighter color to indicate the input's state. Disabled switch Disabled checked switch Sizes Add a size modifier class to make your switch appear smaller or larger. Small switch Default switch Large switch Custom width Customize your switch for any width and indicator size you need by overriding the CSS variables. For example, for a more modern look, you could widen the switch and indicator. Custom width switch CSS Variables .example { --bs-switch-height: 1.25rem; --bs-switch-width: calc(var(--bs-switch-height) * 1.75); --bs-switch-padding: 0.0625rem; --bs-switch-margin-block: 0.125rem; --bs-switch-transition-duration: var(--bs-control-transition-duration); --bs-switch-transition-timing: var(--bs-control-transition-timing); --bs-switch-bg: var(--bs-bg-3); --bs-switch-border-width: var(--bs-border-width); --bs-switch-border-color: var(--bs-border-color); --bs-switch-indicator-bg: var(--bs-white); --bs-switch-indicator-width: calc( var(--bs-switch-height) - var(--bs-switch-padding) * 2 - var(--bs-switch-border-width) * 2 ); --bs-switch-indicator-height: calc( var(--bs-switch-height) - var(--bs-switch-padding) * 2 - var(--bs-switch-border-width) * 2 ); --bs-switch-checked-bg: var(--bs-control-checked-bg); --bs-switch-checked-border-color: var(--bs-switch-checked-bg); --bs-switch-checked-indicator-bg: var(--bs-white); --bs-switch-disabled-bg: var(--bs-control-disabled-bg); --bs-switch-disabled-indicator-bg: var(--bs-fg-3); }</description></item><item><title>Range</title><link>https://idea-react.pages.dev/forms/range/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/range/</guid><description>Range Use our custom range inputs for consistent cross-browser styling with a filled track, value bubble, and tick marks. Overview The native &lt;input type=&quot;range&quot;> is hard to style and can’t show a filled track in a consistent, cross-browser way using CSS alone—only Firefox offers ::-moz-range-progress , and CSS can’t read an input’s value. So our range is a small JavaScript component : use FormRange , which wraps a native range input, and the plugin keeps a --bs-range-fill custom property (0–1) in sync, which the CSS uses to draw the fill, the value bubble, and tick marks. FormRange owns the component's theme tokens, so the input and any decorations inherit them. Each mounted component initializes automatically. Example range Theme colors Set the theme prop on FormRange to change the track fill and thumb color. Disabled Add the disabled boolean attribute on the input to give it a grayed out appearance, remove pointer events, and prevent focusing. Disabled range Min and max Range inputs have implicit values for min and max — 0 and 100 , respectively. You may specify new values for those using the min and max attributes. Example range Steps By default, range inputs “snap” to integer values. To change this, you can specify a step value. In the example below, we double the number of steps by using step=&quot;0.5&quot; . Example range Value bubble Set bubble to show a value bubble that follows the thumb. The bubble reuses our tooltip styles. Brightness Tick marks Link a &lt;datalist> to the input with the list attribute and the plugin renders a tick mark for each &lt;option> , positioned at its value (even when the values are unevenly spaced). An &lt;option> ’s label is shown beneath its tick. Temperature With form field Wrap FormRange in FormField to pair it with a label and description. Volume Adjust the volume level. Usage FormRange initializes and disposes the plugin automatically. Pass bubble and formatter as props, and use onValueChange for numeric updates. Native value and defaultValue control the input value. Each FormRange is initialized automatically when mounted—the component is JavaScript-driven, so the fill won’t render without the plugin. Options Name Type Default Description bubble boolean false Show a value bubble above the thumb. formatter function null (value) => string used for the bubble and tick label text. CSS Variables .example { --bs-range-track-width: 100%; --bs-range-track-height: 0.5rem; --bs-range-track-cursor: pointer; --bs-range-track-bg: var(--bs-bg-3); --bs-range-track-border-radius: 1rem; --bs-range-track-fill-bg: var(--bs-theme-bg, var(--bs-primary-base)); --bs-range-track-disabled-bg: color-mix(in oklch, var(--bs-bg-4), var(--bs-fg-3)); --bs-range-thumb-width: 1rem; --bs-range-thumb-height: var(--bs-range-thumb-width); --bs-range-thumb-bg: var(--bs-theme-bg, var(--bs-primary-base)); --bs-range-thumb-border: var(--bs-range-thumb-bg) solid var(--bs-border-color); --bs-range-thumb-border-radius: 1rem; --bs-range-thumb-box-shadow: 0 1px 2px rgb(0 0 0 / 7.5%), 0 2px 4px rgb(0 0 0 / 7.5%); --bs-range-thumb-active-bg: color-mix( in oklch, var(--bs-theme-bg, var(--bs-primary-base)) 70%, var(--bs-bg-body) ); --bs-range-thumb-disabled-bg: var(--bs-fg-3); --bs-range-thumb-transition-property: background-color, border-color, box-shadow; --bs-range-thumb-transition-duration: 0.15s; --bs-range-thumb-transition-timing: ease-in-out; --bs-range-tick-width: var(--bs-border-width); --bs-range-tick-height: 0.5rem; --bs-range-tick-bg: var(--bs-border-color); }</description></item><item><title>Radio</title><link>https://idea-react.pages.dev/forms/radio/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/radio/</guid><description>Radio Radio wraps a native radio input with customizable appearance for choosing one option from many. Basic radio Similar to checkboxes, radios are styled with the .radio class. However, there’s no custom SVG as we use pure CSS to style the input and its checked state. With form field Wrap Radio in a FormField layout wrapper and add your label. The grid layout places the radio and label side by side. First example radio Second example radio Description Add a description or other content after the label. Wrap the label and description in FormFieldContent to ensure appropriate spacing and alignment. Example new radio Supporting description for the above label. Theme colors Modify the appearance of checked radios with the theme prop. This will set the checked background and border color to the theme color. Example primary radio Example accent radio Example secondary radio Example success radio Example danger radio Example warning radio Example info radio Example dark radio Example light radio Example inverse radio Disabled Set the disabled prop on Radio ; its associated FormLabel is automatically styled in a lighter color to indicate the input's state. Example new radio Example checked disabled radio Sizes Set size=&quot;sm&quot; or size=&quot;lg&quot; to make your radio appear smaller or larger. Small radio Default radio Large radio CSS Variables Override the radio component's CSS variables for visual customization. .example { --bs-radio-size: 1.25rem; --bs-radio-margin-block: 0.125rem; --bs-radio-bg: var(--bs-bg-body); --bs-radio-border-color: var(--bs-border-color); --bs-radio-checked-bg: var(--bs-control-checked-bg); --bs-radio-checked-border-color: var(--bs-control-checked-border-color); --bs-radio-disabled-bg: var(--bs-control-disabled-bg); --bs-radio-disabled-opacity: var(--bs-control-disabled-opacity); }</description></item><item><title>Password strength</title><link>https://idea-react.pages.dev/forms/password-strength/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/password-strength/</guid><description>Password strength Provide visual feedback on password strength with segmented meters or progress bars that update as users type. Overview Strength meters help users create secure passwords by providing real-time feedback on password complexity. Bootstrap’s strength component offers: Segmented meter : Four segments that fill based on strength level Progress bar variant : A single bar that grows with strength Text feedback : Optional text messages for each strength level Customizable scoring : Configure minimum length and scoring criteria Minimal JavaScript : Lightweight component following Bootstrap patterns Examples Segmented The default strength meter uses four segments that fill progressively as password strength increases. The PasswordStrength component enables JavaScript behavior automatically. Password With text feedback PasswordStrength displays the strength message by default. Set showText={false} to hide it. Password Progress bar Set variant=&quot;bar&quot; on PasswordStrength for a single progress bar that grows with password strength. Password Static segmented You can use the component without JavaScript for static displays by passing the strength prop. Weak Fair Good Strong Static progress bar Weak Fair Good Strong Strength criteria The default scoring algorithm evaluates passwords based on: Criteria Points Meets minimum length (8 characters) +1 4+ characters over minimum +1 Contains lowercase letters +1 Contains uppercase letters +1 Contains numbers +1 Contains special characters +1 Multiple special characters +1 16+ characters +1 Level Points Weak 1-2 Fair 3-4 Good 5-6 Strong 7-8 Usage PasswordStrength binds to the password field through input , or discovers a sibling input. Pass scoring options as props. Use strength for a static meter and showText for feedback. Options Name Type Default Description input string | element null Selector or element for the password input. If not provided, looks for input[type=&quot;password&quot;] in the parent. minLength number 8 Minimum password length for first strength point. messages object {weak, fair, good, strong} Custom messages for each strength level. weights object See below Point values for each scoring criterion. Set to 0 to disable a criterion. thresholds array [2, 4, 6] Score boundaries for strength levels: [weak, fair, good] . Scores above the last value are &quot;strong&quot;. scorer function null Custom scoring function (password) => number . Overrides built-in scoring when provided. Default weights { minLength: 1, // Meets minimum length extraLength: 1, // 4+ characters over minimum lowercase: 1, // Contains lowercase letters uppercase: 1, // Contains uppercase letters numbers: 1, // Contains numbers special: 1, // Contains special characters multipleSpecial: 1, // Multiple special characters longPassword: 1 // 16+ characters } Custom weights &lt;PasswordStrength weights={{ uppercase: 0, special: 2 }} thresholds={[3, 5, 7]} /> Custom scorer &lt;PasswordStrength scorer={password => Number(password.length >= 12) * 4 + Number(/[!@#$%]/.test(password)) * 4} thresholds={[2, 4, 6]} /> CSS-only usage For simple cases or server-rendered content, you can use the component without JavaScript by passing the strength prop. &lt;PasswordStrength strength=&quot;good&quot; /> Accessibility The strength meter is decorative feedback and should be used alongside clear password requirements text Consider using aria-describedby to associate the password input with requirement text Screen reader users benefit from the text feedback option which announces strength changes CSS Variables .example { --bs-strength-height: 0.375rem; --bs-strength-gap: 0.25rem; --bs-strength-margin-top: 0.25rem; --bs-strength-border-radius: var(--bs-radius-pill); --bs-strength-bg: var(--bs-bg-2); --bs-strength-color: var(--bs-bg-2); --bs-strength-weak-color: var(--bs-danger-bg); --bs-strength-fair-color: var(--bs-warning-bg); --bs-strength-good-color: var(--bs-info-bg); --bs-strength-strong-color: var(--bs-success-bg); }</description></item><item><title>OTP input</title><link>https://idea-react.pages.dev/forms/otp-input/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/otp-input/</guid><description>OTP input Collect one-time passwords, PIN codes, and verification codes with a single accessible input rendered as separate digit slots. Overview OTP (One-Time Password) inputs are a common pattern for two-factor authentication, verification codes, and PIN entry. Bootstrap's OTP input is built around a single real text field that is visually rendered as separate digit slots. This keeps the control simple and fully accessible—screen readers, password managers, and SMS autofill all treat it like any other text input—while still giving you the familiar multi-box appearance. One accessible control : a single &lt;input> backs the whole field, so assistive technology announces one field, not one per digit Browser autofill : supports autocomplete=&quot;one-time-code&quot; for SMS/email code autofill Paste support : paste a full code—even a formatted one like 123-456 —and the extra characters are stripped automatically Click to edit : click any slot to jump to it; typing overwrites that digit in place instead of pushing the others along Keyboard navigation : all native text editing (typing, arrows, backspace, delete, selection) works out of the box Masking and types : optionally mask the value, and restrict input to numeric, alphanumeric, or alphabetic characters OTP input is built on form controls and shares its sizing tokens. How it works Use OTPInput with a length prop to determine how many slots to render. The component positions the input over the visual slots and draws one slot per character. Give the input an accessible name with aria-label or an associated FormLabel . Connected inputs Set connected to merge the slots into a single cohesive field with shared borders. Four-digit PIN Set length to control the number of slots—use fewer for shorter codes like a 4-digit PIN. With separator Use groups with an array of group sizes to split the slots into groups separated by a visual divider—handy for codes like &quot;123-456&quot;. The separator is decorative and never becomes part of the value. Sizes Set size=&quot;sm&quot; or size=&quot;lg&quot; to change the slot size. Alphanumeric and masking By default only digits are accepted. Set type to alphanumeric or alpha to accept letters, and mask to obscure the entered value while keeping it a normal text field (no type=&quot;password&quot; , so the numeric keyboard and autofill still work). Disabled Add the disabled attribute to the input to prevent interaction. Validation Set validation=&quot;valid&quot; or validation=&quot;invalid&quot; to show validation states. With form label Associate a FormLabel with the input and add help text with aria-describedby for better accessibility. Verification code Enter the 6-digit code sent to your phone. Usage OTPInput initializes and disposes the plugin automatically. Pass options as props. Use onValueChange for edits and onComplete when all slots are filled. Options Pass options directly as OTPInput props: Name Type Default Description length number Required Number of slots. type string 'numeric' Allowed characters: numeric , alphanumeric , or alpha . Sets inputmode and pattern accordingly. mask boolean false If true , slots display a dot ( • ) instead of the entered character. groups array, null null Group sizes used to insert separators (e.g. [3, 3] ). separator string '·' Character rendered between groups. Accessibility Because the control is a single text input, it exposes one accessible name, role, and value—so assistive technology announces it as one ordinary text field instead of one edit field per digit. The visual slots are decorative and marked aria-hidden , and no per-digit aria-label s are needed. Give the input a single accessible name with aria-label or an associated FormLabel , and add context with aria-describedby . The component sets autocomplete=&quot;one-time-code&quot; and an appropriate inputmode so codes can be autofilled and the right mobile keyboard appears. This supports WCAG 1.3.5 Identify Input Purpose . Copy, paste, and autofill are never blocked, which keeps the control compliant with WCAG 3.3.8 Accessible Authentication (Minimum) —a single input is also what password managers and SMS autofill target reliably. For the verification flow itself, give codes a generous expiry ( WCAG 2.2.1 Timing Adjustable ) and avoid forcing users to re-enter a code already provided in the same process ( WCAG 3.3.7 Redundant Entry ). CSS Variables .example { --bs-otp-size: var(--bs-btn-input-lg-min-height); --bs-otp-font-size: var(--bs-btn-input-font-size); --bs-otp-gap: 0.5rem; --bs-otp-slot-fg: var(--bs-btn-input-fg); --bs-otp-slot-bg: var(--bs-btn-input-bg); --bs-otp-slot-border-width: var(--bs-border-width); --bs-otp-slot-border-color: var(--bs-border-color); --bs-otp-slot-border-radius: var(--bs-radius-5); }</description></item><item><title>Layout</title><link>https://idea-react.pages.dev/forms/layout/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/layout/</guid><description>Layout Give your forms some structure—from inline to horizontal to custom grid implementations—with our form layout options. Forms Every group of form fields should reside in a Form element. Form preserves native browser form behavior and passes standard form attributes through. New to browser forms? Consider reviewing the MDN form docs for an overview and complete list of available attributes. Button components inside a Form default to type=&quot;button&quot; , so set type=&quot;submit&quot; explicitly on submit buttons. The form control wrappers fill their available width, so fields stack vertically by default. Use spacing and grid utilities through the layout components' className props to vary this layout. Utilities Margin utilities are the easiest way to add structure to forms. Pass them through FormField 's className to space labels, controls, optional form text, and validation feedback. Use a single direction throughout the form for consistency. Use semantic elements such as fieldset where appropriate; the Form wrapper can also render as a different element with its as prop. Example label Another label Form grid Use Row and Col for form layouts that require multiple columns, varied widths, and additional alignment options. Set responsive column spans with the Col breakpoint props. Gutters Set gutter utilities through Row 's className to control spacing between columns in both directions. More complex layouts can also be created with the grid system. Email Password Address Address 2 City State Choose... ... Zip Check me out Sign in Horizontal form Create horizontal forms with the Row and Col layout components. Set the column breakpoint props (such as sm={2} ) to size labels and controls, and use the column prop on FormLabel or FormLegend to align the label with its control. Use margin or padding utilities through className on Row , Col , or FormLabel to adjust alignment. For example, removing top padding from a stacked radio label can better align its text baseline. Email Password Radios First radio Second radio Third disabled radio Example checkbox Sign in Horizontal form label sizing Set controlSize on FormLabel or FormLegend to match the controlSize of the associated form control. Email Email Email Column sizing Place any number of Col components in a Row to split the available width equally. Set a breakpoint prop such as sm={7} to size one column while the remaining columns share the rest. Auto-sizing The example below passes a flexbox alignment utility through Row 's className and sets the Col component's xs prop to &quot;auto&quot; , so each column takes only as much space as its contents need. Name Username @ Preference Choose... One Two Three Remember me Submit You can then combine responsive Col props to adjust the layout at multiple breakpoints. Name Username @ Preference Choose... One Two Three Remember me Submit Inline forms Use responsive Col props to create horizontal layouts. Add gutter and alignment utilities through Row 's className ; on narrow viewports, set xs={12} on each Col to stack the controls. Username @ Preference Choose... One Two Three Remember me Submit</description></item><item><title>Input group</title><link>https://idea-react.pages.dev/forms/input-group/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/input-group/</guid><description>Input group Easily extend form controls by adding text, buttons, or button groups on either side of textual inputs, custom selects, and custom file inputs. Input groups attach add-on elements to a textual input field. Add-ons can be text, buttons, or button groups. Add labels, help text, and validation styles with form fields . Pass htmlFor to InputGroupText to render the add-on itself as a label for its control. @ @example.com Examples Place one add-on or button on either side of a control, or add one to both sides. Place FormLabel outside InputGroup so the label remains associated with the control. With form field Wrap InputGroup in FormField to pair it with a label and description. Your vanity URL https://example.com/ Choose a unique URL for your profile. Buttons Use buttons instead of addons for supporting interactive options. Button Textarea Input groups adapt to the height of textarea elements. With textarea Select Options Choose... One Two Three Choose... One Two Three Options Button Choose... One Two Three Choose... One Two Three Button File input Upload Upload Button Button Checkboxes and radios Place any checkbox or radio within an input group’s addon instead of text. Multiple inputs Although InputGroup can display multiple FormControl components, validation styles are available only when the group contains a single control. First and last name @ Multiple addons Multiple add-ons are supported and can be mixed with checkbox and radio input versions. $ 0.00 $ 0.00 $ .00 Button addons Button Button Button Button Button Button Buttons with menus Action Another action Something else here Separated link Action Another action Something else here Separated link Action before Another action before Something else here Separated link Action Another action Something else here Separated link Segmented buttons Action Action Another action Something else here Separated link Action Action Another action Something else here Separated link Border radius Sometimes an extra element needs to bypass the group's border-radius adjustments. Wrap that element in InputGroupIgnore to preserve its own border radius. Consider this extra hidden input example: @ Sizing Set the size prop on InputGroup to resize its contents; you do not need to repeat the size prop on each form control. Sizing on the individual input group elements isn’t supported. Small Default Large CSS Variables .example { --bs-input-group-addon-padding-y: var(--bs-btn-input-padding-y); --bs-input-group-addon-padding-x: var(--bs-btn-input-padding-x); --bs-input-group-addon-font-size: var(--bs-btn-input-font-size); --bs-input-group-addon-line-height: var(--bs-btn-input-line-height); --bs-input-group-addon-color: var(--bs-fg-body); --bs-input-group-addon-bg: var(--bs-bg-2); --bs-input-group-addon-border-color: var(--bs-border-color); }</description></item><item><title>Form controls</title><link>https://idea-react.pages.dev/forms/form-control/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/form-control/</guid><description>Form controls Use FormControl , FormTextArea , and FormSelect to add custom styles, sizing, focus states, and more to native form controls. Heads up! FormSelect uses the same base styles as FormControl for ease of use. These wrappers style most textual inputs (including date and time types), textareas, and select elements consistently, with element-specific modifiers where needed. Email address With form field Use the form field component to layout and wrap your inputs with a label, description, and validation feedback messages in a vertical stack. Email address We’ll never share your email with anyone else. Textarea FormTextArea shares the base appearance of FormControl . Set its rows attribute or use custom CSS to change its height. Example textarea Taller textarea Select FormSelect provides the basic select appearance. Styling is limited by the browser—options and popovers cannot be styled. Example select Choose one… One Two Three The multiple attribute is supported on select elements: Multiple select Open this select menu One Two Three As is the size attribute: Size 3 select Open this select menu One Two Three Sizes Set controlSize to sm or lg on FormControl , FormTextArea , or FormSelect to adjust the control's height, padding, font size, line height, and border radius. Small input Default input Large input And for textareas: Small textarea Default textarea Large textarea And for selects: Small select Open this select menu One Two Three Default select Open this select menu One Two Three Large select Open this select menu One Two Three Form text FormText is inline by default; set block for descriptions that belong on their own line. Form text should be explicitly associated with the form control it relates to using the aria-describedby attribute. This will ensure that assistive technologies—such as screen readers—will announce this form text when the user focuses or enters the control. FormText adds top spacing when rendered as a block, keeping descriptions separated from the controls above. Password Your password must be 8-20 characters long, contain letters and numbers, and must not contain spaces, special characters, or emoji. FormText renders as a &lt;small> element by default. Use its as prop to choose another inline element when needed. Password Must be 8-20 characters long. States Disabled Add the disabled boolean attribute on an input to give it a grayed out appearance, remove pointer events, and prevent focusing. Open this select menu One Two Three Readonly Add the readonly boolean attribute on an input to prevent modification of the input’s value. readonly inputs can still be focused and selected, while disabled inputs cannot. Readonly plain text Set plaintext on FormControl to display a read-only input as plain text, removing the default field styling while preserving its margin and padding. Email Password Email Password Confirm identity Types Nearly all input types are supported, but not all are documented here. Types that need additional props or styling are shown below. Date &amp; Time Date and time inputs need no additional component-specific props. Their exact functionality and appearance depend on the browser and operating system. You can also use our datepicker component for a more consistent experience across browsers with JavaScript. Color Set type=&quot;color&quot; and the color prop on FormControl to size the color input consistently and account for browser differences. Color picker Sizes are also supported: Large color picker Small color picker Datalists Datalists allow you to create a group of &lt;option> s that can be accessed (and autocompleted) from within an &lt;input> . These are similar to &lt;select> elements, but come with more menu styling limitations and differences. While most browsers and operating systems include some support for &lt;datalist> elements, their styling is inconsistent at best. Learn more about support for datalist elements . Datalist example Set the caret prop on FormControl to add a caret without using a select element. Datalist example with caret File File inputs use the ::file-selector-button pseudo-element to style the button within the control. Use FormControl with controlSize when you need a size variant. Default file input example Multiple files input example Disabled file input example Small file input example Large file input example Ghost FormGhost removes the input's default styling when a surrounding component handles spacing, borders, and focus states. Use it for composites such as search bars and command inputs. Because FormGhost removes the input's focus outline, make sure its surrounding component provides a visible focus indicator, such as with :focus-within . Search You can also use the form-adorn component to provide prebuilt styles for your ghost input. CSS Optional custom properties shown as initial are unset in the published CSS. Variables .example { --bs-control-min-height: var(--bs-btn-input-min-height); --bs-control-padding-y: var(--bs-btn-input-padding-y); --bs-control-padding-x: var(--bs-btn-input-padding-x); --bs-control-font-size: var(--bs-btn-input-font-size); --bs-control-line-height: var(--bs-btn-input-line-height); --bs-control-fg: var(--bs-btn-input-fg); --bs-control-bg: var(--bs-btn-input-bg); --bs-control-border-width: var(--bs-border-width); --bs-control-border-color: var(--bs-border-color); --bs-control-border-radius: var(--bs-radius-5); --bs-control-box-shadow: var(--bs-box-shadow-inset); --bs-control-action-bg: var(--bs-bg-1); --bs-control-action-hover-bg: var(--bs-bg-2); --bs-control-transition-property: border-color, box-shadow; --bs-control-transition-duration: 0.15s; --bs-control-transition-timing: cubic-bezier(0.34, 1.56, 0.64, 1); --bs-control-placeholder-color: var(--bs-fg-3); --bs-control-disabled-color: var(--bs-control-fg); --bs-control-disabled-bg: var(--bs-bg-3); --bs-control-disabled-border-color: var(--bs-control-border-color); --bs-control-select-bg: url(&quot;data:image/svg+xml,%3csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3e%3cpath fill='none' stroke='%2300000080' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' d='m2 5 6 6 6-6'/%3e%3c/svg%3e&quot;); --bs-control-select-bg-position: right 0.75rem center; --bs-control-select-bg-size: 16px 12px; --bs-control-select-bg-dark: url(&quot;data:image/svg+xml,%3csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3e%3cpath fill='none' stroke='%23ffffff80' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' d='m2 5 6 6 6-6'/%3e%3c/svg%3e&quot;); } For FormLabel : .example { --bs-label-margin-bottom: calc(var(--bs-spacer) / 2); --bs-label-font-size: inherit; --bs-label-font-style: inherit; --bs-label-font-weight: 500; --bs-label-color: var(--bs-fg-body); } For FormText : .example { --bs-form-text-margin-top: 0.25rem; --bs-form-text-font-size: var(--bs-font-size-sm); --bs-form-text-font-style: initial; --bs-form-text-font-weight: initial; --bs-form-text-color: var(--bs-fg-2); } Root variables Some inputs and buttons share some root variables for consistency across all form elements, primarily for sizing. .example { --bs-control-checked-bg: var(--bs-primary-base); --bs-control-checked-border-color: var(--bs-control-checked-bg); --bs-control-active-bg: var(--bs-primary-base); --bs-control-active-border-color: var(--bs-control-active-bg); --bs-control-disabled-bg: var(--bs-bg-3); --bs-control-disabled-opacity: 0.65; --bs-control-transition-duration: 0.15s; --bs-control-transition-timing: cubic-bezier(0.34, 1.56, 0.64, 1); --bs-btn-input-fg: var(--bs-fg-body); --bs-btn-input-bg: var(--bs-bg-body); --bs-btn-input-gap: 0.375rem; --bs-btn-input-min-height: 2.375rem; --bs-btn-input-padding-y: 0.375rem; --bs-btn-input-padding-x: 0.75rem; --bs-btn-input-font-size: var(--bs-body-font-size); --bs-btn-input-font-weight: var(--bs-font-weight-normal); --bs-btn-input-line-height: var(--bs-body-line-height); --bs-btn-input-border-radius: var(--bs-radius-5); --bs-btn-input-xs-gap: var(--bs-spacer-1); --bs-btn-input-xs-min-height: 1.5rem; --bs-btn-input-xs-padding-y: 0.125rem; --bs-btn-input-xs-padding-x: 0.5rem; --bs-btn-input-xs-font-size: var(--bs-font-size-xs); --bs-btn-input-xs-line-height: 1.125; --bs-btn-input-xs-border-radius: var(--bs-radius-5); --bs-btn-input-sm-gap: 0.375rem; --bs-btn-input-sm-min-height: 2rem; --bs-btn-input-sm-padding-y: 0.25rem; --bs-btn-input-sm-padding-x: 0.625rem; --bs-btn-input-sm-font-size: var(--bs-font-size-sm); --bs-btn-input-sm-line-height: var(--bs-line-height-sm); --bs-btn-input-sm-border-radius: var(--bs-radius-5); --bs-btn-input-lg-gap: 0.375rem; --bs-btn-input-lg-min-height: 2.75rem; --bs-btn-input-lg-padding-y: 0.5rem; --bs-btn-input-lg-padding-x: 1rem; --bs-btn-input-lg-font-size: var(--bs-font-size-md); --bs-btn-input-lg-line-height: var(--bs-line-height-md); --bs-btn-input-lg-border-radius: var(--bs-radius-7); }</description></item><item><title>Form adorn</title><link>https://idea-react.pages.dev/forms/form-adorn/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/form-adorn/</guid><description>Form adorn Decorate inputs with icons, text, and more using a custom wrapper that easily handles styling and positioning. How it works Wrap adornments and a FormGhost control in FormAdornment . The wrapper provides the border, background, padding, and focus states, and uses flexbox to position adornments beside the visually unstyled FormGhost , which inherits the wrapper's styles. FormAdornment renders a label by default. This lets people click the icon, text, or surrounding padding to focus the control without any JavaScript. Mark decorative FormAdornmentIcon and FormAdornmentText components with aria-hidden=&quot;true&quot; . Because the default FormAdornment label also labels its nested input, text adornments such as $ can become part of the input's accessible name. Keep decorative content out of the accessibility tree, and provide meaningful names with FormLabel or visible label text and descriptions with FormText . An input can have more than one label, so the default FormAdornment label and a separate FormLabel can work together. Set FormLabel 's htmlFor to the input's id . Do not put a button or another interactive control inside the default FormAdornment label. If the wrapper needs interactive content, use its as prop to render a non-label element and label the input separately. See the form control documentation for more information on FormControl and FormGhost . Example Use FormAdornment to wrap an icon and a FormGhost input. Place the adornment before the input in the DOM to position it at the start (left in LTR). Set the end prop to position the adornment on the trailing side. The DOM order stays the same while the visual order changes: With labels Add a FormLabel outside FormAdornment to give the field a visible name. Set its htmlFor prop to the id of the FormGhost input so the label remains associated with the field if you change the wrapper: Search Email address With form field Use FormField to group FormLabel , FormAdornment , and FormText into a field with a label and description. Search Search across all pages and posts. Text adornments Use FormAdornmentText for currency symbols, units, domain suffixes, and other text-based adornments. Text adornments auto-size to their content. $ USD https:// @example.com Sizing Set the size prop to sm or lg on FormAdornment to adjust its size. CSS Variables .example { --bs-form-adorn-gap: 0.375rem; --bs-form-adorn-icon-size: 1rem; --bs-form-adorn-icon-color: var(--bs-fg-2); }</description></item><item><title>Floating labels</title><link>https://idea-react.pages.dev/forms/floating-labels/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/floating-labels/</guid><description>Floating labels Create beautifully simple form labels that float over your input fields. Example Wrap a FormControl and FormLabel pair in FormFloatingLabel to enable floating labels. A non-empty placeholder is required on each text FormControl . The CSS-only implementation relies on the :placeholder-shown pseudo-element to detect an empty input. The placeholder stays transparent until the control is focused, then uses the normal placeholder color; only FormLabel is shown while the field is empty and unfocused. FormFloatingLabel places FormLabel before the control so screen readers announce the label before the field's value. Its CSS reacts to the control's state with the :has() selector. Email address Password When defaultValue or a controlled value is set, FormLabel automatically moves to its floated position. Input with value Form validation styles also work as expected. Invalid input Textareas By default, FormTextArea has the same height as FormControl . Comments To set a custom height on FormTextArea , do not use the rows attribute. Instead, override the --bs-form-floating-height CSS variable on FormFloatingLabel through a CSS module so the label floats correctly at any height. Comments Selects FormSelect works in the same way, but always shows FormLabel in its floated state. Selects with size and multiple are not supported. Works with selects Open this select menu One Two Three Date and time Date, time, datetime-local, month, and week FormControl inputs also always show FormLabel in its floated state. These input types do not support placeholders the way textual inputs do, so a placeholder is not required (and is ignored by most browsers). Date Time Disabled Add the disabled boolean attribute on an input, a textarea or a select to give it a grayed out appearance, remove pointer events, and prevent focusing. Email address Comments Comments Works with selects Open this select menu One Two Three Readonly plaintext Floating labels also support the plaintext prop on FormControl , which is useful for toggling from an editable input to a plaintext value without affecting the page layout. Empty input Input with value Input groups Floating labels also work inside InputGroup . @ Username When using InputGroup and FormFloatingLabel with validation, place FormFeedback outside InputGroup but inside FormField . @ Username Please choose a username. Always floating Set the always prop on FormFloatingLabel to keep the label floated and the placeholder visible. Email address Password By default, placeholders stay transparent until the control is focused. With always , the placeholder stays visible in both states. Layout When using the grid, place form elements inside Col components. Email address Works with selects Open this select menu One Two Three CSS Variables .example { --bs-form-floating-height: calc(3.75rem + var(--bs-border-width) * 2); --bs-form-floating-line-height: 1.25; --bs-form-floating-padding-x: calc(var(--bs-btn-input-padding-x) * 1.25); --bs-form-floating-padding-y: 1rem; --bs-form-floating-input-padding-t: 1.625rem; --bs-form-floating-input-padding-b: 0.625rem; --bs-form-floating-label-height: 1.5em; --bs-form-floating-label-bg: var(--bs-btn-input-bg); --bs-form-floating-label-disabled-bg: var(--bs-bg-2); --bs-form-floating-label-opacity: 0.65; --bs-form-floating-label-transform: scale(0.85) translateY(-0.5rem) translateX(0.15rem); --bs-form-floating-label-disabled-color: var(--bs-fg-3); --bs-form-floating-transition-property: opacity, transform; --bs-form-floating-transition-duration: 0.1s; --bs-form-floating-transition-timing: ease-in-out; }</description></item><item><title>Field</title><link>https://idea-react.pages.dev/forms/field/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/field/</guid><description>Field A universal layout wrapper for form controls that handles label, description, and validation feedback placement with CSS grid. The Field component provides essential layout, spacing, and functionality for your form input or component of choice. They even scale to support laying out checkboxes, radios, and switches in a two-column layout. Email address We’ll never share your email with anyone else. How it works FormField uses CSS grid to lay out a form control alongside its label, description, and validation feedback. Default layout is a single-column grid where everything stacks vertically. Use this for text inputs, selects, textareas, ranges, input groups, and adorned inputs. Two-column layout activates automatically via :has() when a Checkbox , Radio , or FormSwitch is a direct child. The control sits in the first column while its label, description, and feedback stack in the second. Overhead label — when a FormLabel is present alongside a check, radio, or switch, it spans both columns and sits above the control row. Grouped controls — nest multiple FormField components inside an outer FormField to group radios, checkboxes, or switches under a shared label with shared description and validation feedback. Examples Select Use FormSelect for select controls. Country Choose one… United States Canada United Kingdom Textarea Use FormTextArea for multi-line text controls. Descriptions are optional. Message Be sure to include relevant details. Checkbox When a Checkbox is a direct child, the grid switches to a two-column layout with the checkbox in the first column and its label in the second. Remember me Radio Radios use the same two-column layout. Wrap each Radio and its label in its own FormField . Option one Option two Grouped Wrap multiple FormField components in FormGroup to group related controls under a shared label. The group provides consistent spacing while each inner field keeps its own layout. Shipping method Standard Express Choose your preferred shipping speed. Group cards Set the card prop on each FormField for a card-style treatment that highlights the selected option. Wrap the inner fields in FormGroup with tighter spacing for a more compact look. Select a plan Basic $9/month — For individuals. Pro $29/month — For teams. Switch Switches also trigger the two-column grid. Enable notifications Combobox Comboboxes—as well as datepickers, OTPs, and any other form component—are support as well. Combobox Option one Option two Option three Choose an item from the menu above. Overhead label When a check, radio, or switch needs a field title above it, add a FormLabel . It automatically spans both columns and sits on its own row above the control. Terms and conditions I agree to the terms Please read before agreeing. Descriptions Add FormText after the label and wrap it in FormFieldContent to ensure appropriate spacing and alignment. Subscribe to updates We’ll send you a weekly digest of what’s new. Standard shipping Arrives in 5-7 business days. Username Must be 3-20 characters, letters and numbers only. Validation FormFeedback stacks correctly inside FormField for all control types. Set its type prop to valid for success feedback; it defaults to invalid feedback. Client-side Pass data-bs-validate to ValidationForm to opt in to :user-invalid styling. These pseudo-classes activate after the user interacts with a control. To also show success styling on valid fields, use data-bs-validate=&quot;valid&quot; . Set noValidate to suppress native browser validation tooltips while keeping the constraint validation API available. Email address Please enter a valid email address. Looks good! Agree to terms and conditions You must agree before submitting. Submit Server-side Set the control's validation prop to invalid or valid for server-side validation. Feedback is visible immediately on page load. Email address Please enter a valid email address. Full name Looks good! Agree to terms and conditions You must agree before submitting. Accept marketing emails This field is required.</description></item><item><title>Datepicker</title><link>https://idea-react.pages.dev/forms/datepicker/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/datepicker/</guid><description>Datepicker A flexible calendar and date picker popover with support for input or button toggles, range selection, multiple months, and more. Overview The Bootstrap Datepicker is a wrapper around Vanilla Calendar Pro that provides a consistent, accessible date selection experience. It supports light/dark themes, input binding, and flexible configuration via React props. Datepicker The example applies a width utility through className so the input can accommodate the date format and suggest the expected type of input. How it works Use DatePicker enhanced to enable the datepicker on a native input enhanced renders a text input to avoid conflicts with native browser date pickers; without it, DatePicker retains the browser’s native date input When focused, the calendar popup appears below the input Selecting a date updates the input value and closes the picker The picker also closes on a click outside it, on Escape , or when focus moves to an element outside it The picker respects Bootstrap’s color modes ( data-bs-theme ) Configurable with any Vanilla Calendar Pro option via options.vcpOptions Examples With form field Use the form field component to layout and wrap your inputs with a label, description, and validation feedback messages in a vertical stack. Datepicker field We’ll never share your email with anyone else. With icon Use the form adorn component to add a calendar icon alongside the datepicker input. When the input is inside FormAdornment , the calendar automatically positions relative to the wrapper instead of the input. Select date Min &amp; Max dates Restrict the selectable date range using the min and max props. Event date (2026 only) Multiple dates Enable multiple date selection with selectionMode=&quot;multiple&quot; . Select multiple dates Multiple months Display multiple months side-by-side with the displayMonthsCount option. This is useful for date range selection where users need to see more context. Select date range Date range Select a range of dates with selectionMode=&quot;multiple-ranged&quot; . Use selectedDates to preselect a date range. Select date range Multi-month date range For selecting date ranges that span multiple months, combine selectionMode=&quot;multiple-ranged&quot; with displayMonthsCount={2} to show two months side-by-side, making it easier for users to select across month boundaries. Select date range Options First day of week Set the first day of the week (0 = Sunday, 1 = Monday, etc.) with firstWeekday . Week starts on Sunday Placement Control where the calendar appears relative to the input with placement . Options are left (default), center , right , and auto . Left aligned Center aligned Right aligned Button trigger Use DatePickerButton instead of an input for use cases like dashboard date filters. Set leadingIcon to preserve an icon when the date updates. Select date For date range selection (e.g., dashboard time filters), use selectionMode=&quot;multiple-ranged&quot; . The calendar will close after both start and end dates are selected. Last 7 days You can also display the selected date in a separate element using options.displayElement : &lt;DatePickerButton selectionMode=&quot;multiple-ranged&quot; options={{ displayElement: &quot;#date-display&quot; }} > Choose dates &lt;/DatePickerButton> &lt;span id=&quot;date-display&quot; /> Inline mode Render the calendar inline (always visible, no popup) with DatePickerInline . This is useful for embedding a calendar directly in the page. Inline datepickers with date range selection: Multiple months inline: To bind to a form field, include a hidden input inside the container. The value will be updated with the selected date(s) in YYYY-MM-DD format: Submit Custom date formatting Control how dates are displayed using options.dateFormat . Pass an Intl.DateTimeFormat options object or a custom function. &lt;DatePicker enhanced options={{ dateFormat: { month: &quot;short&quot;, day: &quot;numeric&quot;, year: &quot;numeric&quot; } }} /> &lt;DatePicker enhanced options={{ dateFormat: (date, locale) => date.toLocaleDateString(locale, { month: &quot;short&quot;, day: &quot;numeric&quot; }) }} /> Dark mode The datepicker automatically adapts to Bootstrap’s color modes. When data-bs-theme=&quot;dark&quot; is set on a parent element or the &lt;html> tag, the calendar popup inherits that theme. Inherited from parent When a parent element has a theme, both the input and calendar popup inherit it: Dark mode datepicker Datepicker-only theme Use datepickerTheme to set the datepicker popup’s theme independently of the input. This is useful when you want a light input with a dark datepicker, or vice versa: Light input, dark datepicker CSS Variables .example { --bs-datepicker-padding: 1rem; --bs-datepicker-bg: var(--bs-bg-body); --bs-datepicker-color: var(--bs-fg-body); --bs-datepicker-border-color: var(--bs-border-color-translucent); --bs-datepicker-border-width: var(--bs-border-width); --bs-datepicker-border-radius: var(--bs-radius-7); --bs-datepicker-box-shadow: var(--bs-box-shadow); --bs-datepicker-font-size: var(--bs-font-size-sm); --bs-datepicker-min-width: 280px; --bs-datepicker-zindex: var(--bs-z-menu); --bs-datepicker-header-font-weight: 600; --bs-datepicker-weekday-color: var(--bs-fg-3); --bs-datepicker-day-hover-bg: var(--bs-bg-1); --bs-datepicker-day-selected-bg: var(--bs-primary-bg); --bs-datepicker-day-selected-color: var(--bs-primary-contrast); --bs-datepicker-day-today-bg: var(--bs-bg-2); --bs-datepicker-day-today-color: var(--bs-fg-1); --bs-datepicker-day-disabled-color: var(--bs-fg-4); } Usage DatePicker enhanced , DatePickerButton , and DatePickerInline initialize and dispose the calendar automatically. Pass supported settings as props, plugin settings through options and advanced Vanilla Calendar Pro settings through options.vcpOptions , and receive selected dates with onDatesChange . Options Name Type Default Description min / options.dateMin string, number, Date null Minimum selectable date. Format: YYYY-MM-DD max / options.dateMax string, number, Date null Maximum selectable date. Format: YYYY-MM-DD options.dateFormat object, function null Date formatting. Pass Intl.DateTimeFormat options or a function(date, locale) . options.displayElement string, element, boolean null Element to show formatted date. For buttons, defaults to the button itself. Set to false to disable. displayMonthsCount number 1 Number of months to display side-by-side in the calendar. firstWeekday number 1 First day of week (0 = Sunday, 1 = Monday, etc.) inline boolean false Render calendar inline (always visible, no popup). options.locale string 'default' Locale for date formatting (e.g., 'en-US' , 'de-DE' ) options.positionElement string, element null Element to position the calendar relative to. Automatically detects FormAdornment when present. selectedDates array [] Pre-selected dates in YYYY-MM-DD format selectionMode string 'single' Selection mode: 'single' , 'multiple' , or 'multiple-ranged' placement string 'left' Calendar position relative to input: 'left' , 'center' , 'right' , 'auto' datepickerTheme string null Force datepicker popup theme: 'light' , 'dark' , 'auto' , or null to inherit from ancestor [data-bs-theme] options.vcpOptions object {} Pass-through object for any Vanilla Calendar Pro option</description></item><item><title>Combobox</title><link>https://idea-react.pages.dev/forms/combobox/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/combobox/</guid><description>Combobox A customizable select-like component built with markup-first HTML, powered by the Menu component for positioning and keyboard navigation. Overview The combobox component provides a styled select experience using a Combobox with ComboboxOption children — rendered as a toggle button paired with a menu overlay. Unlike traditional select enhancements, the combobox is markup-first: you declare the options as React children. The JavaScript handles show/hide, selection state, form submission via a hidden input, and keyboard navigation. Full control over menu item content (icons, descriptions, badges, images — anything) Live search/filtering Check mark indicators for selected items Single and multiple selection modes Full keyboard navigation and accessibility Form submission via auto-created hidden input Example Use Combobox with ComboboxOption children. Each selectable option needs a value prop. Option one Option two Option three Placeholders Set placeholder text with the placeholder prop. Combobox displays it when nothing is selected. United States United Kingdom Canada Pre-selected value Set defaultValue on Combobox to pre-select an option, or use value and onChange for controlled selection. The toggle text updates automatically on initialization. Admin Editor Viewer With form field Use the form field component to layout and wrap your combobox with a label, description, and validation feedback messages in a vertical stack. Combobox United States United Kingdom Canada Custom content Since menu items are standard HTML, you can put anything inside them — SVG icons, images, description text, badges, or any other markup. Icons Set icon on ComboboxOption for a leading icon, rendered with the library’s Icon component. HTML CSS JavaScript Descriptions Use the description prop on ComboboxOption for secondary text. The component supplies the flex column layout. Admin Editor Viewer Checked icon Set checkedIcon on each ComboboxOption to show a check mark indicator. It is hidden by default and becomes visible when the option is selected. Active Draft Archived All together Combine all three for a rich menu item layout. Low Medium High Search menu items Enable filtering with search . The component adds a search input and no-results message before the items; customize them with searchPlaceholder and noResultsText . Items are filtered by matching their textContent against the query. United States United Kingdom Canada Australia Germany France Japan Brazil India Mexico Groups Use ComboboxGroup with a label to create labeled groups within the menu. HTML CSS JavaScript Python Ruby Go Multiple select Set multiple for multi-select behavior. Selected items are toggled on click and the menu stays open. The toggle displays the count when more than one item is selected. HTML CSS JavaScript Python Ruby Sizing Use controlSize=&quot;sm&quot; or controlSize=&quot;lg&quot; to change the toggle button’s size. Option one Option two Option one Option two Option one Option two Disabled Add disabled to the toggle button or individual menu items. Option one Option two Available Unavailable Available Form submission For form submission, Combobox creates a hidden input whose name matches the required name prop and whose value updates whenever the selection changes. &lt;Combobox name=&quot;country&quot; defaultValue=&quot;us&quot;> &lt;ComboboxOption value=&quot;us&quot;>United States&lt;/ComboboxOption> &lt;ComboboxOption value=&quot;ca&quot;>Canada&lt;/ComboboxOption> &lt;/Combobox> For multiple selection, the component creates one hidden input per selected value, all sharing the same name. Read these values with FormData.getAll(name) . Usage Combobox manages selection with defaultValue , or value and onChange for controlled state. Pass search , searchNormalize , multiple , and sizing options as props; no plugin initialization is needed. Options Pass options directly as Combobox props. The wrapper manages the menu and form inputs. Name Type Default Description multiple boolean false Enable multi-select mode. Selections toggle and the menu stays open. name string Required Name for the auto-created hidden inputs. placeholder string '' Placeholder text for the toggle. search boolean false Enable search input in the menu. searchNormalize boolean false Normalize accented characters for search matching. Accessibility The combobox component follows WAI-ARIA combobox patterns: The toggle button has aria-haspopup=&quot;listbox&quot; and aria-expanded . Each ComboboxOption receives role=&quot;option&quot; and aria-selected automatically. Full keyboard navigation: Arrow keys, Home, End, Enter, Space, Escape, and Tab. Disabled items have the disabled attribute and aria-disabled=&quot;true&quot; . CSS custom properties The combobox uses CSS custom properties prefixed with --bs-combobox-* for the toggle, and inherits --bs-menu-* properties from the Menu component for the menu overlay. See the upstream variable definitions for the full list of available tokens.</description></item><item><title>Chips</title><link>https://idea-react.pages.dev/forms/chips/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/chips/</guid><description>Chips Small interactive elements representing entities like people, places, tags, or values. Combine with inputs for multi-value fields like skills, categories, or email recipients using themed chips. Overview Chips represent entities and can group or select values in forms and other interactive contexts. They're similar to the older Badges component, but have some meaningful differences. Chip renders a span by default, matching Bootstrap's chip semantics. Use as=&quot;button&quot; when the chip itself needs native button behavior. Chips have one size—they don't scale with the parent font-size like Badges. Chips can have icons, avatars, and dismiss buttons. Chips can be themed, individually or as a group on the parent container. By default, chips use the subtle and text theme tokens, while active state uses the bg and contrast tokens. Native button chips can use the button's disabled state. ChipInput supports keyboard navigation and selection, and gives its chips focus automatically. See examples of all of this in action below. Chips Use Chip for each chip. It renders a span by default; set as=&quot;button&quot; when the chip itself should be a button. Add ChipIcon for a leading icon, ChipImage for an image like an avatar, and ChipDismiss for a remove button. Dismiss buttons use the library’s Icon component and can be nested safely inside the default span . Basic chip With avatar With icon Dismissible Themed chips Set theme to color your chips. Chips are subtle by default as this allows for a clear, themed active state. Default Primary Accent Secondary Success Danger Warning Info Dark Light Inverse Active state Set active to make chips use the solid appearance (bg/contrast). This is useful for toggle-style chip selections. Default Active Default Active Chip input Wrap Chip components and a FormGhost input in ChipInput to create a tag input field. The component enables JavaScript behavior automatically. Chips are grayscale by default, with primary blue for active states, but you can apply any theme color to the container so that chips within inherit the color of your choosing. Type into the input below and press Enter or , to add new chips. Use the Backspace or Delete keys to remove chips. See the Keyboard behavior section for more details. Skills: JavaScript TypeScript Theme variants Set theme on ChipInput to apply a theme color to all chips within. Approved Verified Bug Critical You can also individually apply a theme color to a chip with the chip’s theme prop. Bug Critical Empty state Start with just the ghost input—chips are created as users type. With label Use a form label for better accessibility. Skills React Press Enter or comma to add a skill. Disabled Disable the ghost input to prevent adding new chips, and disable the dismiss buttons on existing chips. Existing chips become non-interactive. Read only Usage ChipInput initializes and disposes the plugin automatically. Pass options as props, and use onValuesChange to receive the current values. Options Pass options directly as ChipInput props: Name Type Default Description separator string | null ',' Character that triggers chip creation when typed. Set to null to disable. allowDuplicates boolean false Allow duplicate chip values. maxChips number | null null Maximum number of chips allowed. null for unlimited. placeholder string '' Placeholder text for dynamically created inputs. dismissible boolean true Add dismiss buttons to created chips. createOnBlur boolean true Create chip from input value when the input loses focus. Keyboard behavior Chip inputs support Mail.app-style keyboard navigation with chip selection. When input is focused Key Action Enter Create chip from current input value , (or separator) Create chip from current input value Backspace / Delete When input is empty, select and focus last chip (first press); pressing again deletes it ← When cursor is at start, move focus to last chip Shift+← Select last chip and extend selection Escape Clear selection, clear input, and blur When a chip is focused Key Action Backspace / Delete Remove selected chips, then select and focus the next closest chip ← Move to previous chip → Move to next chip (or input if at end) Shift+← / Shift+→ Extend selection in that direction Home Move to first chip End Move to input Cmd/Ctrl+A Select all chips Escape Clear selection and focus input Mouse selection Action Effect Click chip Select chip (deselects others) Cmd/Ctrl+Click Toggle chip in selection Shift+Click Range select from anchor to clicked chip Accessibility Associate ChipInputLabel with the chip input to provide an accessible name Chips are focusable and support full keyboard navigation Each ChipDismiss button has aria-label=&quot;Remove&quot; Selected chips have the .active class for visual indication Chips are announced as they are added or removed CSS Chip variables .example { --bs-chip-height: 1.75rem; --bs-chip-padding-x: 0.625rem; --bs-chip-gap: 0.3125rem; --bs-chip-border-radius: var(--bs-radius-pill); --bs-chip-img-size: 1.25rem; --bs-chip-icon-size: 1rem; --bs-chip-dismiss-size: 1rem; --bs-chip-dismiss-opacity: 0.65; --bs-chip-dismiss-hover-opacity: 1; --bs-chip-color: var(--bs-theme-fg, var(--bs-fg-body)); --bs-chip-bg: var(--bs-theme-bg-subtle, var(--bs-bg-2)); --bs-chip-border-color: transparent; --bs-chip-selected-color: var(--bs-theme-contrast, var(--bs-primary-contrast)); --bs-chip-selected-bg: var(--bs-theme-bg, var(--bs-primary-bg)); --bs-chip-selected-border-color: var(--bs-theme-bg, var(--bs-primary-bg)); } Chip input variables These variables are scoped to the ChipInput container. .example { --bs-chip-input-padding-y: 0.75rem; --bs-chip-input-padding-x: 0.75rem; --bs-chip-input-gap: 0.375rem; --bs-chip-input-ghost-min-width: 5rem; --bs-control-fg: var(--bs-btn-input-fg); --bs-control-bg: var(--bs-btn-input-bg); --bs-control-border-width: var(--bs-border-width); --bs-control-border-color: var(--bs-border-color); --bs-control-border-radius: var(--bs-radius-5); }</description></item><item><title>Checkbox</title><link>https://idea-react.pages.dev/forms/checkbox/</link><guid isPermaLink="true">https://idea-react.pages.dev/forms/checkbox/</guid><description>Checkbox Checkbox wraps a native checkbox input with customizable appearance for presenting toggleable options. Basic checkbox Checkbox applies its themed appearance to the native input. This does the following: Overrides the default &lt;input> appearance with themed colors. Renders the :checked and indeterminate icons via a CSS mask on the input’s ::before pseudo-element, so the mark inherits the contrast color and no inline SVG is needed. The appropriate icon is shown based on the input’s state. For folks looking to replace our provided icons, override the --bs-check-icon-checked and --bs-check-icon-indeterminate CSS variables with your own mask-image URLs. Labels and layout are handled with additional HTML and CSS. Indeterminate Checkboxes can utilize the indeterminate pseudo class. There is no available HTML attribute for specifying it; the indeterminate prop sets the native JavaScript property. With form field Wrap Checkbox in a FormField layout wrapper and add your label. The grid layout places the checkbox and label side by side. Example new checkbox Description Add a description or other content after the label. Wrap the label and description in FormFieldContent to ensure appropriate spacing and alignment. Example new checkbox Supporting description for the above label. Theme colors Modify the appearance of checked checkboxes with the theme prop. This will set the checked background and border color to the theme color. Example primary checkbox Example accent checkbox Example secondary checkbox Example success checkbox Example danger checkbox Example warning checkbox Example info checkbox Example dark checkbox Example light checkbox Example inverse checkbox Disabled Set the disabled prop on Checkbox ; its associated FormLabel is automatically styled in a lighter color to indicate the input's state. Example new checkbox Example new checkbox Sizes Set size=&quot;sm&quot; or size=&quot;lg&quot; to make your checkbox appear smaller or larger. Small checkbox Default checkbox Large checkbox CSS Variables Override the checkbox component's CSS variables for visual customization. .example { --bs-check-size: 1.25rem; --bs-check-margin-block: 0.125rem; --bs-check-bg: var(--bs-bg-body); --bs-check-border-color: var(--bs-border-color); --bs-check-border-radius: var(--bs-radius-5); --bs-check-icon-checked: url(&quot;data:image/svg+xml,%3csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 20 20'%3e%3cpath fill='none' stroke='black' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' d='m5.5 10 3 3 6-6'/%3e%3c/svg%3e&quot;); --bs-check-icon-indeterminate: url(&quot;data:image/svg+xml,%3csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 20 20'%3e%3cpath fill='none' stroke='black' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' d='M6 10h8'/%3e%3c/svg%3e&quot;); --bs-check-checked-bg: var(--bs-control-checked-bg); --bs-check-checked-border-color: var(--bs-control-checked-border-color); --bs-check-indeterminate-bg: var(--bs-control-checked-bg); --bs-check-indeterminate-border-color: var(--bs-control-checked-border-color); --bs-check-active-bg: var(--bs-control-active-bg); --bs-check-active-border-color: var(--bs-control-active-border-color); --bs-check-disabled-bg: var(--bs-control-disabled-bg); --bs-check-disabled-opacity: var(--bs-control-disabled-opacity); }</description></item><item><title>Idea React extensions</title><link>https://idea-react.pages.dev/extensions/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/</guid><description>Idea React extensions Idea React complements Bootstrap 6 with reusable React and MobX components. Each extension has its own guide, linked below with its primary purpose. Export Purpose ClickBoundary Detects clicks outside a component boundary CodeBlock Syntax-highlighted code block Countdown Renders a countdown from a target time DialogBox model Collects dialog results through promises MarkdownView Synchronous Markdown rendering with GitHub styles HorizontalMarquee Horizontally scrolls overflowing content Icon Bootstrap Icons font wrapper LiveTSX Renders editable or evaluated TSX examples Loading Full-page loading overlay MonthCalendar Interactive month grid with selectable date entries Nameplate Displays a person with an avatar and name OverlayBox Adds tooltip and popover triggers and positioning PageNav Builds a table of contents from page headings ScrollNav Horizontally scrollable navigation ShareBox Captures content as a shareable image SpinnerButton Button with an inline loading indicator TableSpinner Loading row for a data table TextTruncate Expands and collapses long text Time Formats a date or time value TimeDistance Displays relative time distance Timeline Presents chronological events TypeEcho Animates typed text UserRankView Displays ranked users VerticalMarquee Vertically scrolls overflowing content ZodiacBar Displays zodiac signs for a year range Core Bootstrap component wrappers are documented in the component catalog . Source files and public API types are available in the API reference . Related libraries such as rich-text editing are listed in the Ecosystem .</description></item><item><title>Zodiac bar</title><link>https://idea-react.pages.dev/extensions/zodiac-bar/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/zodiac-bar/</guid><description>Zodiac bar ZodiacBar displays the Chinese zodiac sign for each year in a range, newest first, with an optional link and title per year. Example Usage endYear defaults to the current year. itemOf customizes each item's title and link , and itemClassName restyles the year cards. The exported zodiacOf(year) helper returns the zodiac emoji for any historical year.</description></item><item><title>Vertical marquee</title><link>https://idea-react.pages.dev/extensions/vertical-marquee/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/vertical-marquee/</guid><description>Vertical marquee VerticalMarquee scrolls overflowing content vertically with a CSS animation, suited for notice boards and credit rolls. Example 🎉 Idea React v3 alpha is out 📦 Install with npm i idea-react@next 🧩 Bootstrap 6 official component wrappers ⚡ Powered by MobX and TypeScript Behavior Content shorter than the container stays still; overflowing content scrolls upward in a loop and pauses on hover. Set the scroll duration in seconds to tune the speed. News and announcements See the Horizontal marquee for the horizontal variant.</description></item><item><title>User rank</title><link>https://idea-react.pages.dev/extensions/user-rank/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/user-rank/</guid><description>User rank UserRankView displays a leaderboard: the top three users on a podium with medals, followed by a table of the remaining ranks with avatars, scores, and locations. Example Usage rank lists users ordered by score; the first three render as medal cards and ranks 4–10 render as table rows. linkOf builds the profile link for each user, and address fields from UserAddressProps display each user's location.</description></item><item><title>Type echo</title><link>https://idea-react.pages.dev/extensions/type-echo/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/type-echo/</guid><description>Type echo TypeEcho animates text with a typewriter effect, starting when the element scrolls into view and showing a cursor until the text completes. Example Usage intervals sets the delay between characters in milliseconds (default 150 ). The animation runs once per mount, driven by an IntersectionObserver so off-screen text does not animate early.</description></item><item><title>Timeline</title><link>https://idea-react.pages.dev/extensions/timeline/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/timeline/</guid><description>Timeline Timeline presents chronological events as cards along a vertical line, with a title, time range, participants, and summary per event. Example Usage Each event takes a title , a time tuple of start and optional end, and optionally a summary , a link , and people rendered as Nameplates . timeFormat controls the Time labels.</description></item><item><title>Time distance</title><link>https://idea-react.pages.dev/extensions/time-distance/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/time-distance/</guid><description>Time distance TimeDistance displays how far a moment is from now, in the largest sensible unit, inside a semantic &lt;time> element whose title holds the exact timestamp. Example Usage unitWords localizes the unit labels, while beforeWord and afterWord are appended for past and future moments respectively.</description></item><item><title>Time</title><link>https://idea-react.pages.dev/extensions/time/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/time/</guid><description>Time Time renders a date or time value in a semantic &lt;time> element with a formatted label and a machine-readable dateTime attribute. Example Usage dateTime accepts a Date , timestamp, or date string; format follows the web-utility formatDate tokens such as YYYY , MM , DD , HH , and mm . The text re-renders whenever either prop changes. For relative output such as &quot;3 day(s) before&quot;, use Time distance .</description></item><item><title>Text truncate</title><link>https://idea-react.pages.dev/extensions/text-truncate/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/text-truncate/</guid><description>Text truncate TextTruncate clamps long text to a number of lines and adds an expand/collapse toggle only when the content actually overflows. Example Idea React is a TypeScript-first collection of advanced React components powered by MobX. From dialogs and notifications to live code, editors, and timelines, it brings the building blocks together so you can focus on your application instead of plumbing. This paragraph is long on purpose so the clamp and the expand toggle are visible in the example. Usage A longer biography can be expanded when it overflows its visible lines. rows sets the visible line count (default 3 ). The toggle reports its state through aria-expanded , and overflow is re-checked on window resize and content changes.</description></item><item><title>Table spinner</title><link>https://idea-react.pages.dev/extensions/table-spinner/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/table-spinner/</guid><description>Table spinner TableSpinner renders a loading row for a data table: one centered Spinner in a cell spanning the given number of columns. Example Name Role Score Usage colSpan must match the table's column count; animation , theme , and size style the spinner.</description></item><item><title>Spinner button</title><link>https://idea-react.pages.dev/extensions/spinner-button/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/spinner-button/</guid><description>Spinner button SpinnerButton extends Button with a loading state that shows an inline Spinner and disables the button while work is in progress. Example Submit Usage Submit All Button props pass through, and animation selects the spinner animation. When the button has no children while loading, a visually hidden &quot;Loading...&quot; label keeps it accessible.</description></item><item><title>Share box</title><link>https://idea-react.pages.dev/extensions/share-box/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/share-box/</guid><description>Share box ShareBox captures its children as an image with html2canvas and shares it through the Web Share API . Tapping the box generates a PNG snapshot; tapping the snapshot opens the native share sheet. Example Usage Event poster Rendered DOM content becomes a shareable image. All ShareData fields ( title , text , url , files ) pass to navigator.share() . The snapshot regenerates on window resize, and a Loading overlay is shown while the image renders.</description></item><item><title>Scroll nav</title><link>https://idea-react.pages.dev/extensions/scroll-nav/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/scroll-nav/</guid><description>Scroll nav ScrollNav is a horizontally scrollable navigation bar based on Bootstrap's nav-scroller pattern. Arrow buttons appear automatically when the items overflow the container width. Example Dashboard Friends Explore Suggestions Messages Notifications Profile Settings Help Logout Behavior The component tracks scroll position and container size with a ResizeObserver , showing a left or right caret button only when more content is available in that direction. Each click scrolls by 80% of the visible width with smooth scrolling. Use className to style the scrolling container and navClassName to add class names to the inner navigation element.</description></item><item><title>Page nav</title><link>https://idea-react.pages.dev/extensions/page-nav/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/page-nav/</guid><description>Page nav PageNav builds an in-page table of contents from the document's headings, highlights the section currently in view, and links to each heading using native anchors. The &quot;On this page&quot; panel of this site is rendered with it. Example Usage On mount, the component collects h1 – h6 elements, assigns missing id s, and renders an anchor per heading indented by level. The link whose section is scrolled into view gains the active class and aria-current=&quot;location&quot; . Heading positions are measured relative to the document and refreshed on scrolling and resizing, including after layout changes. The final section stays active when scrolled past its heading. Long link labels wrap while retaining indentation. Scrolling follows the page’s CSS rather than a JavaScript animation. This documentation site enables scroll-behavior: smooth on the root element only under prefers-reduced-motion: no-preference ; reduced motion keeps immediate anchor navigation. Scope and depth rootSelector limits the scan to one container, such as the main article; by default the whole document is scanned. minDepth and depth bound the included heading levels, e.g. minDepth={2} depth={3} lists only h2 and h3 . onItemClick fires with the heading metadata after a link is activated.</description></item><item><title>Popover and tooltip</title><link>https://idea-react.pages.dev/extensions/overlay-box/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/overlay-box/</guid><description>Popover and tooltip Small, contextual overlays for displaying information or custom content. The Idea React OverlayBox wrapper composes Bootstrap 6 tooltip or popover markup with React-triggered behavior. It supports hover, focus, and click triggers with top, right, bottom, and left placement. Popover Overview Click the button below to show and close a popover. Toggle popover Things to know when using popovers: The React wrapper measures its trigger and content, flips to the roomier side, and shifts inside the viewport without a positioning dependency. Resize, scroll and size changes update geometry. By default content stays beside its trigger. Set container to a selector, an element, or a function returning an element to portal elsewhere. Keep overlays used inside modal dialogs within the same dialog to preserve top-layer and focus behavior. Set title for the popover header and detail for the body. Without detail , the wrapper renders a tooltip instead. Triggering popovers on hidden elements will not work. Disabled controls are not interactive, so use a focusable wrapper as the OverlayBox trigger. For a link whose text wraps across multiple lines, apply white-space: nowrap to its styles to keep the panel centered on a single line. The wrapper removes the panel and its aria-describedby reference when it closes or unmounts. Popovers can be triggered from an element inside a shadow DOM. React escapes text by default. Pass JSX to title or detail when you intentionally need HTML; there is no separate sanitizer option. The fade animation honors prefers-reduced-motion . Examples Live demo Titles are set via the title prop and body content is set via detail . Toggle popover Use the title prop for the popover header, not the native HTML title attribute. The wrapper handles the accessible association with aria-describedby . Image content Pass JSX to detail to place rich content, such as an image, inside the popover. Placement Set placement to change the direction. Four options are available: top, right, bottom, and left. Directions are mirrored when using Bootstrap in RTL. Popover on left Popover on top Popover on bottom Popover on right Responsive placement Use placement for the default direction and responsivePlacement for viewport breakpoints. The highest matching breakpoint wins. Open Custom container Pass container=&quot;body&quot; to escape clipping ancestors, or provide an element or a function returning one. The wrapper translates viewport measurements into the overlay's positioned ancestor coordinates. Pointer and focus movement into portal content remain interactive; outside clicks and Escape dismiss it. Hover or focus offset is a main-axis distance or a [crossAxis, mainAxis] pair. padding sets the viewport inset; flip={false} retains the preferred side while still shifting within viewport boundaries. Custom popovers Customize the appearance with the CSS variables on the panel. Set overlayClassName to scope the overrides, then define the variables on that class: .custom-popover { --bs-popover-header-bg: var(--bs-primary-bg); --bs-popover-header-color: var(--bs-primary-contrast); --bs-popover-body-color: var(--bs-primary-contrast); --bs-popover-border-color: var(--bs-primary-bg); --bs-popover-arrow-border: var(--bs-primary-bg); } Custom popover Dismiss on next click Use the focus trigger to dismiss popovers on the user's next click of an element other than the toggle element. Clicks and focus inside the popover itself do not dismiss it , so users can select text or use controls in the content. Dismissible popover A shown popover can also be dismissed by pressing Escape . A popover shown inside a dialog is dismissed on its own: the first Escape closes the popover and a subsequent one closes the dialog. Disabled elements Disabled controls are not interactive, so users cannot hover or click them to trigger a popover. Make the OverlayBox wrapper keyboard-focusable with tabIndex={0} . For disabled popover triggers, you may also prefer a ['hover', 'focus'] trigger so the popover appears as immediate visual feedback; users may not expect to click a disabled element. Disabled button Tooltip Overview Hover the button below to see a tooltip. By default, the tooltip appears above its trigger element. Example tooltip Things to know when using tooltips: The React wrapper uses measured positioning with automatic viewport flipping and shifting, so it does not need Bootstrap's JavaScript plugin or Floating UI. Tooltips are rendered next to the trigger and removed when closed. Provide a title; an empty overlay conveys nothing to users. Triggering tooltips on hidden elements will not work. Disabled controls are not interactive, so make the OverlayBox wrapper keyboard-focusable. For a link whose text wraps across multiple lines, apply white-space: nowrap to the link's styles to keep the tip centered. Tooltips can be triggered from an element inside a shadow DOM. The default trigger is both hover and focus, so keyboard users can reach the tooltip. The fade animation honors prefers-reduced-motion . Examples Tooltips on links Hover over the links below to see tooltips: inline links real text these tooltips on links your own Custom tooltips Customize the appearance with the CSS variables on the tip. Set overlayClassName to scope the overrides, then define the variables on that class: .custom-tooltip { --bs-tooltip-bg: var(--bs-primary-bg); --bs-tooltip-color: var(--bs-primary-contrast); } Custom tooltip Placement Set placement to change the direction. Hover over the buttons below to see the four tooltip directions: top, right, bottom, and left. Directions are mirrored when using Bootstrap in RTL. Tooltip on left Tooltip on top Tooltip on bottom Tooltip on right Responsive placement As with popovers, use responsivePlacement={{ md: 'right', lg: 'bottom' }} alongside a base placement . Changes apply while the tooltip remains open. Custom HTML Pass JSX to the title prop to control the tooltip markup. React handles escaping and rendering, so there is no html option. Tooltip with HTML With an icon: Interactive tooltips Move the pointer onto the tip to reach interactive content inside it, such as a link. The tooltip stays open while the pointer is over the trigger or the tip. It hides when the pointer leaves both, or when you press Escape . This helps satisfy the WCAG 1.4.13 &quot;Content on Hover or Focus&quot; success criterion. Hover, then move onto the tip Disabled elements Disabled controls are not interactive, so make the OverlayBox wrapper keyboard-focusable with tabIndex={0} . Disabled button Accessibility Keep popovers and tooltips accessible to keyboard and assistive technology users by only adding them to HTML elements that are traditionally keyboard-focusable and interactive, such as links or form controls. While other HTML elements can be made focusable with tabindex=&quot;0&quot; , this can create annoying and confusing tab stops for keyboard users. Do not rely solely on hover as the trigger, because it makes the overlay impossible to reach with a keyboard. Avoid large amounts of content in a tooltip or popover that uses the same aria-describedby association: assistive technologies announce the entire content as one continuous stream. Popovers do not manage keyboard focus order; if you need interactive content, consider using a DialogBox instead. CSS Variables Tooltips and popovers use local CSS variables for real-time customization. Override them through overlayClassName or by targeting .tooltip and .popover in a scoped style. See the upstream popover CSS and tooltip CSS for the complete CSS custom property reference. Usage Bootstrap enables popovers and tooltips through a JavaScript plugin. Mount the React component instead—there is no instance to initialize, retrieve, or dispose: Toggle popover The wrapper renders the panel, keeps aria-describedby in sync, and closes it on outside pointer interaction or Escape . Props Prop Type Default Description title ReactNode — Tooltip text or popover header. Required. detail ReactNode — Popover body. When omitted, the overlay is a tooltip. placement 'top' | 'right' | 'bottom' | 'left' 'top' Side of the trigger where the panel appears. trigger 'click' | 'focus' | 'hover' or an array of them ['hover', 'focus'] Interactions that open the panel. delay number | { show: number; hide: number } 0 Delay in milliseconds before showing or hiding. overlayClassName string — Class names for the tooltip or popover panel, useful for scoped theming. Data attributes The plugin's data attributes map directly to props: Bootstrap attribute React prop data-bs-title title data-bs-content detail data-bs-placement placement and a responsivePlacement breakpoint map data-bs-trigger trigger (no manual ; render the overlay conditionally instead) data-bs-custom-class overlayClassName data-bs-html Pass JSX to title or detail data-bs-container container data-bs-offset offset Methods and events The plugin's show , hide , toggle , setContent , and instance methods do not exist in the React wrapper. Render &lt;Popover> or &lt;Tooltip> directly when you need to control visibility or content: Popover content Likewise, use React state and lifecycle instead of show.bs.popover , shown.bs.tooltip , and the other plugin events.</description></item><item><title>Nameplate</title><link>https://idea-react.pages.dev/extensions/nameplate/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/nameplate/</guid><description>Nameplate Nameplate pairs an Avatar with a person's name, for compact author or member listings. Example Usage</description></item><item><title>Month calendar</title><link>https://idea-react.pages.dev/extensions/month-calendar/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/month-calendar/</guid><description>Month calendar MonthCalendar renders an interactive month grid as an accessible table with previous and next month controls, localized weekday names, and selectable date entries. Example Usage value lists DateData entries whose content appears in the matching cell; entries sharing a date are grouped in a popover. onSelect receives the clicked entry and onChange fires when the visible month changes. locale controls weekday formatting and defaults to the browser language; theme styles the header and controls.</description></item><item><title>Markdown view</title><link>https://idea-react.pages.dev/extensions/markdown-view/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/markdown-view/</guid><description>Markdown view MarkdownView synchronously parses a Markdown string with marked and renders the HTML inside an &lt;article> . It adds markdown-body to the root element for use with GitHub Markdown CSS . Load the stylesheet from unpkg.com with a &lt;link /> in your page's &lt;head> , alongside Bootstrap: &lt;link rel=&quot;stylesheet&quot; href=&quot;https://unpkg.com/github-markdown-css@5.9.0/github-markdown.css&quot; /> The component does not import or bundle this stylesheet. Example Usage import { MarkdownView } from 'idea-react'; &lt;MarkdownView aria-label=&quot;Article&quot;>{markdownSource}&lt;/MarkdownView>; Pass Markdown as the string children . Native article attributes, className , and refs pass through. Use as to select another root element. Parsing is synchronous, including during server rendering. Asynchronous marked extensions are not supported. Changing children immediately replaces the rendered HTML. Trusted content Neither marked nor MarkdownView sanitizes HTML. Embedded HTML is rendered as-is, so only pass trusted Markdown. Sanitize untrusted input before rendering it; see marked's security guidance . The previous EditorHTML component and its Editor.js data/parser API have been removed. Pass Markdown text instead of block data. Rich-text HTML from React Bootstrap Editor (see the Ecosystem) is a different format and must not be passed as Markdown.</description></item><item><title>Loading</title><link>https://idea-react.pages.dev/extensions/loading/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/loading/</guid><description>Loading Loading shows a full-page loading overlay with a Spinner and a message. It covers the viewport with a translucent backdrop, so render it only while blocking work is running. Example Usage The children replace the default Loading... text. For loading states inside a button or a table, use the Spinner button or Table spinner instead. Set opacity={100} for a fully opaque backdrop, such as while restoring persisted application state. Keep the covered content inert until restoration finishes so keyboard focus cannot enter it.</description></item><item><title>Live TSX</title><link>https://idea-react.pages.dev/extensions/live-tsx/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/live-tsx/</guid><description>Live TSX LiveTSX renders an editable, instantly evaluated TSX example with react-live . It shows a live preview, a code editor, and any evaluation errors. Usage React element children are serialized to JSX source for the editor; string children are used as the code directly. Provide every referenced component or value through scope . Error handling Evaluation errors render below the editor in a fg-danger block, so broken edits never crash the page.</description></item><item><title>Icon</title><link>https://idea-react.pages.dev/extensions/icon/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/icon/</guid><description>Icon Icon renders a Bootstrap Icons glyph from the icon font. Load the icon font stylesheet once, then reference any icon by name. Example Usage name is the icon name without the bi- prefix; size sets the font size in rem . Icons are decorative by default, so add an aria-label or visually hidden text when an icon conveys meaning on its own.</description></item><item><title>Horizontal marquee</title><link>https://idea-react.pages.dev/extensions/horizontal-marquee/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/horizontal-marquee/</guid><description>Horizontal marquee HorizontalMarquee scrolls overflowing content horizontally with a CSS animation, as a modern replacement for the deprecated &lt;marquee> element. Example Idea React · TypeScript-first Bootstrap 6 and React components powered by MobX · built by the idea2app community Behavior Content narrower than the container stays still; overflowing content scrolls in a loop. The animation pauses while hovered so users can read the text. Announcement text See the Vertical marquee for the vertical variant.</description></item><item><title>DialogBox model</title><link>https://idea-react.pages.dev/extensions/dialog-model/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/dialog-model/</guid><description>DialogBox model The DialogBox model composes the Dialog wrapper with promise-based dialogs. open() returns a promise that resolves or rejects when the dialog closes. Promise-based dialogs Create the model with a render function, then await open() to collect the result. The example below resolves with the submitted numbers and rejects when the dialog is dismissed.</description></item><item><title>Countdown</title><link>https://idea-react.pages.dev/extensions/countdown/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/countdown/</guid><description>Countdown Countdown renders the remaining time to a target moment as a list of time sections, updating every second until the end time is reached. Example Units units lists the sections from largest to smallest. Each scale is the amount of the next smaller unit that makes up one of the current unit, ending at milliseconds. itemClassName styles each section, and onEnd fires once when the countdown reaches zero.</description></item><item><title>Code block</title><link>https://idea-react.pages.dev/extensions/code-block/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/code-block/</guid><description>Code block CodeBlock renders syntax-highlighted code with Shiki . String children are highlighted as-is, while React elements are serialized to JSX source first. Example Language language accepts javascript , jsx , typescript , tsx , css , html , json , sh , or text . The highlighted markup is injected inline, so the block needs no client-side JavaScript. Color scheme Highlight colors follow the inherited CSS color-scheme : light , dark , or light dark to follow the system preference. Bootstrap theme containers work automatically, including nested containers with a different theme. Changing the scheme updates highlighting without rerendering the component.</description></item><item><title>Click boundary</title><link>https://idea-react.pages.dev/extensions/click-boundary/</link><guid isPermaLink="true">https://idea-react.pages.dev/extensions/click-boundary/</guid><description>Click boundary ClickBoundary wraps its children in a container and tells inner clicks apart from outer clicks, which is useful for closing menus, popovers, or other transient surfaces when the user clicks elsewhere. Usage Click inside or outside this box The component listens for click events in the capture phase on window , so outer clicks are detected even when other handlers stop propagation. The listener is removed on unmount. Callbacks onInnerClick fires when the click target is inside the wrapped container. onOuterClick fires for every other click in the document. Both callbacks receive the native MouseEvent .</description></item><item><title>examples</title><link>https://idea-react.pages.dev/examples/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/</guid><description>Examples Explore 33 Bootstrap examples built with Idea React components. Starters Start your next project with these TypeScript and Bootstrap templates.</description></item><item><title>examples/sticky-footer-navbar</title><link>https://idea-react.pages.dev/examples/sticky-footer-navbar/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/sticky-footer-navbar/</guid><description>Search Sticky footer with fixed navbar Pin a footer to the bottom of the viewport in desktop browsers with this custom HTML and CSS. A fixed navbar has been added with padding-top: 60px; on the main > .container . Back to the default sticky footer minus the navbar. Place sticky footer content here.</description></item><item><title>examples/sticky-footer</title><link>https://idea-react.pages.dev/examples/sticky-footer/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/sticky-footer/</guid><description>Sticky footer Pin a footer to the bottom of the viewport in desktop browsers with this custom HTML and CSS. Use the sticky footer with a fixed navbar if need be, too. Place sticky footer content here.</description></item><item><title>examples/starter-template</title><link>https://idea-react.pages.dev/examples/starter-template/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/starter-template/</guid><description>Starter template Get started with Bootstrap Download examples Starter projects Ready to go beyond the starter template? Check out these open source projects that you can quickly duplicate to a new GitHub repository. Guides Read more detailed instructions and documentation on using or contributing to Bootstrap. Created by the Bootstrap team · ©</description></item><item><title>examples/sign-in</title><link>https://idea-react.pages.dev/examples/sign-in/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/sign-in/</guid><description>Please sign in Email address Password Remember me Sign in © 2017–</description></item><item><title>examples/sidebars</title><link>https://idea-react.pages.dev/examples/sidebars/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/sidebars/</guid><description>Sidebars examples Sidebar Sidebar Icon-only Collapsible List group</description></item><item><title>examples/product</title><link>https://idea-react.pages.dev/examples/product/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/product/</guid><description>Aperture Designed for engineers Build anything you want with Aperture Learn more Buy</description></item><item><title>examples/pricing</title><link>https://idea-react.pages.dev/examples/pricing/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/pricing/</guid><description>Pricing example Pricing Quickly build an effective pricing table for your potential customers with this Bootstrap example. It’s built with default Bootstrap components and utilities with little customization. Compare plans</description></item><item><title>examples/navbars-drawer</title><link>https://idea-react.pages.dev/examples/navbars-drawer/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/navbars-drawer/</guid><description>Navbar with drawer examples This example shows how responsive drawer menus work within the navbar. For positioning of navbars, checkout the top and fixed top examples. From the top down, you'll see a dark navbar, light navbar and a responsive navbar—each with drawers built in. Resize your browser window to the large breakpoint to see the toggle for the drawer. Learn more about drawer navbars »</description></item><item><title>examples/navbars</title><link>https://idea-react.pages.dev/examples/navbars/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/navbars/</guid><description>Matching .xl:container... Navbar Centered nav Button Navbar examples This example is a quick exercise to illustrate how the navbar and its contents work. Some navbars extend the width of the viewport, others are confined within a .container . For positioning of navbars, checkout the top and fixed top examples. At the smallest breakpoint, a drawer is used to hide the links and show a menu button to toggle the collapsed content. View navbar docs »</description></item><item><title>examples/navbar-static</title><link>https://idea-react.pages.dev/examples/navbar-static/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/navbar-static/</guid><description>Search Navbar example This example is a quick exercise to illustrate how the top-aligned navbar works. As you scroll, this navbar remains in its original position and moves with the rest of the page. View navbar docs »</description></item><item><title>examples/navbar-fixed</title><link>https://idea-react.pages.dev/examples/navbar-fixed/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/navbar-fixed/</guid><description>Search Navbar example This example is a quick exercise to illustrate how fixed to top navbar works. As you scroll, it will remain fixed to the top of your browser’s viewport. View navbar docs »</description></item><item><title>examples/navbar-bottom</title><link>https://idea-react.pages.dev/examples/navbar-bottom/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/navbar-bottom/</guid><description>Bottom Navbar example This example is a quick exercise to illustrate how the bottom navbar works. View navbar docs »</description></item><item><title>examples/menus</title><link>https://idea-react.pages.dev/examples/menus/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/menus/</guid><description></description></item><item><title>examples/masonry</title><link>https://idea-react.pages.dev/examples/masonry/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/masonry/</guid><description>Bootstrap and Masonry Integrate Masonry with the Bootstrap grid system and cards component. Masonry is not included in Bootstrap. Add it by including the JavaScript plugin manually, or using a CDN like so: &lt;script src=&quot; https://cdn.jsdelivr.net/npm/masonry-layout@4.2.2/dist/masonry.pkgd.min.js &quot; integrity=&quot;sha384-GNFwBvfVxBkLMJpYMOABq3c+d3KnQxudP/mGPkzpZSTYykLBNsZEnG2D9G/X/+7D&quot; crossorigin=&quot;anonymous&quot; async>&lt;/script> By adding data-masonry='{&quot;percentPosition&quot;: true }' to the .row wrapper, we can combine the powers of Bootstrap's responsive grid and Masonry's positioning.</description></item><item><title>examples/list-groups</title><link>https://idea-react.pages.dev/examples/list-groups/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/list-groups/</guid><description>Add new task... First radio With support text underneath to add more detail Second radio Some other text goes here Third radio And we end with another snippet of text Fourth disabled radio This option is disabled First radio With support text underneath to add more detail Second radio Some other text goes here Third radio And we end with another snippet of text Fourth disabled radio This option is disabled</description></item><item><title>examples/jumbotrons</title><link>https://idea-react.pages.dev/examples/jumbotrons/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/jumbotrons/</guid><description>Jumbotron with icon Call to action Secondary link Placeholder jumbotron Call to action Full-width jumbotron Basic jumbotron This is a simple Bootstrap jumbotron that sits within a .container , recreated with built-in utility classes.</description></item><item><title>examples/jumbotron</title><link>https://idea-react.pages.dev/examples/jumbotron/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/jumbotron/</guid><description>Jumbotron example Custom jumbotron Example button Change the background Swap the background-color utility and add a .fg-* color utility to mix up the jumbotron look. Then, mix and match with additional component themes and more. Example button Add borders Or, keep it light and add a border for some added definition to the boundaries of your content. Be sure to look under the hood at the source HTML here as we've adjusted the alignment and sizing of both column's content for equal-height. Example button ©</description></item><item><title>examples/heroes</title><link>https://idea-react.pages.dev/examples/heroes/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/heroes/</guid><description>Heroes examples Centered hero Quickly design and customize responsive mobile-first sites with Bootstrap, the world’s most popular front-end open source toolkit, featuring a responsive grid system, extensive prebuilt components, and powerful JavaScript plugins. Primary button Secondary Centered screenshot Quickly design and customize responsive mobile-first sites with Bootstrap, the world’s most popular front-end open source toolkit, featuring a responsive grid system, extensive prebuilt components, and powerful JavaScript plugins. Primary button Secondary Responsive left-aligned hero with image Quickly design and customize responsive mobile-first sites with Bootstrap, the world’s most popular front-end open source toolkit, featuring a responsive grid system, extensive prebuilt components, and powerful JavaScript plugins. Primary Default Vertically centered hero sign-up form Email address Password Remember me Sign up By clicking Sign up, you agree to the terms of use. Border hero with cropped image and shadows Quickly design and customize responsive mobile-first sites with Bootstrap, the world’s most popular front-end open source toolkit, featuring a responsive grid system, extensive prebuilt components, and powerful JavaScript plugins. Primary Default Dark color hero Quickly design and customize responsive mobile-first sites with Bootstrap, the world’s most popular front-end open source toolkit, featuring a responsive grid system, extensive prebuilt components, and powerful JavaScript plugins. Custom button Secondary</description></item><item><title>examples/headers</title><link>https://idea-react.pages.dev/examples/headers/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/headers/</guid><description>Headers examples Simple header Home Login Sign up Login Sign up Sign out Reports Analytics Sign out Login Sign up Double header Login Sign-up</description></item><item><title>examples/grid</title><link>https://idea-react.pages.dev/examples/grid/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/grid/</guid><description>Idea React grid examples Basic grid layouts to get you familiar with building within the Bootstrap grid system. These examples use a page-local style module to distinguish the columns. Six grid tiers There are six tiers to the Bootstrap grid system, one for each range of devices we support. Each tier starts at a minimum viewport size and automatically applies to the larger devices unless overridden. Three equal columns Get three equal-width columns starting at desktops and scaling to large desktops . On mobile devices, tablets and below, the columns will automatically stack. Three equal columns alternative Set the number of columns on Row to create an evenly divided grid. Three unequal columns Get three columns starting at desktops and scaling to large desktops of various widths. Remember, grid columns should add up to twelve for a single horizontal block. More than that, and columns start stacking no matter the viewport. Two columns Get two columns starting at desktops and scaling to large desktops . 8 columns from md 4 columns from md Full width, single column A column defaults to full width when no responsive span is set. Two columns with two nested columns Per the documentation, nesting is easy—just put a row of columns within an existing column. This gives you two columns starting at desktops and scaling to large desktops , with another two (equal widths) within the larger column. At mobile device sizes, tablets and down, these columns and their nested columns will stack. 8 columns from md 4 columns from md Mixed: mobile and desktop The grid has six responsive tiers: xs (extra small), sm (small), md (medium), lg (large), xl (extra large), and 2xl (extra extra large). Combine the matching props on Col to create flexible layouts. Each tier scales up, so a md prop also applies at larger breakpoints unless overridden. 8 columns from md 6 from xs, 4 from md Mixed: mobile, tablet, and desktop 6 from sm, 8 from lg 6 from xs, 4 from lg Gutters Set horizontal gutter utilities in Row 's className . Set vertical gutter utilities in Row 's className . Set both horizontal and vertical gutter utilities in Row 's className . Containers</description></item><item><title>examples/footers</title><link>https://idea-react.pages.dev/examples/footers/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/footers/</guid><description>© Company, Inc © Company, Inc © Subscribe to our newsletter Monthly digest of what's new and exciting from us. Email address Subscribe © Company, Inc. All rights reserved.</description></item><item><title>examples/features</title><link>https://idea-react.pages.dev/examples/features/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/features/</guid><description>Features examples Columns with icons Hanging icons Custom cards Icon grid Features with title Left-aligned title explaining these awesome features Paragraph of text beneath the heading to explain the heading. We'll add onto it with another sentence and probably just keep going until we run out of words. Primary button</description></item><item><title>examples/drawer-navbar</title><link>https://idea-react.pages.dev/examples/drawer-navbar/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/drawer-navbar/</guid><description>Search Bootstrap Since 2011 Recent updates Suggestions</description></item><item><title>examples/dialogs</title><link>https://idea-react.pages.dev/examples/dialogs/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/dialogs/</guid><description>Modal title This is a modal sheet, a variation of the modal that docks itself to the bottom of the viewport like the newer share sheets in iOS. Save changes Close Enable this setting? You can always change your mind in your account settings. Yes, enable No thanks What's new Great, thanks! Sign up for free Email address Password Sign up By clicking Sign up, you agree to the terms of use. Or use a third-party</description></item><item><title>examples/dashboard</title><link>https://idea-react.pages.dev/examples/dashboard/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/dashboard/</guid><description>Company name Saved reports Settings Sign out Dashboard Share Export This week Section title #</description></item><item><title>examples/cover</title><link>https://idea-react.pages.dev/examples/cover/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/cover/</guid><description>Cover Home Features Contact Cover your page. Cover is a one-page template for building simple and beautiful home pages. Download, edit the text, and add your own fullscreen background photo to make it your own. Learn more Cover template for Bootstrap , by @mdo .</description></item><item><title>examples/checkout</title><link>https://idea-react.pages.dev/examples/checkout/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/checkout/</guid><description>Checkout form Below is an example form built entirely with Bootstrap’s form controls. Each required form group has a validation state that can be triggered by attempting to submit the form without completing it. Your cart 3 Promo code EXAMPLECODE −$5 Total (USD) $20 Redeem Billing address First name Valid first name is required. Last name Valid last name is required. Username @ Your username is required. Email (Optional) Please enter a valid email address for shipping updates. Address Please enter your shipping address. Address 2 (Optional) Country Choose... United States Please select a valid country. State Choose... California Please provide a valid state. Zip Zip code required. Shipping address is the same as my billing address Save this information for next time Payment Continue to checkout © 2017– Company Name</description></item><item><title>examples/cheatsheet</title><link>https://idea-react.pages.dev/examples/cheatsheet/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/cheatsheet/</guid><description>Cheatsheet On this page Contents A well-known quote, contained in a blockquote element. Someone famous in Source Title This may still come in handy in some situations. Responsive image 200x200 Class Default A caption for the above image. Forms Email address We'll never share your email with anyone else. Password Select menu Open this select menu Check me out Radios buttons Upload Checked switch checkbox input Example range Submit Disabled input Disabled select menu Disabled select Can't check this Disabled radios buttons Upload Disabled checked switch checkbox input Disabled range Submit @ @example.com Your vanity URL $ .00 With textarea Email address Password First name Looks good! Last name Looks good! Username @ Please choose a username. City Please provide a valid city. State Choose... ... Please select a valid state. Zip Please provide a valid zip. Agree to terms and conditions You must agree before submitting. Submit form Components Well done! Aww yeah, you successfully read this important alert message. This example text is going to run a bit longer so that you can see how spacing within an alert works with this kind of content. Whenever you need to, be sure to use margin utilities to keep things nice and tidy. Home Library Data Launch demo dialog Launch static backdrop dialog Menu header Separated link Previous Next Previous Next Click to toggle popover Navbar Bootstrap 11 mins ago Hello, world! This is a toast message. Tooltip with HTML</description></item><item><title>examples/carousel</title><link>https://idea-react.pages.dev/examples/carousel/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/carousel/</guid><description>Search Back to top © 2017– Company, Inc. · Privacy · Terms</description></item><item><title>examples/buttons</title><link>https://idea-react.pages.dev/examples/buttons/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/buttons/</guid><description>Secondary action Primary action Primary icon Secondary icon Loading... Loading... Dismiss Dismiss Dismiss Dismiss</description></item><item><title>examples/breadcrumbs</title><link>https://idea-react.pages.dev/examples/breadcrumbs/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/breadcrumbs/</guid><description>Home Library Data Home Library Data Home Library Data Home Library Data</description></item><item><title>examples/blog</title><link>https://idea-react.pages.dev/examples/blog/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/blog/</guid><description>Subscribe Large Sign up Title of a longer featured blog post Multiple lines of text that form the lede, informing new readers quickly and efficiently about what’s most interesting in this post’s contents. Continue reading... World Featured post Nov 12 This is a wider card with supporting text below as a natural lead-in to additional content. Continue reading Thumbnail Design Post title Nov 11 This is a wider card with supporting text below as a natural lead-in to additional content. Continue reading Thumbnail From the Firehose Sample blog post January 1, 2021 by Mark This blog post shows a few different types of content that’s supported and styled with Bootstrap. Basic typography, lists, tables, images, code, and more are all supported as expected. This is some additional paragraph placeholder content. It has been written to fill the available space and show how a longer snippet of text affects the surrounding content. We'll repeat it often to keep the demonstration flowing, so be on the lookout for this exact same string of text. Blockquotes This is an example blockquote in action: Quoted text goes here. This is some additional paragraph placeholder content. It has been written to fill the available space and show how a longer snippet of text affects the surrounding content. We'll repeat it often to keep the demonstration flowing, so be on the lookout for this exact same string of text. Example lists This is some additional paragraph placeholder content. It's a slightly shorter version of the other highly repetitive body text used throughout. This is an example unordered list: And this is an ordered list: And this is a definition list: Inline HTML elements HTML defines a long list of available inline tags, a complete list of which can be found on the Mozilla Developer Network . Most of these elements are styled by browsers with few modifications on our part. Heading This is some additional paragraph placeholder content. It has been written to fill the available space and show how a longer snippet of text affects the surrounding content. We'll repeat it often to keep the demonstration flowing, so be on the lookout for this exact same string of text. Sub-heading This is some additional paragraph placeholder content. It has been written to fill the available space and show how a longer snippet of text affects the surrounding content. We'll repeat it often to keep the demonstration flowing, so be on the lookout for this exact same string of text. Example code block This is some additional paragraph placeholder content. It's a slightly shorter version of the other highly repetitive body text used throughout. Another blog post December 23, 2020 by Jacob This is some additional paragraph placeholder content. It has been written to fill the available space and show how a longer snippet of text affects the surrounding content. We'll repeat it often to keep the demonstration flowing, so be on the lookout for this exact same string of text. Longer quote goes here, maybe with some emphasized text in the middle of it. This is some additional paragraph placeholder content. It has been written to fill the available space and show how a longer snippet of text affects the surrounding content. We'll repeat it often to keep the demonstration flowing, so be on the lookout for this exact same string of text. Example table And don't forget about tables in these posts: This is some additional paragraph placeholder content. It's a slightly shorter version of the other highly repetitive body text used throughout. New feature December 14, 2020 by Chris This is some additional paragraph placeholder content. It has been written to fill the available space and show how a longer snippet of text affects the surrounding content. We'll repeat it often to keep the demonstration flowing, so be on the lookout for this exact same string of text. This is some additional paragraph placeholder content. It's a slightly shorter version of the other highly repetitive body text used throughout. Older Newer About Customize this section to tell your visitors a little bit about your publication, writers, content, or something else entirely. Totally up to you. Recent posts Archives Elsewhere Blog template built for Bootstrap by @mdo . Back to top</description></item><item><title>examples/album</title><link>https://idea-react.pages.dev/examples/album/</link><guid isPermaLink="true">https://idea-react.pages.dev/examples/album/</guid><description>About Add some information about the album below, the author, or any other background context. Make it a few sentences long so folks can pick up some informative tidbits. Then, link them off to some social networking sites or contact information. Contact Album Album example Something short and leading about the collection below—its contents, the creator, etc. Make it short and sweet, but not too short so folks don’t simply skip over it entirely. Back to top Album example is © Bootstrap, but please download and customize it for yourself! New to Bootstrap? Visit the homepage or read our getting started guide .</description></item><item><title>Tables</title><link>https://idea-react.pages.dev/content/tables/</link><guid isPermaLink="true">https://idea-react.pages.dev/content/tables/</guid><description>Tables Documentation and examples for opt-in styling of tables (given their prevalent use in JavaScript plugins) with Bootstrap. Idea React provides the Table wrapper for these examples. Use the striped , stripedColumns , hover , bordered , borderless , and small props for the corresponding variants; card adds the card wrapper, while responsive adds a responsive wrapper. Set verticalAlign , captionTop , and stacked to apply the corresponding table styles. Pass a breakpoint to responsive or stacked to apply its style responsively, for example responsive=&quot;md&quot; . The as prop replaces the table root, or the outer wrapper when responsive is enabled. With an explicit as , additional props, className , and the ref are forwarded to that root; responsive tables retain their inner table and its Bootstrap variants. Overview Due to the widespread use of tables across third-party widgets like calendars and date pickers, Table styles are opt-in . The wrapper applies the base styling; use its variant props or className to customize the table. Nested tables can be styled independently from their parent. Here is the default appearance of Table . # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Variants Use theme color utilities through className to style a table, row, or cell. These adapt to color modes as well. Class Heading Heading Default Cell Cell Accented tables Striped rows Use the striped prop to add zebra-striping to any table row within the &lt;tbody> . # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Striped columns Use the stripedColumns prop to add zebra-striping to any table column. # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social These props can also be combined with table variants: # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Hoverable rows Add the hover prop to enable a hover state on table rows within a &lt;tbody> . # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social These hoverable rows can also be combined with the striped rows variant: # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Active tables Highlight a row or cell by passing className=&quot;table-active&quot; to it. # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social How do the variants and accented tables work? For the accented tables (striped rows, striped columns, hoverable rows, and active tables), we start by setting the background of a table cell to var(--bs-theme-bg-subtle, var(--bs-table-bg)) . The theme utility classes each set --bs-theme-bg-subtle and --bs-theme-fg on the table, row, or cell whose className includes the utility, and the cells inside pick them up. This way, we don't get into trouble if semi-transparent colors are used as table backgrounds. A box shadow is layered on top of any specified background-color , and the stripe, active, and hover factors mix the theme foreground into the cells. Text colors are generated the same way, and borders use --bs-theme-border when a theme class sets it, or --bs-table-border-color otherwise. Table borders Bordered tables Add the bordered prop for borders on all sides of the table and cells. # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Pass border-color utilities through className to change colors: # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Tables without borders Add the borderless prop for a table without borders. # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Card-like tables Need a bordered, rounded table without nesting it in a card? Wrap the table and clip the corners. With utilities Use border, border-radius, and overflow utilities through the wrapper's className . Pass a margin utility through Table 's className to remove its bottom margin. # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social With a card wrapper Set card on Table to add a wrapper that rounds corners like a card, clips cell backgrounds, and removes the last row's bottom border so it does not stack on the wrapper. # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Small tables Set the small prop on Table to make it more compact by cutting all cell padding in half. # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Table group dividers Add className=&quot;table-group-divider&quot; to a row group to add a thicker, darker border between table groups. Customize its color with the border-top-color style. # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Vertical alignment Header cells are vertically aligned to the bottom. Body cells inherit their alignment from the table and are aligned to the top by default. Set verticalAlign on Table to control body cell alignment; vertical-alignment utility classes can still be passed through className on individual rows or cells. Heading 1 Heading 2 Heading 3 Heading 4 This cell inherits vertical-align: middle; from the table This cell inherits vertical-align: middle; from the table This cell inherits vertical-align: middle; from the table This here is some placeholder text, intended to take up quite a bit of vertical space, to demonstrate how the vertical alignment works in the preceding cells. This cell inherits vertical-align: bottom; from the table row This cell inherits vertical-align: bottom; from the table row This cell inherits vertical-align: bottom; from the table row This here is some placeholder text, intended to take up quite a bit of vertical space, to demonstrate how the vertical alignment works in the preceding cells. This cell inherits vertical-align: middle; from the table This cell inherits vertical-align: middle; from the table This cell is aligned to the top. This here is some placeholder text, intended to take up quite a bit of vertical space, to demonstrate how the vertical alignment works in the preceding cells. Nesting Border styles, active styles, and table variants are not inherited by nested tables. # First Last Handle 1 Mark Otto @mdo Header Header Header A First Last B First Last C First Last 3 John Doe @social How nesting works To prevent any styles from leaking to nested tables, we use the child combinator ( > ) selector in our CSS. Since we need to target all the td s and th s in the thead , tbody , and tfoot , our selector would look pretty long without it. As such, we use the rather odd looking .table > :not(caption) > * > * selector to target all td s and th s of the .table , but none of any potential nested tables. Note that if you add &lt;tr> s as direct children of a table, those &lt;tr> will be wrapped in a &lt;tbody> by default, thus making our selectors work as intended. Footer # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Footer Footer Footer Footer Caption A &lt;caption> functions like a heading for a table. It helps users with screen readers to find a table and understand what it's about and decide if they want to read it. List of users # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Set the captionTop prop on Table to place its caption above the table. List of users # First Last Handle 1 Mark Otto @mdo 2 Jacob Thornton @fat 3 John Doe @social Stacked tables Set stacked on Table to convert its rows into stacked blocks when space is limited. Each row becomes a vertical block with the first cell acting as a bold title and the remaining cells displayed as label–value pairs. Labels are generated from data-cell attributes on each cell. The responsive prop provides the container query required for responsive stacking. Pass stacked=&quot;md&quot; or another breakpoint to stack only below a specific container width. Without a breakpoint, the rows are always stacked. Name Type Default Description backdrop boolean or 'static' true Includes a backdrop element. Specify static for a backdrop which doesn't close on click. keyboard boolean true Closes the component when escape key is pressed. focus boolean true Puts the focus on the component when initialized. Responsive tables Responsive tables allow tables to be scrolled horizontally with ease. Make any table responsive across all viewports with the responsive prop. Or, pick a maximum breakpoint with which to have a responsive table up to by using responsive=&quot;sm&quot; , responsive=&quot;md&quot; , responsive=&quot;lg&quot; , responsive=&quot;xl&quot; , or responsive=&quot;2xl&quot; . The wrapper also acts as the container query context for stacked tables. Responsive tables make use of overflow-y: hidden , which clips off any content that goes beyond the bottom or top edges of the table. In particular, this can clip off menus and other third-party widgets. Always responsive Across every breakpoint, use responsive for horizontally scrolling tables. # Heading Heading Heading Heading Heading Heading Heading Heading Heading 1 Cell Cell Cell Cell Cell Cell Cell Cell Cell 2 Cell Cell Cell Cell Cell Cell Cell Cell Cell 3 Cell Cell Cell Cell Cell Cell Cell Cell Cell Breakpoint specific Use responsive=&quot;sm&quot; , responsive=&quot;md&quot; , responsive=&quot;lg&quot; , responsive=&quot;xl&quot; , or responsive=&quot;2xl&quot; as needed to create responsive tables up to a particular breakpoint. From that breakpoint and up, the table will behave normally and not scroll horizontally. # Heading Heading Heading Heading Heading Heading Heading Heading 1 Cell Cell Cell Cell Cell Cell Cell Cell 2 Cell Cell Cell Cell Cell Cell Cell Cell 3 Cell Cell Cell Cell Cell Cell Cell Cell CSS Tables use CSS variables for real-time customization. Since .table styles are opt-in, nested tables stay independent from their parent. The factor variables ( --table-striped-bg-factor , --table-active-bg-factor , and --table-hover-bg-factor ) determine the contrast in table variants. See the upstream table CSS for the CSS custom property reference.</description></item><item><title>Images</title><link>https://idea-react.pages.dev/content/images/</link><guid isPermaLink="true">https://idea-react.pages.dev/content/images/</guid><description>Images Use the Image wrapper for responsive images and common image treatments without manually adding their underlying classes. Set fluid for responsive sizing, thumbnail for a framed image, rounded for rounded corners, or roundedCircle for a circular image. Native image attributes such as src , alt , width , and height pass through. For semantic image-and-caption groups, use Figure , FigureImage , and FigureCaption . FigureImage is responsive by default. Responsive images Set fluid on Image to constrain its width to the parent while preserving its aspect ratio. Image thumbnails Set thumbnail on Image to give it a framed, rounded appearance. Aligning images Use layout utilities through className to float or align images. To center an image as a block, combine mx-auto and d-block ; a parent with text alignment can center an inline image. Figures Use Figure , FigureImage , and FigureCaption to group an image with an optional caption. Figure is a flex container, so layout and alignment utilities can be passed through its className . FigureImage is responsive by default; set fluid={false} to opt out. A caption for the above image. And with a reverse alignment: A caption for the above image. Picture Use the native &lt;picture> element when selecting among image sources. Put Image inside it so image styling applies to the rendered image, not its parent. Give Image an alt value that describes the image, or alt=&quot;&quot; when it is only decorative. The placeholder value in the example below should be replaced with meaningful text. &lt;picture> &lt;source srcset=&quot;...&quot; type=&quot;image/svg+xml&quot; /> &lt;img src=&quot;...&quot; alt=&quot;...&quot; /> &lt;/picture> CSS Variables Bootstrap exposes CSS variables for customizing image thumbnails and figures. Component CSS variable Default Image thumbnail --bs-thumbnail-padding .25rem --bs-thumbnail-bg var(--bs-bg-body) --bs-thumbnail-border-width var(--bs-border-width) --bs-thumbnail-border-color var(--bs-border-color) --bs-thumbnail-border-radius var(--bs-radius-5) --bs-thumbnail-box-shadow var(--bs-box-shadow-sm) Figure --bs-figure-gap calc(var(--bs-spacer) * .5) --bs-figure-caption-font-size var(--bs-font-size-sm) --bs-figure-caption-color var(--bs-fg-3)</description></item><item><title>Bootstrap components</title><link>https://idea-react.pages.dev/components/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/</guid><description>Bootstrap components Bootstrap 6 provides a comprehensive set of responsive interface components. This catalog mirrors the component groups in Bootstrap v6.0.0-alpha.1 . All upstream component groups have React wrappers and local guides, including interactive behavior and the documented visual variants. Built-in wrappers Component Notes Accordion Native exclusive, always-open, compact, and nested disclosures Alert Contextual feedback with optional dismissal Avatar Image or initials avatars with status and stacks Badge Themed status labels and counters Breadcrumb Location hierarchy with custom dividers Button Native buttons and links with themes Button group Grouped buttons, toolbars, and toggle groups Card Flexible content containers with headers and footers Carousel Slides, indicators, captions, controls, and autoplay Close button Dismiss controls for overlays and drawers Collapse Vertical or horizontal panels with synchronized triggers Dialog Native dialog element and promise-based DialogBox model Drawer Edge-aligned dialogs for navigation and panels List group Stacked content, actions, variants, and layouts Menu Keyboard-accessible contextual menus Nav Tabs , pills, underline, and vertical navigation Nav overflow Overflow-aware horizontal navigation Navbar Responsive navigation landmark Pagination Themed page links with active and disabled states Placeholder Sized, colored, animated loading skeletons Popover Rich contextual overlays Progress Accessible, stacked, striped, and animated bars Scrollspy Active navigation tracking for scrolling sections Spinner Border and growing loading indicators Stepper Responsive timelines and navigation-based steps Tab Keyboard-accessible tabbed panels Toasts Themed notifications with dismissal Toggler Class and attribute toggles for one or many targets Tooltip Accessible text hints See the separate Forms guide for the Bootstrap form components. Root elements Single-root components accept as to select an HTML tag or another React component: &lt;Card as=&quot;article&quot; aria-label=&quot;News&quot;> &lt;CardTitle as=&quot;h2&quot;>Latest news&lt;/CardTitle> &lt;/Card> &lt;Button as={RouterLink} to=&quot;/docs&quot; theme=&quot;primary&quot;> Documentation &lt;/Button> The selected component's additional props are inferred and forwarded, including required props. Idea React's own props keep their meaning when names overlap. Custom roots must forward DOM props and refs, and preserve the native capabilities required by behavioral components. Class component refs still reference the instance. Fragment-root and multiple-root components are excluded. Idea React extensions Idea React also includes components without a direct Bootstrap equivalent. See the extension catalog for the complete public component list and quick descriptions. Additional Bootstrap layout and content wrappers cover Grid , Images , and Tables .</description></item><item><title>Tooltips</title><link>https://idea-react.pages.dev/components/tooltip/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/tooltip/</guid><description>Tooltips Custom replacement for browser tooltips—themed with CSS variables and positioned by Idea React’s OverlayBox . Overview Hover the button below to see a tooltip. By default, the tooltip will appear above their trigger element (the child of OverlayBox ). Hover me Things to know when using tooltips with OverlayBox : Provide a non-empty title so the tooltip has a meaningful accessible description. Specify container=&quot;body&quot; to avoid rendering problems in more complex components (like our input groups, button groups, etc). Triggering tooltips on hidden elements will not work. Tooltips for disabled elements must be triggered on a wrapper element. When triggered from links whose text spans multiple lines, tooltips will be centered. Use white-space: nowrap in the link's styles to avoid this behavior. Unmount OverlayBox together with its trigger so the tooltip and positioning listeners are cleaned up. Tooltips can be triggered thanks to an element inside a shadow DOM. Got all that? Great, let’s see how they work with some examples. Pass rich content as React nodes instead of injecting untrusted HTML. React escapes text content by default. The animation effect of this component is dependent on the prefers-reduced-motion media query. Examples Tooltips on links Hover over the links below to see tooltips: Placeholder text to demonstrate some inline links with tooltips. This is now just filler, no killer. Content placed here just to mimic the presence of real text . And all that to give you an idea of how tooltips would look when used in real-world situations. So hopefully you’ve now seen how these tooltips on links can work in practice, once you use them on your own site or project. Use the title prop on OverlayBox , rather than the native title attribute on the trigger, to avoid duplicate browser tooltips. Custom tooltips You can customize the appearance of tooltips using CSS variables . We pass a CSS module class through overlayClassName to scope our custom appearance and use it to override a local CSS variable. Custom tooltip Placement Set placement to change the direction. Hover over the buttons below to see the four tooltips directions: top, right, bottom, and left. Directions are mirrored when using Bootstrap in RTL. Tooltip on top Tooltip on right Tooltip on bottom Tooltip on left Responsive placement Change placement at different breakpoints using responsivePlacement={{ md: 'right', lg: 'bottom' }} , where each breakpoint is one of sm , md , lg , xl , or 2xl . Top → md:right → lg:bottom Left → lg:top Resize your browser to see the tooltip placement change at different breakpoints. Custom HTML And with custom HTML added: Tooltip with HTML With an icon (rendered through Icon ): Tooltip with icon Interactive tooltips Move the pointer onto the tip to reach interactive content inside it, such as a link. The tooltip stays open while the pointer is over the trigger or the tip. It hides when the pointer leaves both, or when you press the Escape key. This helps satisfy the WCAG 1.4.13 “Content on Hover or Focus” success criterion. Interactive tooltip Disabled elements Disabled controls are not interactive, so users cannot focus, hover, or click them to trigger a tooltip. As a workaround, place the control inside a keyboard-focusable wrapper and use that wrapper as the OverlayBox trigger. Disabled button CSS Variables Local CSS custom properties expose the component’s colors, spacing, borders, and transitions. Override them through style or a CSS module. The defaults below come from the Bootstrap stylesheet used by Idea React; see the upstream variable reference . Variable Default --bs-tooltip-zindex var(--bs-z-tooltip) --bs-tooltip-max-width 200px --bs-tooltip-padding-x var(--bs-spacer-3) --bs-tooltip-padding-y calc(var(--bs-spacer) * 0.375) --bs-tooltip-font-size var(--bs-font-size-sm) --bs-tooltip-color var(--bs-bg-body) --bs-tooltip-bg var(--bs-fg-body) --bs-tooltip-border-radius var(--bs-radius-5) --bs-tooltip-opacity 0.95 --bs-tooltip-arrow-width 0.8rem --bs-tooltip-arrow-height 0.4rem --bs-tooltip-transition-property opacity --bs-tooltip-transition-duration 0.15s --bs-tooltip-transition-timing linear Usage Delegated tooltips To enable tooltips on many triggers at once—including elements added to the DOM later—render an OverlayBox for each trigger in your React list. React mounts and removes the overlays with their triggers; no selector-based plugin initialization is needed. Markup Wrap the trigger in OverlayBox and provide its title . It renders the Tooltip markup, places it relative to the trigger, and connects it with aria-describedby . Keep tooltips accessible to keyboard and assistive technology users by only adding them to HTML elements that are traditionally keyboard-focusable and interactive (such as links or form controls). While other HTML elements can be made focusable by adding tabIndex={0} , this can create annoying and confusing tab stops on non-interactive elements for keyboard users, and most assistive technologies currently do not announce tooltips in this situation. Additionally, do not rely solely on hover as the trigger for your tooltips as this will make them impossible to trigger for keyboard users. A shown tooltip can be dismissed by pressing the Escape key, helping satisfy the WCAG 1.4.13 “Content on Hover or Focus” success criterion. The tooltip also stays open while the pointer moves onto the tip, so users can reach interactive content inside it. As with dropdown menus, a tooltip shown inside a dialog is dismissed on its own: the first Escape closes the tooltip and a subsequent one closes the dialog. Options OverlayBox prop Default Description title required Tooltip text or rich React content. trigger hover and focus Choose &quot;click&quot; , &quot;hover&quot; , &quot;focus&quot; , or a combination as an array. placement &quot;top&quot; Preferred direction: top , right , bottom , or left . responsivePlacement — Override direction at named breakpoints. container alongside trigger A selector, DOM element, or callback returning an element. delay 0 Show/hide delay in milliseconds, or { show: 500, hide: 100 } . offset 8 Distance from the trigger, or a [crossAxis, mainAxis] pair. padding 8 Viewport inset for overflow avoidance. flip true Flip direction when space is constrained. overlayClassName — Apply a CSS module class to the tooltip.</description></item><item><title>Toggler</title><link>https://idea-react.pages.dev/components/toggler/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/toggler/</guid><description>Toggler Toggle attributes or classes on click using the Toggler component. Works with any attribute except id . Toggler is an interactive component that can be used to avoid writing small or one-off JavaScript snippets to create interactive elements. Instead of writing custom JavaScript, use its attribute , value , and target props to toggle attribute values, changes classes, and more on click events. Examples Toggle class Toggle the class of an element by setting attribute=&quot;class&quot; and passing the class name as value . Without a target , the component toggles itself. Remove existing If the element already has the class specified in value , toggling will remove it. Clicking again adds it back. Target element Use target to toggle the class of another element. Target elements can supply their own data-bs-attribute and data-bs-value overrides. Multiple elements Use a class name selector in target to toggle the class of multiple elements. Toggle attribute Toggle attributes by setting the attribute and value props. For example, toggling the hidden attribute: You could also use this to toggle the disabled attribute on a fieldset element to disable all the controls within. Or any other ideas you can think of with attributes. Usage Options Name Type Default Description as 'button' , 'div' or 'span' 'button' Trigger element. Non-button triggers receive a button role and keyboard support. target string — Selector for affected elements. Omit it to toggle the trigger itself. attribute string 'class' Attribute to toggle. Changing id is not supported. value string, number, boolean or null — Class or attribute value to toggle. Events Use onToggled(elements) to respond after the matched elements have been updated.</description></item><item><title>Toasts</title><link>https://idea-react.pages.dev/components/toasts/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/toasts/</guid><description>Toasts Push notifications to your visitors with a toast, a lightweight and easily customizable alert message. Toasts are lightweight notifications designed to mimic the push notifications that have been popularized by mobile and desktop operating systems. They’re built with flexbox, so they’re easy to align and position. Overview Things to know when using the Toast model: Toasts are opt-in: create a Toast model and mount its Component before calling open() . Toasts automatically hide after delay milliseconds; pass delay: 0 to keep one visible until it is dismissed. The animation effect of this component is dependent on the prefers-reduced-motion media query. Examples Basic To encourage extensible and predictable toasts, we recommend a header and body. Toast headers use display: flex , allowing easy alignment with margin and flexbox utilities passed through className . Toasts are as flexible as you need and have very little required markup. At a minimum, we require a single element to contain your “toasted” content and strongly encourage a dismiss button. Live example Click the button below to show a toast (positioned with our utilities in the lower right corner) that has been hidden by default. Translucent Toasts are slightly translucent to blend in with what’s below them. Pass translucent to ToastItem or Toast.open() to enhance the translucency with a backdrop blur and saturation filter. Stacking You can stack toasts by wrapping them in a toast container, which will vertically add some spacing. Dark toasts Set a toast to dark mode by setting data-bs-theme=&quot;dark&quot; on a parent element. Variants Set the theme prop to apply a theme color to the toast. Use theme color utilities through className on individual elements. Custom content Customize your toasts by removing sub-components, adding your own content, or passing utility class names through className . For example, render Icon for a hide control and use flexbox utilities to adjust the layout. Alternatively, you can also add additional controls and components to toasts. Instant By default, toasts fade in and out. To disable the animation, pass instant to ToastItem or Toast.open() . The toast then appears without the CSS transition. Placement Place toasts with custom CSS as you need them. The top right is often used for notifications, as is the top middle. Use the position prop on ToastContainer or toast.Component for a standard viewport position. If you’re only ever going to show one toast at a time, put the positioning styles right on ToastItem . For systems that generate more notifications, consider using a wrapping element so they can easily stack. Use flexbox utilities through ToastContainer 's className to align toasts horizontally or vertically. Accessibility Toasts are intended to be small interruptions to your visitors or users, so to help those with screen readers and similar assistive technologies, you should wrap your toasts in an aria-live region . Changes to live regions (such as injecting/updating a toast component) are automatically announced by screen readers without needing to move the user’s focus or otherwise interrupt the user. Additionally, include aria-atomic=&quot;true&quot; to ensure that the entire toast is always announced as a single (atomic) unit, rather than just announcing what was changed (which could lead to problems if you only update part of the toast’s content, or if displaying the same toast content at a later point in time). If the information needed is important for the process, e.g. for a list of errors in a form, then use the alert component instead of toast. Note that the live region needs to be present in the markup before the toast is generated or updated. If you dynamically generate both at the same time and inject them into the page, they will generally not be announced by assistive technologies. You also need to adapt the role and aria-live level depending on the content. If it’s an important message like an error, use role=&quot;alert&quot; aria-live=&quot;assertive&quot; , otherwise use role=&quot;status&quot; aria-live=&quot;polite&quot; attributes. As the content you’re displaying changes, be sure to update the delay timeout so that users have enough time to read the toast. When using delay: 0 , you must add a close button to allow users to dismiss the toast. While technically it’s possible to add focusable/actionable controls (such as additional buttons or links) in your toast, you should avoid doing this for autohiding toasts. Even if you give the toast a long delay timeout , keyboard and assistive technology users may find it difficult to reach the toast in time to take action (since toasts don’t receive focus when they are displayed). If you absolutely must have further controls, we recommend using a toast with delay: 0 . CSS Variables Local CSS custom properties expose the component’s colors, spacing, borders, and transitions. Override them through style or a CSS module. The defaults below come from the Bootstrap stylesheet used by Idea React; see the upstream variable reference . Variable Default --bs-toast-zindex var(--bs-z-toast) --bs-toast-padding-x 1rem --bs-toast-padding-y 0.75rem --bs-toast-spacing 1.5rem --bs-toast-max-width 350px --bs-toast-font-size var(--bs-font-size-sm) --bs-toast-bg var(--bs-bg-body) --bs-toast-border-width var(--bs-border-width) --bs-toast-border-color var(--bs-border-color-translucent) --bs-toast-box-shadow var(--bs-box-shadow) --bs-toast-header-color var(--bs-fg-3) --bs-toast-header-bg var(--bs-bg-1) --bs-toast-header-border-color var(--bs-border-color-translucent) --bs-toast-transition-property opacity, display --bs-toast-transition-duration 0.15s --bs-toast-transition-timing linear Usage Create a Toast model and mount its Component to establish the live region before showing notifications. Call open({ title, body, delay }) to append a toast. The live example above demonstrates this React integration. Options Message option Default Description body required Toast body as a React node. title — Optional toast heading. delay 3000 Milliseconds before hiding; 0 disables automatic dismissal. id generated Supply an ID to replace an existing notification or dismiss it later. role &quot;status&quot; Use &quot;alert&quot; for urgent messages and an appropriate live-region priority. theme — Contextual theme color. translucent false Blur and saturate the background. instant false Skip the CSS transition. Methods open(message) returns a promise that resolves when that notification closes. Call close(id) to dismiss an individual notification.</description></item><item><title>Tab</title><link>https://idea-react.pages.dev/components/tab/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/tab/</guid><description>Tab Create toggleable content panes using any of our navigation or list group components. Tabs supports navigation styles such as variant=&quot;tabs&quot; and variant=&quot;pills&quot; , as well as a variant=&quot;list-group&quot; presentation. Nav tab Give Tabs a unique id , then add Tab children with an eventKey and label . The component creates matching tab controls and content panes, including their accessibility attributes. Tabs forwards the Nav layout and styling props fill , justified , vertical , cardHeader , and navbar to the tab list. vertical also enables vertical keyboard navigation; an explicit orientation takes precedence. These Nav-only props do not affect the list-group variant. With buttons Tabs use button controls rather than navigation links. Tabs renders the tab list and its tablist role on an inner element, and generates the button controls. Pills The tabs plugin also works with pills. And with vertical pills. Set vertical to give the tab list the corresponding layout, aria-orientation , and keyboard behavior. List groups Use Tabs with variant=&quot;list-group&quot; for a list-group presentation. Add Tab children as usual; the component generates the controls and corresponding content panels. Accessibility Dynamic tabbed interfaces, as described in the ARIA Authoring Practices Guide tabs pattern , require tab roles and additional aria- attributes to convey their structure and current state. Tabs generates these attributes and uses buttons for controls that switch content rather than navigate to another page. In line with the ARIA Authoring Practices pattern, only the currently active tab receives keyboard focus. Tabs sets tabIndex={-1} on inactive controls. Once the active tab has focus, the cursor keys activate the previous/next tab. The Home and End keys activate the first and last enabled tabs, respectively. The component changes the roving tabindex accordingly: horizontal lists use Left/Right, while vertical lists use Up/Down. In general, to facilitate keyboard navigation, it’s recommended to make the tab panels themselves focusable as well. Tabs supplies tabIndex={0} for each panel. The tab JavaScript plugin does not support tabbed interfaces that contain menus, as these cause both usability and accessibility issues. From a usability perspective, the fact that the currently displayed tab’s trigger element is not immediately visible (as it’s inside the closed menu) can cause confusion. From an accessibility point of view, there is currently no sensible way to map this sort of construct to a standard WAI ARIA pattern, meaning that it cannot be easily made understandable to users of assistive technologies. Usage Use defaultActiveKey for the initially selected tab, or activeKey with onChange for a controlled selection. Disabled tabs cannot be activated and are skipped during keyboard navigation. Fade effect Content panes fade in by default. The pane you leave hides immediately, because two in-flow panes cannot cross-fade without one stacking under the other. Set fade={false} to switch the fade off. &lt;Tabs id=&quot;instant-tabs&quot; defaultActiveKey=&quot;home&quot; fade={false}> &lt;Tab eventKey=&quot;home&quot; label=&quot;Home&quot;> Home content &lt;/Tab> &lt;Tab eventKey=&quot;profile&quot; label=&quot;Profile&quot;> Profile content &lt;/Tab> &lt;/Tabs> Events Use onChange(eventKey) to respond to selection changes instead of registering Bootstrap plugin events.</description></item><item><title>Stepper</title><link>https://idea-react.pages.dev/components/stepper/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/stepper/</guid><description>Stepper Create timelines, wizards, or step-by-step progress bars. Ideal for shopping carts, sign-up forms, and more. Use Stepper and StepperItem for ordered steps, StepperNav and StepperLink for navigation, and StepperOverflow for scrollable horizontal steps. The horizontal prop accepts true or a breakpoint such as &quot;sm&quot; ; items accept active and theme . Examples Stepper renders an ordered list and uses CSS Grid for layout. Steps are vertical by default; set its horizontal prop to a breakpoint to switch to a horizontal layout responsively. Basic Here’s a simple example of a vertical stepper. Create account Confirm email Update profile Finish Responsive For container-query-based horizontal layouts, place Stepper inside a parent with the contains-inline utility applied through className , then set the horizontal prop to the desired breakpoint. Create account Confirm email Update profile Finish Gap Customize the gap with styles that override the --bs-stepper-gap CSS variable. Create account Confirm email Update profile Finish Variants Create account Confirm email Update profile Finish Overflow Wrap a horizontal stepper in StepperOverflow to enable horizontal scrolling when it exceeds its parent. It uses container-type: inline-size to support container queries. Create account Verify email address Complete profile setup Add payment method Review and confirm Finish onboarding Complex Add additional content beyond labels to provide more context within each step, such as descriptions, helper messages, status indicators, or other decorative elements. Create Create an account. Confirm Confirm your email. Set-up Configure your profile. Finish Welcome aboard! Mix with other components, like badges, and our theme helpers to create a more unique steppers. Create account Complete Confirm email Complete Update profile In-progress Finish Pending Alignment Use text alignment utilities on the wrapper around Stepper (which uses display: inline-grid ) to align the steps. The inline grid arrangement keeps steps equal width and ensures connecting lines are rendered correctly. Default stepper Confirm email Update profile Finish Center stepper Confirm email Update profile Finish End stepper Confirm email Update profile Finish Apply a full-width utility through Stepper 's className to make it span the available width. Step items will stretch to fill the space; alignment does not affect full-width steppers. Create account Confirm email Update profile Finish With anchors Use StepperLink for steps that navigate between pages. Use StepperButton for steps that trigger an action within the current page. Use link utilities through StepperLink 's className for quick color control. Create account Confirm email Update profile Finish CSS Variables Customize the component with the following local CSS variables. Override them through the wrapper’s style prop or your own CSS module. CSS variable Default --bs-stepper-size 2rem --bs-stepper-gap 1rem --bs-stepper-font-size var(--bs-font-size-sm) --bs-stepper-text-gap 0.5rem --bs-stepper-track-size 0.125rem --bs-stepper-bg var(--bs-bg-2) --bs-stepper-active-color var(--bs-primary-contrast) --bs-stepper-active-bg var(--bs-primary-bg) Overflow wrapper The StepperOverflow wrapper establishes an inline-size query container with horizontal scrolling. The horizontal stepper retains its minimum content width, keeping labels readable when the available space is narrow.</description></item><item><title>Spinners</title><link>https://idea-react.pages.dev/components/spinner/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/spinner/</guid><description>Spinners Use Spinner to indicate a component or page loading state. It is styled with CSS and requires no JavaScript. Spinner accepts animation=&quot;border&quot; or &quot;grow&quot; , size=&quot;sm&quot; , and native element attributes. SpinnerIcon applies the rotation animation to an Icon from the icon font. Spinner visibility can be controlled by rendering it conditionally. Customize its color with className , alignment with layout utilities, and size with its size prop. For accessibility, provide an accessible name such as aria-label=&quot;Loading&quot; when Spinner uses role=&quot;status&quot; . The animation effect depends on the prefers-reduced-motion media query. See the reduced motion section of our accessibility documentation . Border spinner Use the border spinners for a lightweight loading indicator. Loading Loading… Growing spinner If you don’t fancy a border spinner, switch to the grow spinner. While it doesn’t technically spin, it does repeatedly grow! Variants Spinners use currentColor , so pass a text-color utility through className to customize their appearance. Size Spinner is 1em square by default. Set size=&quot;sm&quot; for a smaller indicator that fits inside other components. Or, use custom CSS or inline styles to change the dimensions as needed. Custom spinners Use SpinnerIcon to apply the rotation animation to an Icon . CSS Variables Customize the component with the following local CSS variables. Override them through the wrapper’s style prop or your own CSS module. Border spinner tokens: CSS variable Default --bs-spinner-width 1em --bs-spinner-height 1em --bs-spinner-border-width 0.125em --bs-spinner-animation-speed 1s --bs-spinner-animation-timing-function linear --bs-spinner-animation-name spinner-border Growing spinner tokens: CSS variable Default --bs-spinner-width 1em --bs-spinner-height 1em --bs-spinner-animation-speed 1s --bs-spinner-animation-timing-function linear --bs-spinner-animation-name spinner-border Keyframes Used for creating the CSS animations for our spinners. The border spinner rotates through 360deg ; the grow spinner scales from 0 to its full size while fading in. Use SpinnerIcon to apply the rotation animation to an icon from the icon font.</description></item><item><title>Scrollspy</title><link>https://idea-react.pages.dev/components/scrollspy/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/scrollspy/</guid><description>Scrollspy Automatically update Bootstrap navigation or list group components based on scroll position to indicate which link is currently active in the viewport. How it works ScrollSpy marks navigation links as active when the section referenced by their href is scrolled into view. It works with Nav and ListGroup , as well as other in-page links. To start, scrollspy requires two things: a navigation, list group, or a simple set of links, plus a scrollable container. The scrollable container can be the &lt;body> or a custom element with a set height and overflow-y: scroll . Use ScrollSpy as the scrollable container and set target=&quot;#navId&quot; , where navId is the unique id of the associated navigation. The component supplies a focusable tabIndex={0} for keyboard access. As you scroll the container, the active state is added to and removed from links in the associated navigation. Links must point to an existing element id ; for example, NavLink with href=&quot;#home&quot; requires a matching section with id=&quot;home&quot; . Target elements that are not visible will be ignored. See the Non-visible elements section below. Target id s are matched with getElementById , so ids containing special or percent-encoded characters (for example #item.1 , #section:overview , or #%2Fpath ) resolve correctly. Detection Scrollspy uses an IntersectionObserver to track sections without scroll-position polling. Detection is deterministic and driven entirely by an activation line near the top of the scroll container. The active section is the deepest one whose top has scrolled past the activation line, like the section you’re currently reading. While scrolling through the gap between two headings, the last activated section stays active until the next one crosses the line. At the very top of the container, before any section crosses the line, the first section stays active. At the very bottom of the container, the last section is activated even if its top never reaches the line (handy for short final sections). Set where the activation line sits with topMargin (a more user-friendly % or px value from the top of the scroll root, such as 96px to sit below a stickied navbar), or take full control with the raw IntersectionObserver rootMargin string. See Options . Jump to the debug overlay section to visualize the activation line in action. Examples Navbar Scroll the area below the navbar and watch the active state change. Open the menu and watch its items be highlighted as well. Nested nav Scrollspy also works with nested .nav s. If a nested .nav is .active , its parents will also be .active . Scroll the area next to the navbar and watch the active class change. List group ScrollSpy also works with ListGroup . Scroll the area next to the list group and watch the active state change. Simple anchors ScrollSpy is not limited to Nav and ListGroup ; it also works with in-page links. Scroll the area and watch the active state change. Debug overlay It can be hard to picture exactly where Scrollspy decides a section is active. Enable the debug prop to draw red guides over the scroll container and illustrate the behavior. The red dashed line near the top is the activation line. A section becomes active as its heading scrolls above this line. In this example it sits at 96px . The red bottom zone lights up when you reach the bottom of the container. This is where the last section stays active even if its heading never reaches the activation line. Scroll the example and watch the highlighted navigation item change as headings cross the line. Guide positions are computed from the same topMargin / rootMargin detection math the component uses. First Last First section Watch the activation line while scrolling this container. Last section The bottom zone selects the final section. Non-visible elements Target elements that aren’t visible will be ignored and their corresponding nav items won’t receive an .active class. Scrollspy instances initialized in a non-visible wrapper will ignore all target elements. Use the refresh method to check for observable elements once the wrapper becomes visible. Call the component’s refresh() method after revealing content outside React; changes to its props are observed automatically. Usage The component initializes on mount and releases its observers and listeners on unmount. Set scrollRoot=&quot;window&quot; to observe page scrolling instead of the component's own scrollable element. Options Pass options as React props: Name Type Default Description rootMargin string or null null Advanced IntersectionObserver root margin. When set, it takes precedence over topMargin , for example 0px 0px -40% . smoothScroll boolean false Smoothly scroll to a clicked target, then update the URL hash and move focus to it. target string — Selector for the navigation whose links match the observed sections. threshold number[] [0] IntersectionObserver thresholds. topMargin string '12%' Position of the activation line from the top of the scroll root. Accepts percentages or pixels. scrollRoot 'self' or 'window' 'self' Element or viewport scrolling. debug boolean false Draw the activation line and bottom-zone guides. Methods Use the instance method refresh() after adding, removing, or revealing observed DOM content outside React. Children and relevant prop changes refresh the component automatically. Events Use onActiveChange(id) to respond when a different section becomes active.</description></item><item><title>Progress</title><link>https://idea-react.pages.dev/components/progress/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/progress/</guid><description>Progress Use Progress and ProgressStack to display progress bars, including stacked bars, striped backgrounds, animation, and text labels. How it works Progress renders an accessible progress indicator and visual bar. It does not use the HTML &lt;progress> element , which allows the component to support stacking, animation, and labels inside the bar. Progress uses value , min , and max to set the current and range values, and generates the accessibility attributes automatically. Provide an accessible name with aria-label or aria-labelledby . Pass a label as Progress 's children. Use barProps to pass styles or utility classes to the inner bar. Use ProgressStack to group multiple progress components into a stacked bar. Put that all together, and you have the following examples. Progress generates both elements and the value attributes from value , min , and max . Provide an accessible name; pass labels as children and inner-bar utilities through barProps . ProgressStack uses CSS to place each segment’s calculated width on its outer element. Bar sizing Width Use width utilities through Progress 's barProps.className when you need to adjust the visual bar width. Height Set the height on Progress itself; the inner bar resizes automatically. Labels Pass a label as children of Progress . 25% Long labels By default, the content inside Progress is clipped to the bar. If the bar is shorter than its label, the content may become unreadable. To change this behavior, pass the overflow-visible utility through barProps.className . Labels longer than the progress bar may not be fully accessible because their text color must contrast with both the track and bar backgrounds. Use caution when implementing this example. If the text can overlap the progress bar, we often recommend displaying the label outside of the progress bar for better accessibility. Backgrounds Set theme on Progress to choose a theme color for its bar. For custom colors, pass a background utility through barProps.className . Conveying meaning to assistive technologies: Color alone is not conveyed to screen reader users. Ensure that information is also clear from the content, or include it in the accessible name with aria-label or aria-labelledby . If you’re adding labels to progress bars with a custom background color, make sure to also set an appropriate text color , so the labels remain readable and have sufficient contrast. We recommend using the theme contrast helper classes. 25% 50% 75% 100% Multiple bars Place multiple Progress components inside ProgressStack to create a single stacked bar. In this case, set each segment's value on Progress ; do not set a separate width on its inner bar. Striped Set striped on Progress to apply a gradient stripe over the bar's background color. Animated stripes Set animated as well as striped on Progress to animate the stripes from right to left. CSS Variables Customize the component with the following local CSS variables. Override them through the wrapper’s style prop or your own CSS module. CSS variable Default --bs-progress-height 1rem --bs-progress-font-size var(--bs-font-size-sm) --bs-progress-bg var(--bs-bg-2) --bs-progress-border-radius var(--bs-radius-5) --bs-progress-box-shadow var(--bs-box-shadow-inset) --bs-progress-bar-color var(--bs-white) --bs-progress-bar-bg var(--bs-primary-bg) --bs-progress-bar-transition width 0.6s ease --bs-progress-bar-animation progress-bar-stripes 1s linear infinite Keyframes Used when the animated prop is enabled. The animation moves the striped background from one stripe width to zero, producing continuous motion from right to left.</description></item><item><title>Popover</title><link>https://idea-react.pages.dev/components/popover/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/popover/</guid><description>Popover Small, contextual overlays for displaying custom content and information via JavaScript. Overview Click the button below to show and close a popover. Toggle popover Things to know when using popovers with OverlayBox : Provide meaningful title and detail content; use detail for the popover body. Specify container=&quot;body&quot; to avoid rendering problems in more complex components (like our input groups, button groups, etc). Triggering popovers on hidden elements will not work. Popovers for disabled elements must be triggered on a wrapper element. When triggered from links whose text wraps across multiple lines, popovers will be centered between the links' overall width. Apply white-space: nowrap to the link's styles to avoid this behavior. Unmount OverlayBox together with its trigger so the popover and positioning listeners are cleaned up. Popovers can be triggered thanks to an element inside a shadow DOM. Pass rich content as React nodes instead of injecting untrusted HTML. React escapes text content by default. The animation effect of this component is dependent on the prefers-reduced-motion media query. Keep reading to see how popovers work with some examples. Examples Live demo Titles are set via title and body content is set via detail on OverlayBox . Use the title prop on OverlayBox , rather than the native title attribute on the trigger, to avoid duplicate browser tooltips. Toggle popover Placement Set placement to change the direction. Four options are available: top, right, bottom, and left. Directions are mirrored when using Bootstrap in RTL. Popover on left Popover on top Popover on bottom Popover on right Responsive placement Change placement at different breakpoints using responsivePlacement={{ md: 'right', lg: 'bottom' }} , where each breakpoint is one of sm , md , lg , xl , or 2xl . Top → md:right → lg:bottom Left → lg:top Resize your browser to see the popover placement change at different breakpoints. Custom container When you have some styles on a parent element that interfere with a popover, you’ll want to specify a custom container so that the popover’s HTML appears within that element instead. This is common in responsive tables, input groups, and the like. Popover in body Another situation where you’ll want to set an explicit custom container are popovers inside a dialog , to make sure that the popover itself is appended to the dialog. This is particularly important for popovers that contain interactive elements – dialogs will trap focus, so unless the popover is a child element of the dialog, users won’t be able to focus or activate these interactive elements. Toggle popover Custom popovers You can customize the appearance of popovers using CSS variables . We pass a CSS module class through overlayClassName to scope our custom appearance and use it to override some of the local CSS variables. Custom popover Dismiss on next click Use the focus trigger to dismiss popovers on the user’s next click of an element other than the toggle element. Clicks and focus inside the popover itself do not dismiss it , so users can select text or use controls in the content. Dismissing on next click requires specific HTML for proper cross-browser and cross-platform behavior. For an anchor trigger, include a tabindex . Dismissible popover A shown popover can also be dismissed by pressing the Escape key. As with dropdown menus, a popover shown inside a dialog is dismissed on its own: the first Escape closes the popover and a subsequent one closes the dialog. Disabled elements Disabled controls are not interactive, so users cannot hover or click them to trigger a popover. As a workaround, place the control inside a keyboard-focusable wrapper and use that wrapper as the OverlayBox trigger. For disabled popover triggers, you may also prefer trigger={[&quot;hover&quot;, &quot;focus&quot;]} so that the popover appears as immediate visual feedback to your users as they may not expect to click on a disabled element. Disabled button CSS Variables Local CSS custom properties expose the component’s colors, spacing, borders, and transitions. Override them through style or a CSS module. The defaults below come from the Bootstrap stylesheet used by Idea React; see the upstream variable reference . Variable Default --bs-popover-zindex var(--bs-z-popover) --bs-popover-max-width 280px --bs-popover-font-size var(--bs-font-size-sm) --bs-popover-bg var(--bs-bg-body) --bs-popover-border-width var(--bs-border-width) --bs-popover-border-color var(--bs-border-color-translucent) --bs-popover-border-radius var(--bs-radius-7) --bs-popover-inner-border-radius calc(var(--bs-radius-7) - var(--bs-border-width)) --bs-popover-box-shadow var(--bs-box-shadow) --bs-popover-header-padding-x var(--bs-spacer) --bs-popover-header-padding-y var(--bs-spacer-3) --bs-popover-header-font-size var(--bs-font-size-sm) --bs-popover-header-color inherit --bs-popover-header-bg var(--bs-bg-1) --bs-popover-body-padding-x var(--bs-spacer) --bs-popover-body-padding-y var(--bs-spacer-3) --bs-popover-body-color var(--bs-fg-body) --bs-popover-arrow-width 1rem --bs-popover-arrow-height 0.5rem --bs-popover-arrow-border var(--bs-popover-border-color) --bs-popover-transition-property opacity --bs-popover-transition-duration 0.15s --bs-popover-transition-timing linear Usage Keep popovers accessible to keyboard and assistive technology users by only adding them to HTML elements that are traditionally keyboard-focusable and interactive (such as links or form controls). While other HTML elements can be made focusable by adding tabIndex={0} , this can create annoying and confusing tab stops on non-interactive elements for keyboard users, and most assistive technologies currently do not announce popovers in this situation. Additionally, do not rely solely on hover as the trigger for your popovers as this will make them impossible to trigger for keyboard users. Avoid adding an excessive amount of rich content in popovers. Once popovers are displayed, their content is tied to the trigger element with the aria-describedby attribute, causing all of the popover’s content to be announced to assistive technology users as one long, uninterrupted stream. Popovers do not manage keyboard focus order, and their placement can be random in the DOM, so be careful when adding interactive elements (like forms or links), as it may lead to an illogical focus order or make the popover content itself completely unreachable for keyboard users. In cases where you must use these elements, consider using a dialog instead. Options OverlayBox prop Default Description title required Popover heading as a React node. detail — Popover body as a React node. Without it, OverlayBox renders a tooltip. trigger hover and focus Use &quot;click&quot; for the click-to-toggle examples, &quot;focus&quot; to dismiss on blur, or an array of triggers. placement &quot;top&quot; Preferred direction: top , right , bottom , or left . responsivePlacement — Override direction at named breakpoints. container alongside trigger A selector, DOM element, or callback returning an element. Keep dialog overlays in the dialog’s top layer. delay 0 Show/hide delay in milliseconds, or { show: 500, hide: 100 } . offset 12 Distance from the trigger, or a [crossAxis, mainAxis] pair. padding 8 Viewport inset for overflow avoidance. flip true Flip direction when space is constrained. overlayClassName — Apply a CSS module class to the popover.</description></item><item><title>Placeholder</title><link>https://idea-react.pages.dev/components/placeholder/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/placeholder/</guid><description>Placeholder Use loading placeholders (skeleton loaders) for your components or pages to indicate something may still be loading. Use Placeholder for skeleton shapes and animation, and PlaceholderButton for a disabled button-shaped placeholder. Their props generate the component styles discussed below. About Placeholders are built with HTML and CSS and need no JavaScript. Render them conditionally to control visibility, and use the Placeholder props to set their color, size, width, or animation. When animating several placeholders together, render them as children of an animated Placeholder . Example In the example below, we take a typical card component and recreate it with placeholders applied to create a “loading card”. Size and proportions are the same between the two. 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 Render Placeholder for a skeleton shape, and use Col to set its grid width. Use the as prop when the placeholder should render as a different element. PlaceholderButton applies the button sizing and disabled state for button-shaped placeholders. The use of aria-hidden=&quot;true&quot; only indicates that the element should be hidden to screen readers. The loading behavior of the placeholder depends on how authors will actually use the placeholder styles, how they plan to update things, etc. Some JavaScript code may be needed to swap the state of the placeholder and inform AT users of the update. Width Set the width prop for a fixed or percentage width, use Col for grid sizing, or pass Bootstrap width utilities through className . Color By default, Placeholder uses currentColor . Set its theme prop to choose a theme color, or use className for a custom color. Sizing The size of Placeholder follows the typographic style of its parent. Set size to &quot;lg&quot; , &quot;sm&quot; , or &quot;xs&quot; to use a sizing modifier. Animation Set Placeholder 's animation prop to &quot;wave&quot; for the default loading animation, or &quot;pulse&quot; for an opacity pulse. &quot;glow&quot; remains available as a compatibility alias for &quot;pulse&quot; . Text Set animation on Placeholder to apply the loading animation to text. Working on it… CSS Variables CSS variable Default --bs-placeholder-opacity-max 0.18 --bs-placeholder-opacity-min 0.1 --bs-placeholder-wave-opacity-max 1 --bs-placeholder-wave-opacity-min 0.4</description></item><item><title>Pagination</title><link>https://idea-react.pages.dev/components/pagination/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/pagination/</guid><description>Pagination Documentation and examples for showing pagination to indicate a series of related content exists across multiple pages. Compose Pagination , PageItem , PageLink , and PageText inside a labelled navigation element. Pagination accepts theme and size ; links inherit active and disabled from their PageItem . Overview Pagination renders the page links as a list, providing large hit areas and allowing screen readers to announce the available links. Place it inside a navigation landmark so assistive technologies can identify its purpose. If the page has more than one navigation landmark, give the pagination landmark a descriptive accessible name, such as &quot;Search results pages&quot;. Previous 1 2 3 Next Working with icons Looking to use an icon or symbol in place of text for some pagination links? Be sure to provide proper screen reader support with aria attributes. « 1 2 3 » Active Set active on PageItem to indicate the current page. When PageLink renders as a link, it also sets aria-current=&quot;page&quot; for assistive technologies. Previous 1 2 3 Next For a non-interactive current page, render PageText instead of a link; it does not need aria-current . Disabled Set disabled on PageItem to disable its PageLink . The component removes the destination and click handler, supplies aria-disabled , and excludes the link from keyboard focus. Previous 1 2 3 Next Variants Set theme on Pagination to apply a semantic theme color across the component, including hover, focus, and the active page item. Previous 1 2 3 Next Previous 1 2 3 Next Previous 1 2 3 Next Previous 1 2 3 Next Previous 1 2 3 Next Previous 1 2 3 Next Previous 1 2 3 Next Previous 1 2 3 Next Sizing Set the size prop to &quot;lg&quot; or &quot;sm&quot; to change the pagination size. 1 2 3 1 2 3 1 2 3 Alignment Align pagination by passing flexbox utilities through className , such as className=&quot;justify-content-center&quot; : Previous 1 2 3 Next Or pass className=&quot;justify-content-end&quot; : Previous 1 2 3 Next CSS Variables Customize the component with the following local CSS variables. Override them through the wrapper’s style prop or your own CSS module. CSS variable Default --bs-pagination-min-height var(--bs-btn-input-min-height) --bs-pagination-padding-x var(--bs-btn-input-padding-x) --bs-pagination-padding-y var(--bs-btn-input-padding-y) --bs-pagination-font-size var(--bs-btn-input-font-size) --bs-pagination-color var(--bs-link-color) --bs-pagination-bg var(--bs-bg-body) --bs-pagination-border-width var(--bs-border-width) --bs-pagination-border-color var(--bs-border-color) --bs-pagination-border-radius var(--bs-btn-input-border-radius) --bs-pagination-hover-color var(--bs-link-hover-color) --bs-pagination-hover-bg var(--bs-bg-1) --bs-pagination-hover-border-color var(--bs-border-color) --bs-pagination-active-color var(--bs-theme-contrast, var(--bs-primary-contrast)) --bs-pagination-active-bg var(--bs-theme-bg, var(--bs-primary-bg)) --bs-pagination-active-border-color var(--bs-theme-bg, var(--bs-primary-bg)) --bs-pagination-disabled-color var(--bs-fg-3) --bs-pagination-disabled-bg var(--bs-bg-2) --bs-pagination-disabled-border-color var(--bs-border-color)</description></item><item><title>Navbar</title><link>https://idea-react.pages.dev/components/navbar/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/navbar/</guid><description>Navbar Create flexible, responsive navigation bars. Includes support for branding, navigation, and a built-in drawer for mobile. Example Here’s a navbar that includes most supported sub-components and a responsive right drawer with our Drawer component . Resize the browser to preview responsive behavior. How it works Here’s what you need to know before getting started with the navbar: Use Navbar as the root, set expand to control the responsive breakpoint, and set theme to choose its color scheme. Navbars and their contents are fluid by default. Change the container to limit their horizontal width in different ways. Use our margin , padding , and flex utility classes for controlling spacing and alignment within navbars. Navbars are responsive by default using our drawer component . On mobile, navigation links slide in from the side as a drawer. Navbar renders a semantic &lt;nav> landmark by default. If you change its element with as , provide an appropriate navigation landmark. Indicate the current item by using aria-current=&quot;page&quot; for the current page or aria-current=&quot;true&quot; for the current item in a set. The animation effect depends on the prefers-reduced-motion media query. See the reduced motion accessibility guidance . Supported content Navbars come with built-in support for a handful of sub-components. Choose from the following as needed: NavbarBrand for your company, product, or project name. NavbarNav for lightweight navigation links, including menus. NavbarToggler for navigation toggling and drawer behaviors. Flex and spacing utilities for any form controls and actions. NavbarText for vertically centered text. Brand Use NavbarBrand for a brand name or link. It renders an anchor by default; set as=&quot;span&quot; when the brand is not a link. Text Pass the brand text as NavbarBrand 's children. Image Place an Image inside NavbarBrand to use an image as the brand. Image and text To combine an image and text, place both inside NavbarBrand and pass layout utilities through the Image component's className . Nav NavbarNav contains NavLink items and supports navigation variants. Set Navbar 's expand prop for responsive layout. Navigation in navbars also grows to occupy horizontal space to keep the contents aligned. Set active on NavLink to indicate the current page. Also set aria-current=&quot;page&quot; on the active NavLink . And because we use classes for our navs, you can avoid the list-based approach entirely if you like. You can also use menus in your navbar. Wrap each menu in NavItem for its positioning, as shown below. Forms Place various form controls and components within a navbar: Immediate child elements of Navbar use flex layout and default to justify-content: space-between . Use additional flex utilities as needed to adjust this behavior. Input groups work, too. If the navbar is primarily a form, use the Form wrapper as its container. Various buttons are supported as part of these navbar forms, too. This is also a great reminder that vertical alignment utilities can be used to align different sized elements. Text Use NavbarText for text in a navbar; it adjusts vertical alignment and horizontal spacing. Mix and match with other components and utilities as needed. Dark navbar To make a navbar dark, set theme=&quot;dark&quot; on Navbar . Translucent navbar Set translucent to blur and saturate the background of a navbar. This works well for navbars positioned over content, such as fixed or sticky navbars. Color schemes Navbar themes use Bootstrap's CSS variables. The default is our &quot;light navbar&quot; for use with light background colors, but you can also apply data-bs-theme=&quot;dark&quot; to the .navbar parent for dark background colors. Then, customize with .bg-* and additional utilities. &lt;Navbar theme=&quot;dark&quot; /> &lt;Navbar theme=&quot;dark&quot; className=&quot;bg-primary&quot; /> &lt;Navbar theme=&quot;light&quot; className=&quot;bg-1&quot; /> Containers Although it’s not required, you can wrap Navbar in a Container to center it on a page, or place a Container inside Navbar to center only its contents. An inner Container is required for a fixed or static top navbar . Use any of the responsive containers to change how wide the content in your navbar is presented. Placement Use our position utilities to place navbars in non-static positions. Choose from fixed to the top, fixed to the bottom, stickied to the top (scrolls with the page until it reaches the top, then stays there), or stickied to the bottom (scrolls with the page until it reaches the bottom, then stays there). Fixed navbars use position: fixed , meaning they’re pulled from the normal flow of the DOM and may require custom CSS (e.g., padding-top on the &lt;body> ) to prevent overlap with other elements. Responsive behaviors Navbars use NavbarToggler and the expand prop to determine when their content appears in a drawer or inline. Pass a breakpoint such as expand=&quot;md&quot; ; in combination with other utilities, you can easily choose when to show or hide particular elements. For navbars that never collapse, use expand={true} . For navbars that always show the drawer, use expand={false} . Drawer By default, navbars use the drawer component for their responsive behavior. This provides a modern drawer-style menu that slides in from any side of the screen. Drawer placement You can customize which side the drawer appears from using its placement prop: &quot;start&quot; - slides in from the left (or right in RTL) &quot;end&quot; - slides in from the right (or left in RTL) &quot;top&quot; - slides in from the top &quot;bottom&quot; - slides in from the bottom These examples show the drawer below the md breakpoint. Click the toggler on a narrow screen to see it slide in from different directions. Toggler Navbar togglers are left-aligned by default, but when placed after a sibling such as NavbarBrand , they automatically align to the far right. Reversing the component order reverses the toggler placement. The first example collapses below the md breakpoint; the following examples always keep the toggler visible. Click it to open the drawer. To toggle inline content outside the responsive navbar examples, pass its selector to CollapseToggle with the navbarToggler prop: With no brand shown in the navbar (the brand is hidden inside the drawer): With a brand name shown on the left and toggler on the right: With a toggler on the left and brand name on the right: External content Sometimes you want to use the drawer plugin to trigger a container element for content that structurally sits outside of the .navbar . Because our plugin works on the id and data-bs-target matching, that’s easily done! When you do this, we recommend including additional JavaScript to move the focus programmatically to the container when it is opened. Otherwise, keyboard users and users of assistive technologies will likely have a hard time finding the newly revealed content - particularly if the container that was opened comes before the toggler in the document’s structure. We also recommend making sure that the toggler has the aria-controls attribute, pointing to the id of the content container. In theory, this allows assistive technology users to jump directly from the toggler to the container it controls–but support for this is currently quite patchy. CSS Variables Use CSS custom properties on the component to customize its appearance without recompiling Bootstrap. .navbar { --bs-navbar-padding-x: 0; --bs-navbar-padding-y: 0.5rem; --bs-navbar-min-height: 3.5rem; --bs-navbar-color: var(--bs-fg-2); --bs-navbar-hover-color: var(--bs-fg-1); --bs-navbar-disabled-color: var(--bs-fg-3); --bs-navbar-active-color: var(--bs-fg-body); --bs-navbar-brand-margin-end: 1rem; --bs-navbar-brand-font-size: var(--bs-font-size-md); --bs-navbar-brand-font-weight: var(--bs-font-weight-medium); --bs-navbar-brand-color: var(--bs-fg-body); --bs-navbar-brand-hover-color: var(--bs-fg-body); --bs-navbar-nav-link-padding-x: 0.75rem; --bs-navbar-toggler-width: 2rem; --bs-navbar-toggler-padding-y: 0.25rem; --bs-navbar-toggler-padding-x: 0.75rem; --bs-navbar-toggler-font-size: var(--bs-font-size-lg); --bs-navbar-toggler-border-color: color-mix(in oklch, var(--bs-fg-body) 15%, transparent); --bs-navbar-toggler-border-radius: var(--bs-radius-5); --bs-navbar-toggler-transition: box-shadow 0.15s ease-in-out; --bs-navbar-toggler-icon-size: 1.25rem; --bs-navbar-toggler-icon: #{escape-svg( url(&quot;data:image/svg+xml,&lt;svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'>&lt;path stroke='black' stroke-linecap='round' stroke-width='1' d='M1 3.5h14M1 8h14M1 12.5h14'/>&lt;/svg>&quot;) )}; } .navbar { --bs-navbar-color: color-mix(in oklch, var(--bs-white) 55%, transparent); --bs-navbar-hover-color: color-mix(in oklch, var(--bs-white) 75%, transparent); --bs-navbar-disabled-color: color-mix(in oklch, var(--bs-white) 25%, transparent); --bs-navbar-active-color: var(--bs-white); --bs-navbar-brand-color: var(--bs-white); --bs-navbar-brand-hover-color: var(--bs-white); --bs-navbar-toggler-border-color: color-mix(in oklch, var(--bs-white) 10%, transparent); } .navbar { --bs-nav-gap: 0.25rem; --bs-nav-link-gap: 0.5rem; --bs-nav-link-padding-x: 0.5rem; --bs-nav-link-padding-y: 0.375rem; --bs-nav-link-color: var(--bs-navbar-color); --bs-nav-link-border-width: var(--bs-border-width); --bs-nav-link-hover-color: var(--bs-navbar-hover-color); --bs-nav-link-hover-bg: transparent; --bs-nav-link-active-color: var(--bs-navbar-active-color); --bs-nav-link-active-bg: transparent; --bs-nav-link-disabled-color: var(--bs-navbar-disabled-color); }</description></item><item><title>Nav overflow</title><link>https://idea-react.pages.dev/components/nav-overflow/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/nav-overflow/</guid><description>Nav overflow Automatically collapse navigation items into a &quot;More&quot; menu when space is limited using the Priority+ pattern. How it works The nav overflow component (also known as the &quot;Priority+&quot; pattern) automatically detects when navigation items don’t fit within their container and moves them into a menu. This provides a responsive navigation experience without requiring different markup for different screen sizes. Here’s what you need to know before getting started: Place NavLink and Menu children inside NavOverflow , and give the wrapper a unique id . Responds to container size , not viewport size. The component watches the wrapper with a ResizeObserver, so it works in embedded contexts, documentation examples, and responsive containers. The wrapper is what makes this reliable. Collapsing items changes the width of the nav, so the component measures the wrapper instead. Measuring the nav would feed the result back in as the input. Overflow items are represented in a &quot;More&quot; menu while the originals are hidden. A nav item that hosts a menu becomes a submenu of the overflow menu. Works with all nav styles: default, pills, tabs, and underline. Active and disabled states are preserved in the overflow menu. The animation effect depends on the prefers-reduced-motion media query. See the reduced motion accessibility guidance . Examples Wrap the links in &lt;NavOverflow id=&quot;…&quot;> . When items don’t fit, they’ll automatically move to a &quot;More&quot; menu. Resize the browser to see how nav items automatically move to the &quot;More&quot; menu as space becomes limited. With tabs The overflow pattern works seamlessly with tabbed navigation: With underline Keep items visible Pass className=&quot;nav-overflow-keep&quot; to any item that should never be moved to the overflow menu. These items remain visible regardless of available space—useful for high-priority items like &quot;Home&quot; or action buttons. With disabled items Disabled states are preserved when items move to the overflow menu: In a navbar The nav overflow pattern can also be used within a navbar for horizontal navigation that adapts to available space: With menus A nav item that already hosts a menu becomes a submenu of the overflow menu. Its nested submenus stay intact. Customizing the toggle Custom text Use the moreText option to customize the text shown in the overflow toggle button: &lt;NavOverflow id=&quot;custom-text&quot; moreText=&quot;See all&quot;> &lt;NavLink href=&quot;#first&quot;>First&lt;/NavLink> &lt;NavLink href=&quot;#second&quot;>Second&lt;/NavLink> &lt;/NavOverflow> Custom icon Provide a custom icon via the moreIcon prop, using the Icon component: &lt;NavOverflow id=&quot;custom-icon&quot; moreIcon={&lt;Icon name=&quot;three-dots&quot; />} moreText={false}> &lt;NavLink href=&quot;#first&quot;>First&lt;/NavLink> &lt;NavLink href=&quot;#second&quot;>Second&lt;/NavLink> &lt;/NavOverflow> Set moreText to false for an icon-only toggle. The component labels the button aria-label=&quot;More&quot; so it still has an accessible name. An empty string does the same. React nodes are passed directly through moreIcon ; HTML strings and data-bs-overflow-icon extraction are not used. Icon placement Use the iconPlacement option to position the icon before ( 'start' , the default) or after ( 'end' ) the text: &lt;NavOverflow id=&quot;icon-placement&quot; moreText=&quot;Menu&quot; iconPlacement=&quot;end&quot;> &lt;NavLink href=&quot;#first&quot;>First&lt;/NavLink> &lt;NavLink href=&quot;#second&quot;>Second&lt;/NavLink> &lt;/NavOverflow> Minimum visible items Use the threshold option to ensure a minimum number of items remain visible before the overflow kicks in: &lt;NavOverflow id=&quot;minimum-visible&quot; threshold={3}> &lt;NavLink href=&quot;#first&quot;>First&lt;/NavLink> &lt;NavLink href=&quot;#second&quot;>Second&lt;/NavLink> &lt;NavLink href=&quot;#third&quot;>Third&lt;/NavLink> &lt;NavLink href=&quot;#fourth&quot;>Fourth&lt;/NavLink> &lt;/NavOverflow> Collapse all Use the collapseBelow option to force all items into the overflow dropdown when the wrapper’s width is below a threshold. Pass a breakpoint name to resolve the value from --bs-breakpoint-{name} , or a number for a direct pixel value. &lt;NavOverflow id=&quot;collapse-at-breakpoint&quot; variant=&quot;pills&quot; collapseBelow=&quot;md&quot;> &lt;NavLink href=&quot;#&quot;>{'Link 1'}&lt;/NavLink> &lt;NavLink href=&quot;#&quot;>{'Link 2'}&lt;/NavLink> &lt;NavLink href=&quot;#&quot;>{'Link 3'}&lt;/NavLink> &lt;/NavOverflow> Or use a raw pixel value: &lt;NavOverflow id=&quot;collapse-at-width&quot; collapseBelow={768}> &lt;NavLink href=&quot;#first&quot;>First&lt;/NavLink> &lt;NavLink href=&quot;#second&quot;>Second&lt;/NavLink> &lt;/NavOverflow> Above the threshold, normal progressive collapse resumes. Items with nav-overflow-keep in their className are never collapsed. Usage Options Pass options as React props. The component initializes on mount, updates on resize, and disposes its observers on unmount. Name Type Default Description collapseBelow number or string 0 Wrapper width below which all items collapse. Pass a breakpoint name or a pixel value; 0 disables this behavior. iconPlacement 'start' or 'end' 'start' Position of the icon relative to the toggle text. menuPlacement string 'bottom-end' Placement of the overflow menu. menuStrategy 'absolute' or 'fixed' 'absolute' Use 'fixed' when an overflow ancestor would clip the menu. moreText string or false 'More' Toggle label; false or an empty string produces an icon-only toggle. moreIcon ReactNode Chevron icon Custom toggle icon. threshold number 0 Minimum number of items to keep visible before showing overflow. minimumVisibleItems number threshold Explicit alias that takes precedence over threshold . Methods The instance method updateOverflow() manually recalculates overflow. Resizing and prop changes already trigger it automatically. Events Use onOverflowChange(overflowCount, visibleCount) to observe overflow calculations.</description></item><item><title>Nav</title><link>https://idea-react.pages.dev/components/nav/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/nav/</guid><description>Nav Add lists of links to your pages with various navigation components—tabs, pills, underline—and plenty of options to customize. Base nav Nav provides a semantic navigation container with NavLink children. Use the active and disabled props on links, and set variant to switch between visual styles. The base Nav component uses flexbox and provides a foundation for navigation. It includes link padding for larger hit areas and disabled styling. To convey the active state to assistive technologies, use the aria-current attribute — using the page value for current page, or true for the current item in a set. Nav renders a semantic &lt;nav> element with direct NavLink children. Its flex layout lets the links work without extra list markup. When a navigation item performs an action instead of navigating, set as=&quot;button&quot; on NavLink . You can mix these with links, for example when adding a menu. Tab JavaScript plugin Use Tabs and Tab to create tabbable regions. Available styles Set the variant prop on Nav to choose a style. Mix and match with layout utilities through className as needed. Tabs Set variant=&quot;tabs&quot; on Nav for a tabbed appearance. Pills Set variant=&quot;pills&quot; on Nav for a more themed appearance. Set vertical on a pill Nav to stack the links vertically. Underline Set variant=&quot;underline&quot; on Nav for an underline style: Alignment Change the alignment of your nav with flexbox utilities . By default, navs are horizontal and left-aligned, but you can easily modify them to center or right-aligned, and even stacked vertically. Horizontal Use a flexbox alignment utility through Nav 's className to center the links: Use a flexbox alignment utility through Nav 's className to align the links to the end: Vertical Set vertical on Nav to stack links. To change direction only at certain viewports, pass a responsive flexbox utility through className . Nav renders a &lt;nav> with direct NavLink children; it does not require a list wrapper. Fill and justify Set fill on Nav to make its links occupy the full available width proportionally. Notice that all horizontal space is occupied, but not every link has the same width. NavLink components can be direct children of Nav ; no NavItem wrapper is required. Set justified on Nav to make its links equal width while filling the available space. Use Nav with fill for proportional widths, or justified for equal widths. Working with flex utilities If you need responsive nav variations, consider using a series of flexbox utilities . While more verbose, these utilities offer greater customization across responsive breakpoints. In the example below, our nav will be stacked on the lowest breakpoint, then adapt to a horizontal layout that fills the available width starting from the small breakpoint. Regarding accessibility Nav renders a &lt;nav> landmark by default. When rendering it as another element with as , provide an appropriate navigation landmark; do not assign the landmark role to a list. Nav with variant=&quot;tabs&quot; is still navigation and should not be given tab roles. Use Tabs for a dynamic tabbed interface, as described in the ARIA Authoring Practices Guide tabs pattern . Tabs manages the selected state and required ARIA attributes. Using menus Add menus with the Menu component . Tabs with menus Pills with menus CSS Variables Use CSS custom properties on the component to customize its appearance without recompiling Bootstrap. On the .nav base class: .nav { --bs-nav-gap: 0.125rem; --bs-nav-link-gap: 0.5rem; --bs-nav-link-align: center; --bs-nav-link-justify: center; --bs-nav-link-padding-x: 0.75rem; --bs-nav-link-padding-y: 0.375rem; --bs-nav-link-color: var(--bs-fg-2); --bs-nav-link-hover-color: var(--bs-fg-1); --bs-nav-link-hover-bg: var(--bs-bg-1); --bs-nav-link-active-color: var(--bs-fg-body); --bs-nav-link-active-bg: var(--bs-bg-2); --bs-nav-link-disabled-color: var(--bs-fg-4); --bs-nav-link-border-width: var(--bs-border-width); --bs-nav-link-transition-property: 'color, background-color, border-color'; --bs-nav-link-transition-duration: 0.15s; --bs-nav-link-transition-timing: ease-in-out; } When variant=&quot;tabs&quot; is set: .nav { --bs-nav-tabs-border-width: var(--bs-border-width); --bs-nav-tabs-border-color: var(--bs-border-color); --bs-nav-tabs-border-radius: var(--bs-radius-5); --bs-nav-tabs-link-hover-border-color: var(--bs-border-subtle); --bs-nav-tabs-link-active-color: var(--bs-fg-body); --bs-nav-tabs-link-active-bg: var(--bs-bg-body); --bs-nav-tabs-link-active-border-color: var(--bs-border-color) var(--bs-border-color) var(--bs-bg-body); } When variant=&quot;pills&quot; is set: .nav { --bs-nav-pills-bg: var(--bs-bg-1); --bs-nav-pills-padding: 0.25rem; --bs-nav-pills-border-radius: 3rem; --bs-nav-pills-link-active-color: var(--bs-primary-contrast); --bs-nav-pills-link-active-bg: var(--bs-primary-bg); --bs-nav-pills-link-border-radius: 3rem; } When variant=&quot;underline&quot; is set: .nav { --bs-nav-gap: 1rem; --bs-nav-link-active-bg: transparent; --bs-nav-underline-border-width: 0.125rem; --bs-nav-underline-link-active-color: var(--bs-fg-body); }</description></item><item><title>Menu</title><link>https://idea-react.pages.dev/components/menu/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/menu/</guid><description>Menu Toggle contextual menus and custom overlays for lists of buttons, links, forms, and other custom content. Overview Toggle menus with buttons whenever possible. Here’s an example using an Idea React button: Action Another action Something else here Menus are toggleable, contextual overlays for displaying lists of links and more. They’re made interactive by the Menu wrapper. Positioning updates when the viewport or trigger geometry changes. They’re toggled by clicking, not by hovering; this is an intentional design decision . Examples Menu uses its button-based toggle. Unlike an upstream anchor example, the wrapper does not expose an alternate link toggle. Use button groups to create split button menus where the menu is displayed when a secondary button is clicked. Action Another action Something else here Split Action Another action Something else here Separated link Dark menus Opt into darker menus to match a dark navbar or custom style by passing theme=&quot;dark&quot; to Menu , or adding data-bs-theme=&quot;dark&quot; to a parent. Action Another action Something else here Separated link And putting it to use in a navbar: Navbar Action Another action Something else here Translucent menus Blur and saturate the background of menus to create a translucent effect with translucent . Active menu item Action Another action Something else here Danger menu item Placement Use placement on Menu to control where the menu appears. Physical placements: top-start , top-end , bottom-start , bottom-end , left-start , left-end , right-start , right-end — fixed directions regardless of text direction. Edge alignment: the -start and -end suffixes select an edge of the trigger. The wrapper does not expose upstream logical start / end side placements or automatically mirror placement in RTL. Use both a physical direction and an alignment, such as bottom-start or right-end . Action Another action Something else here Action Another action Something else here Action Another action Something else here Action Another action Something else here Action Another action Something else here Action Another action Something else here Action Another action Something else here Action Another action Something else here Responsive Change placement at different breakpoints using responsivePlacement={{ md: 'right', lg: 'bottom' }} , where each breakpoint is one of sm , md , lg , xl , or 2xl . Multiple breakpoints can be combined in the responsivePlacement object. For example, placement=&quot;bottom-start&quot; responsivePlacement={{ md: &quot;bottom-end&quot;, lg: &quot;right-start&quot; }} will: Show the menu at bottom-start on small screens (default) Switch to bottom-end at the md breakpoint Switch to right-start at the lg breakpoint Action Another action Something else here Action Another action Something else here Resize your browser window to see the placement change at different breakpoints. Menu items Use MenuItem for each entry. It renders a link when href is provided; set as=&quot;button&quot; for an action. We use utility classes to display menus in our docs examples, but they’re not required for your own use. Action Another action Something else here You can also create non-interactive menu items with MenuText . Feel free to style further with custom CSS or text utilities. Menu item text Action Another action Something else here Active Pass active to MenuItem to style them as the active selection. To convey the active state to assistive technologies, use the aria-current attribute — using the page value for the current page, or true for the current item in a set. Regular link Active link Another link Disabled Pass disabled to MenuItem to style them as disabled. Regular link Disabled link Another link Variants You can use the theme prop to apply a theme color to a menu item. Primary action Success action Delete Icons Use MenuItemIcon to add an icon slot to menu items. It renders the shared Icon component. Edit Duplicate Delete Descriptions Use MenuItemContent for a flex column layout and MenuItemDescription for secondary text below the main label. Profile View your profile and settings Settings Manage your preferences Selected Pass selected to MenuItem to indicate the current selection. Selected option Another option Something else Menu content Headers Add a header to label sections of actions in any menu. Menu header Action Another action Something else here Dividers Separate groups of related menu items with a divider. Action Another action Something else here Separated link Text Place any freeform text within a menu with text and use margin and padding utilities. Note that you’ll likely need additional sizing styles to constrain the menu width. Some example text that’s free-flowing within the menu. And this is more example text. Forms Put a form within a menu, or make it into a menu, and use margin and padding utilities to give it the negative space you require. Email address Password Remember me Sign in New around here? Sign up Forgot password? Scrollable menus Assign --bs-menu-max-height and --bs-menu-overflow-y custom properties to constrain the menu height and enable scrolling. Item 1 Item 2 Item 3 Item 4 Item 5 Item 6 Item 7 Item 8 Item 9 Item 10 Item 11 Item 12 Item 13 Item 14 Item 15 Item 16 Item 17 Item 18 Item 19 Item 20 You can also pass scrollable to make the menu scrollable. This assumes a generally safe maximum height of 80dvh and sets the overflow for you. Submenus Create nested menus with MenuSubmenu . Submenus support hover and click activation, keyboard navigation, and viewport-aware positioning. Submenus currently fly out to the side; the upstream small-screen stacked layout and back button are not exposed by the React wrapper. Pass a label and nested menu items to MenuSubmenu ; it renders and wires the trigger and panel. Action Another action Something else here Submenu action Another action Something else Nested Submenus can be nested to multiple levels. Each level opens to the side and flips direction when there’s not enough viewport space. Action Submenu action Deep action Another deep action Menu options Use offset to change the location of the menu. A number sets the distance from the trigger in pixels; [crossAxis, mainAxis] sets both axes. padding sets the viewport inset and flip={false} disables collision flipping. The trigger remains the positioning reference. Action Another action Something else here Action Another action Something else here Auto close behavior By default, the menu is closed when clicking inside or outside the menu. You can use the autoClose option to change this behavior of the menu. Regardless of the autoClose setting, pressing Esc while focus is within the menu (its toggle or items) closes the menu and returns focus to the toggle. Action Another action Something else here Action Another action Something else here Action Another action Something else here Action Another action Something else here Accessibility The WAI ARIA standard defines an actual role=&quot;menu&quot; widget , but this is specific to application-like menus which trigger actions or functions. ARIA menus can only contain menu items, checkbox menu items, radio button menu items, radio button groups, and sub-menus. Idea React’s menus, on the other hand, are designed to be generic and applicable to a variety of situations and markup structures. For instance, it is possible to create menus that contain additional inputs and form controls, such as search fields or login forms. For this reason, Idea React does not expect (nor automatically add) any of the role and aria- attributes required for true ARIA menus. Authors will have to include these more specific attributes themselves. Submenu triggers are an exception. MenuSubmenu adds aria-haspopup=&quot;true&quot; to its trigger, and keeps aria-expanded on it in sync as the submenu opens and closes. The wrapper keeps this state in sync automatically. Keyboard navigation Menus include built-in keyboard support for navigating menu items. Submenu arrow keys remain physical directions in both LTR and RTL; the wrapper does not implement upstream RTL key reversal. Key Action ↓ / ↑ Navigate to next/previous menu item → Enter submenu ← Exit submenu and return to parent Enter / Space Activate focused item or open submenu Esc Close the menu Home / End Jump to first/last menu item Tab Move focus and close the menu CSS Variables Local CSS custom properties expose the component’s colors, spacing, borders, and transitions. Override them through style or a CSS module. The defaults below come from the Bootstrap stylesheet used by Idea React; see the upstream variable reference . Variable Default --bs-menu-max-height 300px --bs-menu-overflow-y auto Usage Menu manages its own open state, trigger wiring, positioning, and cleanup. Do not initialize Bootstrap’s plugin on the same elements. Options Prop Default Description autoClose true Close on inside/outside clicks, only &quot;inside&quot; , only &quot;outside&quot; , or neither ( false ). Escape still dismisses the menu. placement &quot;bottom-end&quot; Preferred side and edge alignment; align defaults to &quot;end&quot; . responsivePlacement — Override placement at named breakpoints. offset 0 Distance from the toggle, or a [crossAxis, mainAxis] pair. padding 8 Inset from the viewport edge when shifting to avoid overflow. flip true Flip to another side when the preferred side lacks space. Events onOpenChange(open) receives the menu’s new visibility state.</description></item><item><title>List group</title><link>https://idea-react.pages.dev/components/list-group/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/list-group/</guid><description>List group List groups are a flexible and powerful component for displaying a series of content. Modify and extend them to support just about any content within. Basic example The most basic list group combines ListGroup with ListGroupItem children. Build upon it with the props that follow, or with your own CSS as needed. Active items Set active on ListGroupItem to indicate the current selection. Links and buttons Set action on ListGroupItem to create an interactive item with hover, disabled, and active states. Non-interactive items do not display a click or tap affordance. Set disabled on ListGroupItem to disable interaction and communicate the disabled state to assistive technologies. Do not use Button styles for list group items. For button items, ListGroupItem passes disabled to the native button. Link items do not support the native disabled attribute, so the wrapper disables navigation and keyboard focus. Flush Set flush on ListGroup to remove some borders and rounded corners so its items sit edge-to-edge in a parent container such as a card. Numbered Set numbered on ListGroup to number its items; use as=&quot;ol&quot; when an ordered-list element is also appropriate. Numbers are generated with CSS for better placement and customization. The numbered prop uses CSS counters to generate and place the item numbers. These work great with custom content as well. Horizontal Set horizontal on ListGroup to display items in a row at all sizes, or set it to a breakpoint such as sm or md to switch to a row at that breakpoint. The responsive variants use container queries , so place the list group in a query container with the contains-inline utility applied through the parent's className . Currently horizontal list groups cannot be combined with flush list groups. ProTip: For equal-width horizontal items, apply the flex-fill utility through each ListGroupItem 's className . Drag the handle to resize the container below and watch the list group switch between vertical and horizontal layouts as the container—not the viewport—crosses the md breakpoint. Variants Set the theme prop on ListGroupItem to give an item a contextual background and color. For links and buttons Theme colors also work with interactive ListGroupItem components. Notice the hover styles not present in the previous example. Set active to indicate the selected item. Using color to add meaning only provides a visual indication. Include text or a visually hidden label so assistive technologies can convey the same information. With badges Add badges to any list group item to show unread counts, activity, and more with the help of some utilities . Custom content Add nearly any HTML within, even for linked list groups like the one below, with the help of flexbox utilities . Checkboxes and radios Place Checkbox and Radio components inside list group items and customize them as needed. If there is no visible label, provide an aria-label . Apply the stretched-link utility through the item's className when the entire item should be clickable. Use the checkable and radio props for the corresponding list group variants. Add listGroup to FormCheck to apply the input styling used by checkable groups. CSS Variables Use CSS custom properties on the component to customize its appearance without recompiling Bootstrap. .list-group { --bs-list-group-color: var(--bs-fg-body); --bs-list-group-bg: var(--bs-bg-body); --bs-list-group-border-color: var(--bs-border-color); --bs-list-group-border-width: var(--bs-border-width); --bs-list-group-border-radius: var(--bs-radius-5); --bs-list-group-item-padding-x: var(--bs-spacer); --bs-list-group-item-padding-y: var(--bs-spacer-2); --bs-list-group-action-color: var(--bs-fg-2); --bs-list-group-action-hover-color: var(--bs-fg-1); --bs-list-group-action-hover-bg: var(--bs-bg-1); --bs-list-group-action-active-color: var(--bs-fg-body); --bs-list-group-action-active-bg: var(--bs-bg-2); --bs-list-group-disabled-color: var(--bs-fg-3); --bs-list-group-disabled-bg: var(--bs-bg-body); --bs-list-group-active-color: var(--bs-primary-contrast); --bs-list-group-active-bg: var(--bs-primary-bg); --bs-list-group-active-border-color: var(--bs-primary-bg); } JavaScript behavior Use the Tab plugin to create tabbable list group panes.</description></item><item><title>Drawer</title><link>https://idea-react.pages.dev/components/drawer/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/drawer/</guid><description>Drawer Build hidden sidebars or drawers into your project for navigation, shopping carts, and more with React props and the native dialog API. Replaces the old Offcanvas component. How it works Drawer builds on the native &lt;dialog> element and our Dialog component to manage hidden sidebars via JavaScript. These sidebars, or drawers, can appear from the left, right, top, or bottom edge of the viewport. Buttons or anchors are used as triggers that are attached to specific elements you toggle, and React state controls the open prop. Drawer shares the same base as our Dialog component , using native &lt;dialog> APIs for focus trapping, backdrop, and top-layer rendering. Use the &lt;dialog> element , not a &lt;div> . The wrapper renders this element. Due to how CSS handles animations, don’t apply margin or translate directly to Drawer — wrap it if you need those. Modal by default — opens with showModal() , a backdrop, and focus trapping. Set scroll: true and backdrop: false to open as a non-modal drawer with show() : body scrolling stays on, and focus is not trapped. Built-in backdrop via ::backdrop (modal only) closes the drawer on click; set backdrop: &quot;static&quot; to lock clicks outside, or backdrop: false to hide it. Escape key handling closes the drawer by default; set keyboard: false to disable. Dismissal — the close button, Escape, and backdrop click close the drawer. The React wrapper does not currently implement the upstream swipe-to-dismiss gesture. Responsive placement — responsive=&quot;sm&quot; , responsive=&quot;md&quot; , and up stay drawer-like below their breakpoint and collapse inline above it, making drawers useful as responsive navbars. Coordinate open drawers through application state if only one should be shown at a time; the React wrapper does not use Bootstrap’s data API. Animated open and close — drawer slides back out to its placement-specific off-screen position on close, with the ::backdrop fading alongside it when opened modally. When authoring custom CSS, qualify your [open] rules with :not(.hiding) so the exit transition can fall through to the base state; pass animation=&quot;instant&quot; to skip animations. The animation effect of this component is dependent on the prefers-reduced-motion media query. Examples Drawer components Below is a drawer example that is shown by default (via open and modal={false} ). Drawer includes support for a header with a close button and an optional body class for some initial padding . We suggest that you include drawer headers with dismiss actions whenever possible, or provide an explicit dismiss action. Content for the drawer goes here. You can place just about any Bootstrap component or custom elements here. Live demo Use the buttons below to show and hide a drawer element via React state. Both a link and a button can invoke the same action, updating open . Use onDismiss to synchronize state after the close button, backdrop, or Escape is used. Without JavaScript Supported browsers can open and close a drawer with the Invoker Commands API —no Bootstrap JavaScript required. Set commandFor to the drawer’s id , use command=&quot;show-modal&quot; to open, and command=&quot;close&quot; to dismiss. The Invoker Commands API is not supported in all browsers. For guaranteed support, use React-controlled open and onDismiss , as in the examples above, when you need wrapper options, callbacks, or animated close. Open drawer This drawer opens with command=&quot;show-modal&quot; . Close drawer Body scrolling Scrolling the &lt;body> element is disabled when a drawer opens modally. Pass scroll with backdrop={false} to keep body scrolling and open the drawer as non-modal. Focus moves into the drawer, but is not trapped, so the page stays interactive. Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Body scrolling &amp; backdrop You can also allow &lt;body> scrolling while keeping a backdrop. With a backdrop present, the drawer stays modal ( showModal() and focus trapping) even when scroll is true . Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Static backdrop When backdrop is set to static, the drawer will not close when clicking outside of it. I will not close if you click outside of me. Instant drawer By default, drawers animate with a slide on open and close. To disable animations, pass animation=&quot;instant&quot; to Drawer . Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Dark drawer Change the appearance of drawers with utilities to better match them to different contexts like dark navbars. Here we pass theme=&quot;dark&quot; to Drawer , and it makes all nested elements within use dark mode. Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Translucent drawer Pass translucent to the drawer panel to blur and saturate the background. This makes the panel semi-transparent so content behind it shows through. Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Sheet Pass sheet to render the panel flush against the viewport edge. The sheet variant removes the drawer’s inset, border, border-radius, and box-shadow, so it sits edge-to-edge like a traditional offcanvas. It works with any placement. Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Responsive Responsive drawers hide content outside the viewport from a specified breakpoint and down. Above that breakpoint, the contents within will behave as usual. For example, responsive=&quot;lg&quot; hides content in a drawer below the lg breakpoint, but shows the content above the lg breakpoint. Responsive drawers are available for each breakpoint. To make a responsive drawer, set the responsive breakpoint prop. The wrapper wires its close button without an explicit target. This drawer becomes inline content above the lg breakpoint. Resize the browser to see the change. Placement Choose a placement for the drawer. Idea React defaults to &quot;end&quot; . placement=&quot;start&quot; places drawer on the left of the viewport (shown above) placement=&quot;end&quot; places drawer on the right of the viewport placement=&quot;top&quot; places drawer on the top of the viewport placement=&quot;bottom&quot; places drawer on the bottom of the viewport fullscreen covers the entire viewport Try the top, right, bottom, and fullscreen examples out below. Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Footer Pass optional footer content for action buttons or other content at the bottom of the drawer. Some text as placeholder. In real life you can have the elements you have chosen. Like text, images, lists, etc. Accessibility Since the drawer is a native &lt;dialog> , it gets the correct dialog role. Modal drawers also get modal semantics and focus trapping from showModal() . Non-modal drawers ( scroll: true and backdrop: false ) use show() instead, so they do not trap focus or mark the rest of the page as inert. The wrapper supplies aria-label for a string title . When supplying custom title markup, provide an accessible aria-label or aria-labelledby . CSS Variables Local CSS custom properties expose the component’s colors, spacing, borders, and transitions. Override them through style or a CSS module. The defaults below come from the Bootstrap stylesheet used by Idea React; see the upstream variable reference . Variable Default Usage Control open with React state and keep it synchronized through onDismiss . Native dialog behavior is supplied by Dialog . Options Prop Default Description placement &quot;end&quot; Position the panel at start , end , top , or bottom . backdrop true Close on an outside click; &quot;static&quot; prevents outside dismissal, and false hides the backdrop. keyboard true Close when Escape is pressed. scroll false Allow body scrolling; combine with backdrop={false} for a non-modal drawer. animation &quot;slide&quot; Choose the sliding transition or &quot;instant&quot; . responsive — Display inline above the selected breakpoint. Events onDismiss() runs when the drawer is dismissed by its close button, Escape, or a backdrop click. Use it to update the controlled open value.</description></item><item><title>Dialog</title><link>https://idea-react.pages.dev/components/dialog/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/dialog/</guid><description>Dialog A modern component built on the native &lt;dialog> element with built-in accessibility and backdrop support that replaces the old Modal component. How it works The Dialog component leverages the browser’s native &lt;dialog> element, providing built-in accessibility features, focus management, and backdrop handling without the complexity of custom implementations. Key features of the native dialog: Modal or inline via showModal() / show() — modal: true (default) promotes the dialog to the browser’s top layer with a backdrop and focus trapping; modal: false renders it inline. Built-in backdrop using the ::backdrop pseudo-element (modal only); set backdrop: &quot;static&quot; to lock clicks outside, or backdrop: false to hide it. Escape key handling closes the dialog by default; set keyboard: false to disable. Accessibility — focus is trapped inside modal dialogs and returned to the trigger on close, with native &lt;dialog> ARIA semantics. Animated open and close — circumvent browser restrictions by using a .hiding class to keep dialogs in the top layer during close so the exit transition (including ::backdrop ) are animated properly. The animation effect of this component is dependent on the prefers-reduced-motion media query. Example Toggle a dialog by clicking the button below. The dialog uses the native showModal() API for true modal behavior. This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. Without JavaScript Supported browsers can open and close a dialog with the Invoker Commands API —no Bootstrap JavaScript required. Set commandFor to the dialog’s id , use command=&quot;show-modal&quot; to open, and command=&quot;close&quot; to dismiss. The Invoker Commands API is not supported in all browsers. For guaranteed support, use React-controlled open and onClose , as in the examples above, when you need wrapper options, events, or animated close. Open dialog Invoker Commands This dialog opens with command=&quot;show-modal&quot; and closes with command=&quot;close&quot; . No Bootstrap JavaScript is involved. Close Dark dialog To make a dialog dark, pass theme=&quot;dark&quot; to Dialog . This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. Static backdrop When backdrop is set to static , the dialog will not close when clicking outside of it. Click the button below to try it. I will not close if you click outside of me. Use the close button or press Escape. Overlays Tooltips, popovers, and toasts all work inside dialogs, but require some extra care. Since dialogs render in the browser’s top layer, overlays appended to &lt;body> will appear behind the dialog. Keep OverlayBox inside the dialog, or set its container to the dialog element, so tooltips and popovers render inside it. Toasts already work as long as they’re placed in the dialog markup. Tooltips, popovers, toasts, and menus all work inside modal dialogs. Modal dialogs use showModal() , which promotes the dialog to the browser’s top layer -- a special rendering layer above everything else on the page. Animations Instant By default, dialogs animate with a fade on open and close. To disable animations, pass animation=&quot;instant&quot; to Dialog . This dialog doesn’t animate and appears instantly on open and close. Slide down Pass animation=&quot;slide-down&quot; to Dialog and it will slide down from the top of the viewport when opened. This dialog slides down from the top of the viewport. Slide up Pass animation=&quot;slide-up&quot; to Dialog and it will slide up from the bottom of the viewport when opened. This dialog slides up from the bottom of the viewport. Scrollable Create a scrollable dialog that scrolls the dialog body while keeping the header and footer fixed. Pass scrollable to Dialog . This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. This is some placeholder content to show the scrolling behavior for dialogs. We use repeated paragraphs to demonstrate how content can exceed the dialog’s inner height, showing scrolling within the body while the header and footer remain fixed. Swapping dialogs When a toggle trigger is inside an open dialog, clicking it will swap dialogs—opening the new one before closing the current. This ensures the backdrop stays visible throughout the transition with no flash. The React demo coordinates the two open props rather than using data-attribute triggers. Non-modal dialogs By default, dialogs open as modals using the browser-native showModal() method. You can also open dialogs as non-modal using show() by setting modal to false . Non-modal dialogs: Have no backdrop Don’t trap focus Don’t block interaction with the rest of the page Don’t render in the browser’s top layer Still respond to Escape key (if keyboard: true ) This dialog doesn’t block interaction with the rest of the page. Use modal={false} to create a non-modal Dialog . Optional sizes Dialogs have three optional sizes, available via the size prop on Dialog . These sizes kick in at certain breakpoints to avoid horizontal scrollbars on narrower viewports. Size Prop Dialog max-width Small size=&quot;sm&quot; 280px Default — 500px Large size=&quot;lg&quot; 800px Extra large size=&quot;xl&quot; 1140px This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. Fullscreen dialog Pass fullscreen to make the dialog cover the entire viewport. This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. Responsive fullscreen variants are also available. These make the dialog fullscreen only below a specific breakpoint. Prop Fullscreen below fullscreen Always fullscreen=&quot;sm&quot; 576px fullscreen=&quot;md&quot; 768px fullscreen=&quot;lg&quot; 1024px fullscreen=&quot;xl&quot; 1280px fullscreen=&quot;2xl&quot; 1536px This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. This is a native dialog element. It uses the browser’s built-in modal behavior for accessibility and focus management. CSS Variables Local CSS custom properties expose the component’s colors, spacing, borders, and transitions. Override them through style or a CSS module. The defaults below come from the Bootstrap stylesheet used by Idea React; see the upstream variable reference . Variable Default --bs-dialog-padding 1rem --bs-dialog-width 500px --bs-dialog-margin 1.75rem --bs-dialog-color var(--bs-fg-body) --bs-dialog-bg var(--bs-bg-body) --bs-dialog-border-color var(--bs-border-color-translucent) --bs-dialog-border-width var(--bs-border-width) --bs-dialog-border-radius var(--bs-radius-7) --bs-dialog-box-shadow var(--bs-box-shadow-xl) --bs-dialog-transition-property opacity, transform, visibility --bs-dialog-transition-duration 0.3s --bs-dialog-transition-timing var(--bs-transition-timing-overlay) --bs-dialog-backdrop-bg light-dark(rgba(0, 0, 0, 0.5), rgba(0, 0, 0, 0.65)) --bs-dialog-backdrop-blur 8px --bs-dialog-header-padding 1rem --bs-dialog-header-border-color var(--bs-border-color-translucent) --bs-dialog-header-border-width var(--bs-border-width) --bs-dialog-footer-padding 1rem --bs-dialog-footer-border-color var(--bs-border-color-translucent) --bs-dialog-footer-border-width var(--bs-border-width) --bs-dialog-footer-gap 0.5rem JavaScript behavior Control Dialog with open ; update application state from onClose . The wrapper handles the browser’s native dialog methods and focus restoration. Options Prop Default Description modal true Open with a backdrop, focus trapping, and top-layer rendering. backdrop true Close on an outside click; &quot;static&quot; keeps the backdrop without outside dismissal, and false hides it. keyboard true Close when Escape is pressed. scroll false Allow the document body to scroll. animation &quot;fade&quot; Choose fade , instant , slide-down , or slide-up . Events Native onCancel and onClose callbacks are forwarded. onClose runs when the native dialog closes, including after an animated close.</description></item><item><title>Collapse</title><link>https://idea-react.pages.dev/components/collapse/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/collapse/</guid><description>Collapse Toggle content visibility by pairing Collapse with a connected CollapseToggle . How it works Collapse shows and hides content using its open or defaultOpen prop. Pair it with CollapseToggle and set both components' target props to connect the trigger and content. CSS animates the size from zero to the content size; because of how the transition works, put padding on a child rather than directly on the Collapse component. The animation needs interpolate-size . Browsers without it open and close the element at once. See Transitions to change the timing or to remove it. The animation effect depends on the prefers-reduced-motion media query. See the reduced motion accessibility guidance . Example Click the buttons below to show and hide another element via class changes: Collapse hides content when closed and reveals it when open is true Generally, we recommend a button trigger: use CollapseToggle with a target selector. While not recommended from a semantic point of view, passing href also renders an anchor trigger. The component manages the collapse behavior and accessibility attributes. Horizontal The component also supports horizontal collapsing. Set horizontal to transition the inline size instead of the block size, and set a width on the immediate child through style or className . Please note that while the example below has a min-height set to avoid excessive repaints in our docs, this is not explicitly required. Only the width on the child element is required. Multiple toggles and targets A CollapseToggle can show and hide multiple elements by referencing them with a selector in its target prop. Conversely, multiple triggers can show and hide the same element if they each reference it with their target prop. Accessibility CollapseToggle keeps aria-expanded and aria-controls synchronized with the targeted Collapse . Use its default button element for the toggle, or set as to another element and provide the appropriate interactive semantics. CollapseToggle sets aria-controls from its target prop, which identifies the Collapse by selector. CollapseToggle does not implement the optional keyboard interactions described in the ARIA Authoring Practices Guide accordion pattern ; add those interactions when building a full accordion pattern. CSS Variables The collapse transition is controlled by CSS custom properties: .collapse { --bs-transition-collapse-property: block-size, display; --bs-transition-collapse-duration: 0.35s; --bs-transition-collapse-timing: ease; } Styling Collapse shares its transition styles with Accordion . The horizontal prop changes the animated axis to inline size; the component applies its visibility state automatically. Usage The open and defaultOpen props control visibility; CSS handles the transition. Initialization and cleanup are automatic. Options Name Type Default Description defaultOpen boolean false Initial visibility of an uncontrolled collapse. open boolean — Controlled visibility. horizontal boolean false Animate inline size rather than block size. parent string — Parent selector for accordion-like behavior: opening one collapse closes its siblings. Set parent on the collapsible area, not on its trigger. For native details-based disclosure groups, see Accordion . Events Use onOpenChange(open) to respond to visibility changes, or to update the state backing a controlled open prop.</description></item><item><title>Close button</title><link>https://idea-react.pages.dev/components/close-button/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/close-button/</guid><description>Close button A generic close button for dismissing content like modals and alerts. CloseButton supplies the close-button styles, a default type=&quot;button&quot; , and the accessible label “Close”. Pass an onClick handler when wiring it to your own dismissible content. Example Use CloseButton to dismiss or close a component. Its icon is rendered with a CSS mask and inherits its color—no inline SVG is required. Set an accessible label with aria-label so screen readers can identify the button. Disabled state Disabled close buttons change their opacity . We’ve also applied pointer-events: none and user-select: none to preventing hover and active states from triggering. Dark variant Set data-bs-theme=&quot;dark&quot; on CloseButton or one of its parent elements to invert it. This happens automatically in dark mode. CSS Variables Customize the component with the following local CSS variables. Override them through the wrapper’s style prop or your own CSS module. CSS variable Default --bs-btn-close-size 1.25rem --bs-btn-close-color inherit --bs-btn-close-icon SVG mask image --bs-btn-close-opacity 0.5 --bs-btn-close-hover-opacity 0.75 --bs-btn-close-focus-opacity 0.85 --bs-btn-close-disabled-opacity 0.25</description></item><item><title>Carousel</title><link>https://idea-react.pages.dev/components/carousel/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/carousel/</guid><description>Carousel A slider or slideshow component for cycling through series of content, ranging from products to images and more, one at a time. How it works Carousel is built on CSS’s scroll-snap , so sliding, touch dragging, momentum, and keyboard scrolling all come from the browser. The React component manages autoplay, the previous/next controls, the indicators, and active-slide syncing. Because the slides live in a real scroll container, the carousel can show more than one slide at a time , reveal a “peek” of the neighboring slides, and mix variable-width slides—all controlled with CSS. Carousels can have any number of slides, with just about any content within. Our examples show images and text, but you can put anything you like inside each CarouselSlide . We don't support nested carousels. Carousel items or slides do not normalize their dimensions. As such, you may need to use utilities through className or custom styles to size content. Previous/next controls and indicators are optional; add and customize them as needed. Carousel initializes on mount, including active-slide syncing as the user scrolls or swipes. Pass autoplay for autoplaying carousels . Do not initialize the same carousel with Bootstrap’s JavaScript plugin. The React wrapper starts on the first slide. It manages the active state that drives indicator syncing and, with fade , which slide is shown. A child’s active prop does not select the initial slide. Controls and indicators are scoped to their own carousel, so multiple instances do not need Bootstrap target attributes. The animation effect of this component is dependent on the prefers-reduced-motion media query. Slides swap immediately and the autoplay indicator countdown is disabled for users who prefer reduced motion. Examples Top controls The default carousel has a simple design that you can customize. Controls can be placed outside the inner carousel container. They can sit at the top or bottom, with additional content alongside them. Use controlsStart for content at the start of the controls row. First slide Second slide Third slide Bottom controls Similar to the controls on top, but with the controls at the bottom of the carousel and different content. First slide Second slide Third slide Indicators Pass indicators to include slide indicator buttons and use indicatorPlacement to position them within the controls row. With an overlay carousel , the row sits over the bottom of the slides; its alignment determines where the indicators appear. First slide Second slide Third slide Custom content You can put any content inside each CarouselSlide . Add content, then size and style it with utilities through className or CSS Modules as needed. Build anything Compose slides from your own markup—text, buttons, cards, or media. Get started Style it your way Use utilities or custom CSS to size and theme each slide however you need. Learn more Mix and match Combine custom content with controls, indicators, and the overlay layout. Browse examples Modifiers Change the default carousel appearance with alternate control placement and animations. Overlay controls Use controlsPlacement=&quot;overlay&quot; to overlay carousel controls on top of the slides. The component wraps its controls in the overlay row automatically. First slide Second slide Third slide Crossfade Pass fade to animate slides with a fade transition instead of a slide. Depending on your content (e.g., text-only slides), you may want to add bg-body or a CSS module to the slides for proper crossfading. The crossfade is a CSS opacity transition over --bs-carousel-fade-duration , and collapses to an instant swap for users who prefer reduced motion. First slide Second slide Third slide Items Because the carousel is a real scroll container, you can change how many slides are visible and how they’re sized with a few CSS custom properties on Carousel without writing any JavaScript. --bs-carousel-items sets the number of whole slides visible per view (default 1 ). --bs-carousel-items-gap sets the space between slides (default 0px ). --bs-carousel-items-peek sets how much of the neighboring slides to reveal (default 0px ). Multiple items Set items to show several slides at once. Combine it with itemsGap for spacing; these props set the corresponding CSS custom properties. Set items={3} to control the count, or set --bs-carousel-items through a CSS module for responsive layouts. Navigation follows distinct, reachable scroll-snap positions, not every card independently. Targets beyond the scroll range share one end position, represented by the first slide that reaches it. activeIndex and onChange identify that slide; active does not mean it is the only visible card. Controls, indicators, swipe synchronization, and autoplay use the same positions, so there are no extra steps at the end. Selecting another slide that shares the end position selects its representative instead. Positions are recalculated when the viewport or slides resize. Autoplay uses the representative slide’s interval. Peeking Set itemsPeek to reveal a sliver of the previous and next slides, hinting that there’s more to scroll. Variable width Pass auto and size each CarouselSlide yourself with className , style , or a CSS Module. Snap points still land on every slide. Pass center to snap the active slide to the center of the viewport instead of its start—pairs nicely with itemsPeek . Autoplay Set autoplay to true to cycle a carousel automatically on page load. Autoplay pauses on hover—configurable with the pause option—and while the page isn’t visible, using the Page Visibility API . As soon as a visitor takes control—clicking a control or indicator, using the keyboard, or swiping—autoplay stops, so content isn’t moved out from under them. For accessibility reasons, we recommend avoiding the use of autoplaying carousels. If your page does include one, provide a discoverable control to pause and resume it: pass playPause to add a play/pause button (shown below). This satisfies WCAG 2.2 Success Criterion 2.2.2 Pause, Stop, Hide , which a hover- or focus-only pause does not. The wrapper also includes this button automatically when autoplay is enabled. The play/pause button reflects the current state automatically—a pause icon while playing, a play icon while stopped. The wrapper supplies an accessible name for each state. While playing, the active indicator fills like a progress bar over the current slide’s interval as a visual countdown; it pauses with autoplay and is disabled under reduced motion. Set its color with the --bs-carousel-indicator-progress-bg CSS variable. First slide Second slide Third slide Individual intervals Pass interval to a CarouselSlide to change the delay between automatically cycling to the next item. The indicator’s progress fill matches each slide’s own interval, so the countdown speeds up or slows down to match (2s, then 4s, then 6s below). First: 2 seconds Second: 4 seconds Third: 6 seconds End behavior The ends prop controls what happens at the first and last slide. Choose from loop (the default), wrap , or stop . Loop (default) With ends=&quot;loop&quot; the carousel scrolls seamlessly past the ends: stepping next from the last slide (or previous from the first) continues in the same direction into the destination slide instead of jumping back, for an endless conveyor effect. This is the default, so it applies with or without the prop. Seamless looping applies to full-width single-slide carousels driven by the controls, keyboard, or autoplay. Multi-item, peek, centered, and variable-width layouts fall back to wrap : a smooth scroll back across the content, not a same-direction seamless loop. Reduced motion switches immediately instead. First slide Second slide Third slide Wrap With ends=&quot;wrap&quot; the carousel scrolls back from the last reachable position to the first, and vice versa, so the controls never reach a dead end. This scroll has intermediate positions under normal motion preferences and is immediate under reduced motion. First slide Second slide Third slide Stop With ends=&quot;stop&quot; the carousel hard-stops at the first and last slide. The previous control is automatically disabled on the first slide and the next control on the last via the native disabled attribute; when a focused control becomes disabled, focus shifts to the opposite control so it isn’t lost. First slide Second slide Third slide Dark carousel Set data-bs-theme=&quot;dark&quot; on Carousel for darker controls and indicators. This is typically most useful with overlay carousels when you need the reverse contrast against the background of the slides. First slide Second slide Third slide CSS Variables Local CSS custom properties expose spacing, colors, sizing, and transitions for all carousels. Override them through style or a CSS module. These defaults come from Bootstrap 6.0.0-alpha.1; see the variable reference for the control icon masks. Variable Default --bs-carousel-gap 0.75rem --bs-carousel-indicator-bg var(--bs-fg-3) --bs-carousel-indicator-width 0.75rem --bs-carousel-indicator-height 0.75rem --bs-carousel-indicator-spacer 0.25rem --bs-carousel-indicator-opacity-duration 0.6s --bs-carousel-indicator-opacity-timing ease --bs-carousel-indicator-width-duration 0.3s --bs-carousel-indicator-width-timing ease --bs-carousel-indicator-progress-bg var(--bs-carousel-indicator-bg) --bs-carousel-control-icon-width 1rem --bs-carousel-items 1 --bs-carousel-items-gap 0px --bs-carousel-items-peek 0px --bs-carousel-fade-duration 0.6s --bs-carousel-fade-timing ease The React controls use Icon with Bootstrap Icons rather than Bootstrap’s CSS-mask glyphs. The active countdown sets --bs-carousel-interval to the current slide’s interval in milliseconds. Usage Via props Use props to control the carousel rather than Bootstrap’s data-attribute plugin. Previous/next buttons and indicator buttons are wired automatically to their own instance. Prop Description autoplay Automatically cycle through slides on mount. interval Autoplay interval in milliseconds between slides; individual slides can override it. ends Choose stop , wrap , or loop behavior at the ends. playPause Render an accessible play/pause control. controlsPlacement Put the controls at the top, bottom, or over the slides. controlsStart Content to display at the start of the controls row. controlsClassName Bootstrap utilities or a CSS module for the non-overlay controls row. innerClassName Bootstrap utilities or a CSS module for the scroll viewport. indicatorPlacement Position indicators before, after, or between the previous/next buttons. Via React Mount the component to initialize it. Timers and scroll listeners are cleaned up on unmount. import { Carousel, CarouselSlide } from 'idea-react'; &lt;Carousel aria-label=&quot;My carousel&quot; controlsPlacement=&quot;bottom&quot; indicators> &lt;CarouselSlide>First slide&lt;/CarouselSlide> &lt;CarouselSlide>Second slide&lt;/CarouselSlide> &lt;/Carousel>; Dependencies Load Bootstrap CSS and Bootstrap Icons alongside Idea React. The component manages its own state and scrolling and does not require Bootstrap’s JavaScript plugin. Follow the installation guide . Options Prop Type Default Description autoplay boolean false Automatically cycle through slides on mount. ends string &quot;loop&quot; stop disables previous/next at the reachable ends. wrap smoothly scrolls to the opposite end. loop scrolls seamlessly for full-width single-slide carousels, falling back to wrap for multi-item, peek, centered, and variable-width layouts. Reduced motion switches immediately. interval number 5000 Delay in milliseconds between automatically cycling an item. keyboard boolean true React to left/right arrow keys outside editable controls. pause string, boolean &quot;hover&quot; Pause temporarily while the pointer or focus is inside the carousel. Pass false to disable this pause. controls boolean true Render previous and next buttons. controlsPlacement string &quot;overlay&quot; Choose top , bottom , or overlay . indicators boolean false Render slide indicators. indicatorPlacement string &quot;start&quot; Choose start , end , or between . playPause boolean false Provide an explicit autoplay control; also included automatically for autoplay . auto boolean false Let slides retain their individual widths. center boolean false Snap the active slide to the center of the viewport. fade boolean false Crossfade stacked slides instead of scrolling. The visible slide count, gap, and peek are controlled with CSS custom properties, exposed through items , itemsGap , and itemsPeek —see Items . Methods For imperative controls, attach a React ref to Carousel and use its model methods. Methods return before the scrolling or crossfade has visually completed. Scroll and crossfade modes expose the same model methods and selection/playback state. Changing fade replaces the mode model while preserving selection and playback intent, so read carousel.current.store when needed rather than caching the model across mode changes. Layout and control updates keep the existing model and do not restart an unchanged autoplay interval. import { createRef } from 'react'; import { Carousel } from 'idea-react'; const carousel = createRef&lt;Carousel>(); carousel.current?.store.play(); carousel.current?.store.pause(); carousel.current?.store.next(true); carousel.current?.store.previous(true); carousel.current?.store.setIndex(2, true); Method Description store.play() Start cycling through the carousel items. store.pause() Stop cycling through items. store.toggle() Toggle autoplay. store.next(true) Move to the next slide and stop autoplay for user-initiated navigation. store.previous(true) Move to the previous slide and stop autoplay for user-initiated navigation. store.setIndex(index, true) Select a zero-based slide index and stop autoplay for user-initiated navigation. The component disposes its model and scroll animation when unmounted; do not use Bootstrap’s getInstance , getOrCreateInstance , or dispose methods on it. Events onChange(index) receives the zero-based active slide index after navigation or scroll synchronization. It reports logical selection, not the end of the scroll or crossfade animation. Bootstrap’s slide.bs.carousel and slid.bs.carousel plugin events are not emitted by this wrapper. &lt;Carousel onChange={handleSlideChange}> &lt;CarouselSlide>First slide&lt;/CarouselSlide> &lt;CarouselSlide>Second slide&lt;/CarouselSlide> &lt;/Carousel></description></item><item><title>Cards</title><link>https://idea-react.pages.dev/components/card/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/card/</guid><description>Cards Bootstrap’s cards provide a flexible and extensible content container with multiple variants and options. The examples compose Card with its body, title, text, image, header, footer, and group wrappers. Use body , row , theme , subtle , and translucent props instead of adding component classes. Cards are flexible and extensible content containers with support for headers and footers, a wide variety of content, contextual background colors, and additional display options. Cards have no fixed width to start , so they’ll naturally fill the width of their parent element, or slot into your grid columns. 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 Cards are built with as little markup and styles as possible, but still manage to deliver a ton of control and customization. Cards are flexbox containers, so align their contents with flexbox utilities through className and arrange them with Row and Col . Card has no default padding. Add a CardBody child, or set body on Card for a simple padded card. This allows greater flexibility with the least amount of overhead. Cards have no margin by default. Use margin utilities through className or set spacing with Stack 's gap prop. Cards can contain text, images, lists, and other content components. Choose semantic elements that fit the content. Use the as prop on Card or its child components to render an appropriate element such as section or article . Content types Body The building block of a card is CardBody . Use it whenever you need a padded section within a card. This is some text within a card body. For simple cards, set the body prop directly on Card . This is some text within a card body. Titles, text, and links Card bodies arrange their direct children in a column and apply a consistent gap, so titles and text need no additional styles. Use CardTitle for a title, CardSubtitle for a subtitle, and CardText for text. CardSubtitle reduces the gap above it. Use text and color utilities through className as needed. A color utility on CardSubtitle overrides --bs-card-subtitle-color . Links need no card-specific wrapper. Example card title 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 Images Place images anywhere in a card and style as you like. Image within the body Some quick example text to build on the card title and make up the bulk of the card’s content. Last updated 3 mins ago Set placement=&quot;top&quot; or placement=&quot;bottom&quot; on CardImage to round the corresponding image corners. Some quick example text to build on the card title and make up the bulk of the card’s content. Some quick example text to build on the card title and make up the bulk of the card’s content. List groups When your card only contains a list group—with no header, footer, or body—use ListGroup on its own. A card already draws an outer border, so a default list group inside a card would double that border. An item A second item A third item When you mix a list group with other card sub-components, set the flush prop on ListGroup to remove its outer border. Featured An item A second item A third item An item A second item A third item Card footer Kitchen sink Mix and match multiple content types to create the card you need, or throw everything in there. Shown below are image styles, blocks, text styles, and a list group—all wrapped in a fixed-width card. Card title Some quick example text to build on the card title and make up the bulk of the card’s content. An item A second item A third item Card link Another link Header and footer Add an optional header and/or footer within a card. Featured Special title treatment With supporting text below as a natural lead-in to additional content. Go somewhere Use CardHeader for a card header; set its as prop when the heading needs a specific semantic element. Featured Special title treatment With supporting text below as a natural lead-in to additional content. Go somewhere Quote A well-known quote, contained in a blockquote element. Someone famous in Source Title Featured Special title treatment With supporting text below as a natural lead-in to additional content. Go somewhere 2 days ago Width Cards are 100% wide by default. Set their width with custom CSS, place them in Col components, or pass sizing utilities through className . Grid Using the grid, wrap cards in columns and rows as needed. Card title With supporting text below as a natural lead-in to additional content. Go somewhere Card title With supporting text below as a natural lead-in to additional content. Go somewhere Utilities Use our handful of available sizing utilities to quickly set a card’s width. Card title With supporting text below as a natural lead-in to additional content. Button Card title With supporting text below as a natural lead-in to additional content. Button Custom CSS Use custom CSS in your stylesheets or as inline styles to set a width. Card title With supporting text below as a natural lead-in to additional content. Go somewhere Navigation Add some navigation to a card’s header (or block) with Bootstrap’s nav components . Active Link Disabled Special title treatment With supporting text below as a natural lead-in to additional content. Go somewhere This works with Nav using variant=&quot;pills&quot; as well. Active Link Disabled Special title treatment With supporting text below as a natural lead-in to additional content. Go somewhere Images Cards include a few options for working with images. Choose from appending “image caps” at either end of a card, overlaying images with card content, or simply embedding the image in a card. Image caps Similar to headers and footers, cards can include top and bottom “image caps”—images at the top or bottom of a card. Card title This is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Last updated 3 mins ago Card title This is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Last updated 3 mins ago Image overlays Turn an image into a card background and overlay your card’s text. Depending on the image, you may need additional styles or utilities through className . Card title This is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Last updated 3 mins ago Note that content should not be larger than the height of the image. If content is larger than the image the content will be displayed outside the image. Card row Set row on Card to make it horizontal. Set CardImage 's placement prop to start or end to position the image at either inline edge. Card title This is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Last updated 3 mins ago And with the reverse layout: Card title This is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Last updated 3 mins ago Theme variants Customize cards by setting the theme prop. By default, cards use bg for their background and border colors; set subtle to use more subtle colors. Primary Card title Card text… Accent Card title Card text… Secondary Card title Card text… Success Card title Card text… Danger Card title Card text… Warning Card title Card text… Info Card title Card text… Inverse Card title Card text… Primary Card title Card text… Accent Card title Card text… Secondary Card title Card text… Success Card title Card text… Danger Card title Card text… Warning Card title Card text… Info Card title Card text… Inverse Card title Card text… Translucent cards Set translucent on Card to blur and saturate its background. Header and footer backgrounds are also adjusted for a consistent look. Translucent card This card has a translucent background with a backdrop blur effect. Go somewhere Featured Card with header Headers and footers are also made translucent to maintain a consistent look. Go somewhere 2 days ago Card layout In addition to styling the content within cards, Bootstrap includes a few options for laying out series of cards. Card groups Use card groups to render cards as a single, attached element with equal width and height columns. Card groups start off stacked and use display: flex; to become attached with uniform dimensions starting at the sm breakpoint. This layout uses container queries , so place CardGroup inside a query container with the contains-inline utility applied through the parent's className . Without a query container, the cards remain stacked. Card title This is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Last updated 3 mins ago Card title This card has supporting text below as a natural lead-in to additional content. Last updated 3 mins ago Card title This is a wider card with supporting text below as a natural lead-in to additional content. This card has even longer content than the first to show that equal height action. Last updated 3 mins ago When using card groups with footers, their content will automatically line up. Card title This is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Last updated 3 mins ago Card title This card has supporting text below as a natural lead-in to additional content. Last updated 3 mins ago Card title This is a wider card with supporting text below as a natural lead-in to additional content. This card has even longer content than the first to show that equal height action. Last updated 3 mins ago Grid cards Use Row and Col to control how many cards appear per row. Set responsive column props on Row —for example, xs={1} and md={2} —to lay cards out in one column on small viewports and two equal-width columns from the medium breakpoint up. Card title This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Card title This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Card title This is a longer card with supporting text below as a natural lead-in to additional content. Card title This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Change the md prop on Row to 3 and you’ll see the fourth card wrap. Card title This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Card title This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Card title This is a longer card with supporting text below as a natural lead-in to additional content. Card title This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. When you need equal heights, apply a height utility through each Card 's className . To make that the default, set --bs-card-height: 100% in your CSS module. Card title This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Card title This is a short card. Card title This is a longer card with supporting text below as a natural lead-in to additional content. Card title This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Just like with card groups, card footers will automatically line up. Card title This is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer. Last updated 3 mins ago Card title This card has supporting text below as a natural lead-in to additional content. Last updated 3 mins ago Card title This is a wider card with supporting text below as a natural lead-in to additional content. This card has even longer content than the first to show that equal height action. Last updated 3 mins ago CSS Variables Customize the component with the following local CSS variables. Override them through the wrapper’s style prop or your own CSS module. CSS variable Default --bs-card-spacer-y var(--bs-spacer-6) --bs-card-spacer-x var(--bs-spacer-6) --bs-card-subtitle-color inherit --bs-card-border-width var(--bs-border-width) --bs-card-border-color var(--bs-border-color) --bs-card-border-radius var(--bs-radius-7) --bs-card-box-shadow none --bs-card-inner-border-radius calc(var(--bs-card-border-radius) - var(--bs-border-width)) --bs-card-cap-padding-y var(--bs-spacer-3) --bs-card-cap-padding-x var(--bs-spacer-5) --bs-card-cap-bg var(--bs-bg-1) --bs-card-cap-color inherit --bs-card-height auto --bs-card-color inherit --bs-card-bg var(--bs-bg-body) --bs-card-img-overlay-padding var(--bs-card-spacer-y) --bs-card-group-margin 0.75rem --bs-card-body-gap calc(var(--bs-card-spacer-y) * 0.5)</description></item><item><title>Button group</title><link>https://idea-react.pages.dev/components/button-group/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/button-group/</guid><description>Button group Group a series of buttons together on a single line or stack them in a vertical column. Use ButtonGroup with vertical , divider , and size props for the variations below, and ButtonToolbar to combine groups. Both wrappers supply their default grouping role; provide an accessible label for each group or toolbar. Examples Wrap a series of buttons in ButtonGroup . Left Middle Right Button groups require an appropriate role attribute and explicit label to ensure assistive technologies like screen readers identify buttons as grouped and announce them. Use role=&quot;group&quot; for button groups or role=&quot;toolbar&quot; for button toolbars. Then use aria-label or aria-labelledby to label them. With links ButtonGroup can also group links; use the navigation components for navigation-specific behavior. Active link Link Link Dividers Set the divider prop on ButtonGroup to add dividers between buttons. This is most useful with buttons that share a theme color and solid fill. Left Active Right Left Right Works with vertical button groups, too. Left Active Right Left Right Theme variants Set the theme prop on each Button in the group to apply a consistent theme color. Left Middle Right You can mix and match button variants in a button group. Left Middle Right Style variants All button styles are supported in button groups. Set divider on ButtonGroup to add dividers between some styles, or use the button borders with other styles. Left Middle Right Left Middle Right Left Middle Right Toggle buttons Checkbox Checkbox toggle buttons can be grouped together. Any or all of the buttons can be checked. Check 1 Check 2 Check 3 Radio By design, radio toggle button groups can only have one button checked at a time. Radio 1 Radio 2 Radio 3 Button toolbar Combine ButtonGroup components inside ButtonToolbar for more complex layouts. Pass spacing utilities through the className of the toolbar or its children. 1 2 3 4 5 6 7 8 Feel free to mix input groups with button groups in your toolbars. As in the example above, you may need spacing utilities through className to lay them out. 1 2 3 4 @ 1 2 3 4 @ Sizing Set the size prop on ButtonGroup to resize its buttons together. Set it on each group independently when nesting multiple groups. Left Middle Right Left Middle Right Left Middle Right Left Middle Right Nesting Place a ButtonGroup inside another ButtonGroup when you want menus mixed with a series of buttons. 1 2 Menu link Menu link Vertical variation Make a set of buttons appear vertically stacked rather than horizontally. Split button menus are not supported here. Button Button Button Button Menu link Menu link Button Button Menu link Menu link Menu link Menu link Menu link Menu link Radio 1 Radio 2 Radio 3</description></item><item><title>Button</title><link>https://idea-react.pages.dev/components/button/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/button/</guid><description>Button Use Bootstrap’s custom button styles for actions in forms, dialogs, and more with support for multiple sizes, states, and more. Button renders a native button, or an anchor when given href . Its variant , theme , size , icon , styled , active , and disabled props generate the styles described below. Use ButtonInput for input elements and ToggleButton for checkbox- or radio-backed controls. Base class Button applies its base button styles automatically. Set its variant and theme props to choose the visual style and color. Base class Use Button 's className prop to add custom styles; built-in variants can be combined with the theme prop or extended in your own styles. Playground Bootstrap includes several button variants, each serving its own semantic purpose, with a few extras thrown in for more control. Combined with our utilities, you have a very powerful set of defaults to choose from. Variants Compare all button variants and styles at once: Primary Primary Primary Primary Accent Accent Accent Accent Secondary Secondary Secondary Secondary Success Success Success Success Danger Danger Danger Danger Warning Warning Warning Warning Info Info Info Info Inverse Inverse Inverse Inverse Conveying meaning to assistive technologies: Color provides only a visual indication. Ensure the meaning is also clear from the content or included in accessible text. Link buttons Set variant=&quot;link&quot; on Button to make it look like a link. Link Link buttons can also be styled with the theme colors. Primary Accent Secondary Success Danger Warning Info Inverse Styled buttons Set the styled prop on a solid Button to add gradients and shadows for visual depth. Customize the effect further with CSS variables. Primary Accent Secondary Success Danger Warning Info Inverse The gradient and shadow can be customized via CSS variables: Variable Description --bs-btn-gradient-start Top of gradient (default: rgb(255 255 255 / 12.5%) ) --bs-btn-gradient-end Bottom of gradient (default: rgb(0 0 0 / 7.5%) ) --bs-btn-border-mix-color Color to mix with the button background (default: #000 ) --bs-btn-border-mix-amount Amount of color to mix with the button background (default: 10% ) --bs-btn-border-hover-mix-amount Amount of color to mix with the button background on hover (default: 12.5% ) --bs-btn-border-active-mix-amount Amount of color to mix with the button background on active (default: 20% ) --bs-btn-shadow Resting state shadow --bs-btn-active-shadow Pressed/active state shadow Button tags Button renders a native &lt;button> by default and renders an &lt;a> when href is provided. In either case, its default ARIA role is button ; provide an explicit role only when you need to override it. ButtonInput renders an &lt;input> element with native button behavior. Link Button Sizes Set size=&quot;lg&quot; or size=&quot;sm&quot; on Button for a larger or smaller size. Large button Large button Small button Small button Extra small button Extra small button You can even roll your own custom sizing with CSS variables: Custom button Icon buttons Set the icon prop on Button for a square icon-only button. It sets a 1:1 aspect ratio and removes padding, making the button square based on its minimum height. Always include an aria-label on icon-only buttons for screen reader users. Combine with the size prop for different icon button sizes: Disabled state Set the disabled prop on Button to prevent interaction and apply disabled styling. Native button elements also prevent activation when disabled. Primary button Button Primary button Button When Button renders as a link, its disabled prop removes navigation and keyboard focus as well as applying disabled styling. Primary link Link If there’s an href attribute, add tabindex=&quot;-1&quot; and aria-disabled=&quot;true&quot; to prevent keyboard focus and assistive technologies from interacting with the link. Primary link Link You may also want to use custom JavaScript to disable the link functionality altogether. In these React examples, disabled handles this for you: Button removes the link destination, prevents navigation, and supplies aria-disabled and tabIndex={-1} . Block buttons Use a grid container with gap utilities passed through className to create a vertical stack of full-width buttons. Button Button This responsive variation changes from a vertical stack to a horizontal layout at the md breakpoint. Resize your browser to see the layout change. Button Button Use a Col with xs={6} to constrain the button stack to half the available width, and center it with margin utilities passed through className . Button Button Additional utilities can be used to adjust the alignment of buttons when horizontal. Here we’ve taken our previous responsive example and added some flex utilities and a margin utility on the button to right-align the buttons when they’re no longer stacked. Button Button Toggle buttons Use ToggleButton to create button-like checkboxes and radio buttons. It provides the button appearance and interaction behavior, and can be grouped in a button group . Visually, these toggle buttons are identical to our active-state buttons , but are conveyed differently by assistive technologies. Checkbox toggles will be announced by screen readers as &quot;checked&quot;/&quot;not checked&quot; as they are checkboxes under the hood. Active-state buttons are announced as &quot;button&quot;/&quot;button pressed&quot;. It’s up to you to decide which approach makes more sense for your use case. Checkboxes Checkboxes can be checked, unchecked, or disabled. Checkbox-based toggle buttons only toggle a single button’s state. Checked Toggle Disabled Radios Radios can be checked, unchecked, or disabled. Use radio-based toggle buttons to toggle states between a set of buttons that include input elements with the same name attribute value. Checked Toggle Disabled Toggle Active state Button does not manage active state. Pass active from application state so the application remains the source of truth. For toggle semantics, Button sets aria-pressed when active is provided. Buttons without active remain ordinary buttons. Toggle buttons Render the active state supplied by your application: Inactive toggle button Active toggle button Disabled toggle button Inactive link button Active toggle link Disabled link button Because Button defaults to the button role even when href renders an anchor, the active prop also supplies aria-pressed without additional role configuration. CSS Variables Buttons use CSS variables for real-time customization. These are set on the base .btn class and inherited by all button variants. CSS variable Default --bs-btn-gap var(--bs-btn-input-gap) --bs-btn-min-height var(--bs-btn-input-min-height) --bs-btn-padding-x var(--bs-btn-input-padding-x) --bs-btn-padding-y var(--bs-btn-input-padding-y) --bs-btn-font-size var(--bs-btn-input-font-size) --bs-btn-font-weight var(--bs-btn-input-font-weight) --bs-btn-line-height var(--bs-btn-input-line-height) --bs-btn-color var(--bs-fg-body) --bs-btn-white-space nowrap --bs-btn-border-width var(--bs-border-width) --bs-btn-border-color transparent --bs-btn-border-radius var(--bs-radius-5) --bs-btn-hover-border-color transparent --bs-btn-disabled-opacity 0.65 --bs-btn-transition-property color, background-color, border-color, box-shadow --bs-btn-transition-duration 0.15s --bs-btn-transition-timing ease-in-out The variant prop updates these variables according to the selected theme , allowing buttons to adapt automatically to their theme color. Styled buttons use local CSS variables. CSS variable Default --bs-btn-gradient-start rgba(255, 255, 255, 0.125) --bs-btn-gradient-end rgba(0, 0, 0, 0.075) --bs-btn-border-mix-color #000 --bs-btn-border-mix-amount 10% --bs-btn-border-hover-mix-amount 12.5% --bs-btn-border-active-mix-amount 20% --bs-btn-shadow 0 1px 2px rgb(0 0 0 / 15%), inset 0 1px 0 rgb(255 255 255 / 10%) --bs-btn-active-shadow inset 0 2px 4px rgba(0, 0, 0, 0.15) Link buttons use local CSS variables. CSS variable Default --bs-btn-font-weight var(--bs-btn-input-font-weight) --bs-btn-color var(--bs-fg-body) --bs-btn-bg var(--bs-theme-bg) --bs-btn-border-color transparent --bs-btn-hover-color oklch(from var(--bs-theme-contrast) calc(l * .95) calc(c * 1.1) h) --bs-btn-hover-bg oklch(from var(--bs-theme-bg) calc(l * .95) calc(c * 1.1) h) --bs-btn-hover-border-color transparent --bs-btn-active-color oklch(from var(--bs-theme-contrast) calc(l * .9) calc(c * 1.15) h) --bs-btn-active-bg oklch(from var(--bs-theme-bg) calc(l * .9) calc(c * 1.15) h) --bs-btn-active-border-color oklch(from var(--bs-theme-bg) calc(l * .9) calc(c * 1.15) h) --bs-btn-disabled-color var(--bs-theme-contrast) --bs-btn-disabled-border-color var(--bs-theme-bg)</description></item><item><title>Breadcrumb</title><link>https://idea-react.pages.dev/components/breadcrumb/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/breadcrumb/</guid><description>Breadcrumb Indicate the current page's location within a navigational hierarchy using explicit divider elements. Compose Breadcrumb , BreadcrumbItem , BreadcrumbLink , and BreadcrumbDivider inside a labelled navigation element. Use the item’s active prop to mark the current page; BreadcrumbLink also supports active when the link itself needs the current-page styling. Example Use an ordered list with BreadcrumbItem for each page and BreadcrumbDivider elements between them. Leave a divider empty to use the default chevron icon, or add your own separator content. Mark the current BreadcrumbItem as active. Home Library Data Home Documents 2026 Dividers Dividers are added explicitly using BreadcrumbDivider elements. An empty divider renders a default chevron, drawn with a CSS mask so it inherits the divider color (including in dark mode). To use a different separator, add your own content—any SVG icon, text character, or custom markup—which overrides the default. Default divider Leave the BreadcrumbDivider empty to get the built-in chevron. Customize it globally by overriding the --bs-breadcrumb-divider-icon , --bs-breadcrumb-divider-width , and --bs-breadcrumb-divider-height variables. Home Library SVG dividers Add an inline SVG inside the divider to override the default with your own crisp, scalable icon. Use currentColor for the stroke or fill so it inherits the divider color for easy theming. Home Library Text dividers For simple text-based dividers, just add the character directly. Home / Library / Data Custom dividers Use any content you like—different icons, decorative elements, or themed separators. Home › Library › Data Accessibility Since breadcrumbs provide navigation, it’s important to follow these practices: Give the navigation landmark an accessible name, such as aria-label=&quot;Breadcrumb&quot; . Add aria-current=&quot;page&quot; to the BreadcrumbItem containing the current page Divider elements are automatically hidden from assistive technology via CSS For more information, see the ARIA Authoring Practices Guide breadcrumb pattern . CSS Variables Customize the component with the following local CSS variables. Override them through the wrapper’s style prop or your own CSS module. CSS variable Default --bs-breadcrumb-font-size inherit --bs-breadcrumb-bg transparent --bs-breadcrumb-border-radius var(--bs-radius-5) --bs-breadcrumb-divider-color var(--bs-fg-4) --bs-breadcrumb-divider-icon SVG mask image --bs-breadcrumb-divider-width 0.375rem --bs-breadcrumb-divider-height 0.75rem --bs-breadcrumb-link-padding-x 0.75rem --bs-breadcrumb-link-padding-y 0.25rem --bs-breadcrumb-link-color var(--bs-fg-3) --bs-breadcrumb-link-hover-color var(--bs-fg-2) --bs-breadcrumb-link-hover-bg var(--bs-bg-1) --bs-breadcrumb-link-active-color var(--bs-fg-1) --bs-breadcrumb-link-border-radius var(--bs-radius-7)</description></item><item><title>Badges</title><link>https://idea-react.pages.dev/components/badge/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/badge/</guid><description>Badges Small components for indicating status and counts, or labelling items. The examples use Badge with variant , theme , and pill props to generate the corresponding Bootstrap styles. Examples Badges are tiny, static display components used for adding context to other elements. They can be used as part of navigation, buttons, and more to provide a counter or label. Badges scale to match the size of the immediate parent element by using relative font sizing and em units. Badges come in three variants: solid (default), subtle, and outline. New New New Headings Badges adapt to the font-size of the parent element. Example heading New Example heading New Example heading New Example heading New Example heading New Example heading New Buttons Badges can be used as part of links or buttons to provide a counter. Notifications 4 Note that depending on how they are used, badges may be confusing for users of screen readers and similar assistive technologies. While the styling of badges provides a visual cue as to their purpose, these users will simply be presented with the content of the badge. Depending on the specific situation, these badges may seem like random additional words or numbers at the end of a sentence, link, or button. Unless the context is clear (as with the “Notifications” example, where it is understood that the “4” is the number of notifications), Include additional context in accessible text when the badge's meaning is not clear. Positioned Use Badge for the indicator and pass positioning and spacing utilities through its className . Inbox 99+ unread messages For a dot indicator without a count, use Badge with appearance utilities in className and accessible text describing the status. Profile New alerts Variants Set theme on Badge to apply a semantic theme color. Primary Accent Secondary Success Danger Warning Info Inverse Primary Accent Secondary Success Danger Warning Info Inverse Primary Accent Secondary Success Danger Warning Info Inverse Conveying meaning to assistive technologies: Color provides only a visual indication. Ensure the meaning is also clear from the content or included in accessible text. CSS Variables Customize the component with the following local CSS variables. Override them through the wrapper’s style prop or your own CSS module. CSS variable Default --bs-badge-gap 0.375em --bs-badge-padding-x 0.625em --bs-badge-padding-y 0.25em --bs-badge-font-size clamp(12px, 0.75em, 0.75em) --bs-badge-font-weight var(--bs-font-weight-semibold) --bs-badge-color inherit --bs-badge-bg var(--bs-bg-2) --bs-badge-border-width var(--bs-border-width) --bs-badge-border-color transparent --bs-badge-border-radius var(--bs-radius-7)</description></item><item><title>Avatar</title><link>https://idea-react.pages.dev/components/avatar/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/avatar/</guid><description>Avatar Documentation and examples for avatars, including image avatars, initials, status indicators, and avatar stacks. Use Avatar for images, initials, and status indicators, AvatarImage for a standalone image, and AvatarStack for overlapping groups. Set size , theme , subtle , and status to configure the avatar appearances described below. Examples Avatars are used to represent users or entities. They can display an image or initials as a fallback. Image Use Avatar with AvatarImage for image-based avatars. The parent Avatar element provides an easy wrapper for additional avatar features like status indicators and stacks. You’re welcome to use AvatarImage on its own if you only need a single HTML element. When used inside the Avatar wrapper, the image fills the wrapper and its size is set with --bs-avatar-size . Used on its own, AvatarImage honors its own width and height instead, so set them to your desired size. Initials Use text content inside Avatar for initials-based avatars. AB CD EF GG GH IJ KL MN OP Set the subtle prop to create a subtle avatar. AB CD EF GG GH IJ KL MN OP Sizes Avatars come in multiple sizes: extra small, small, default, large, and extra large. Use a custom size by modifying the --bs-avatar-size variable. The numeric size prop sets it in rem. Status indicator Set the status prop to show an indicator inside the avatar. Each status has a distinct shape and color: online — green circle offline — gray rounded square busy — red rounded square away — yellow circle Because the status is conveyed purely through color and shape, provide a statusLabel (e.g. Online ) so assistive technologies can announce it. Status with sizes The status indicator scales with the avatar size. Avatar stack Use AvatarStack to group multiple avatars together with overlapping effect. Avatars are rendered in reverse order so the first avatar appears on top. Stacks use a percentage of the avatar size to determine how much to overlap stacked avatars. Stack with sizes As a shorthand, size props are available for AvatarStack and Avatar . Stack with count Combine with initials to show a count of additional users. +5 +5 CSS Variables Customize the component with the following local CSS variables. Override them through the wrapper’s style prop or your own CSS module. CSS variable Default --bs-avatar-size 2.5rem --bs-avatar-border-radius 50% --bs-avatar-border-width 2px --bs-avatar-border-color var(--bs-bg-body) --bs-avatar-bg var(--bs-bg-2) --bs-avatar-color var(--bs-fg-body) --bs-avatar-status-size 0.75rem --bs-avatar-status-border-width 2px --bs-avatar-status-border-color var(--bs-bg-body) --bs-avatar-stack-spacing -0.3 --bs-avatar-stack-transition transform .2s ease-in-out</description></item><item><title>Alert</title><link>https://idea-react.pages.dev/components/alert/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/alert/</guid><description>Alert Provide contextual feedback messages for typical user actions with the handful of available and flexible alert messages. Default alert Alerts are flex containers that can contain any length of text and an optional close button. They’re designed to be used with theme colors, but have neutral fallback colors when no theme is applied. For inline dismissal, use the dismissible prop. Add custom content as children and style it with components or className utilities as needed. A simple alert—check it out! Variants Use any of our theme values for color mode adaptive, contextual styling. A simple primary alert—check it out! A simple accent alert—check it out! A simple secondary alert—check it out! A simple success alert—check it out! A simple danger alert—check it out! A simple warning alert—check it out! A simple info alert—check it out! A simple inverse alert—check it out! Color alone does not convey meaning to assistive technologies. Include visible text or additional visually hidden text to communicate the purpose of the message. Live example Click the button below to show an alert (hidden with inline styles to start), then dismiss (and destroy) it with the built-in close button. Link color Use the AlertLink component to quickly provide matching colored links within any alert. A simple primary alert with an example link . Give it a click if you like. A simple accent alert with an example link . Give it a click if you like. A simple secondary alert with an example link . Give it a click if you like. A simple success alert with an example link . Give it a click if you like. A simple danger alert with an example link . Give it a click if you like. A simple warning alert with an example link . Give it a click if you like. A simple info alert with an example link . Give it a click if you like. A simple inverse alert with an example link . Give it a click if you like. With icons Render Icon inside Alert for an icon, and use flexbox utilities through className to align the content. Depending on the icon and content, you may need additional utilities or custom styles. An example alert with an icon Dismiss Use the dismissible prop to dismiss an alert inline. Here’s how: dismissible adds a close button to the alert. Use onClosed to synchronize application state after dismissal. An alert fades out before it is removed. The wrapper adds its exit state for the length of the transition, so no extra classes are needed in your markup. Pass instant to remove the alert at once instead. See Transitions for the tokens that tune the fade. You can see this in action with a live demo: Something’s wrong, check the fields below and try again. When an alert is dismissed, the element is completely removed from the page structure. If a keyboard user dismisses the alert using the close button, their focus will suddenly be lost and, depending on the browser, reset to the start of the page/document. For this reason, we recommend including additional JavaScript that handles the onClosed callback and programmatically sets focus() to the most appropriate location in the page. If you’re planning to move focus to a non-interactive element that normally does not receive focus, make sure to add tabindex=&quot;-1&quot; to the element. Additional content For simple vertical layouts, it should be enough to add the flex-column class to the alert. Well done! Aww yeah, you successfully read this important alert message. This example text is going to run a bit longer so that you can see how spacing within an alert works with this kind of content. Whenever you need to, be sure to use margin utilities to keep things nice and tidy. More complex layouts may require additional HTML within the alert—like when mixing in icons and dismiss buttons. More complex alert Aww yeah, you successfully read this important alert message. This example text is going to run a bit longer so that you can see how spacing within an alert works with this kind of content. CSS Variables Local CSS custom properties expose the component’s colors, spacing, borders, and transitions. Override them through style or a CSS module. The defaults below come from the Bootstrap stylesheet used by Idea React; see the upstream variable reference . Variable Default --bs-alert-gap var(--bs-spacer-3) --bs-alert-bg var(--bs-bg-1) --bs-alert-padding-x var(--bs-spacer) --bs-alert-padding-y var(--bs-spacer) --bs-alert-color inherit --bs-alert-border-color var(--bs-border-color) --bs-alert-border-radius var(--bs-radius-7) --bs-alert-link-color inherit --bs-alert-transition-property opacity --bs-alert-transition-duration 0.15s --bs-alert-transition-timing linear JavaScript behavior The React wrapper manages dismissal and removes the alert after its fade transition. Do not initialize a Bootstrap plugin on the same element. Events onClose runs when dismissal begins, and onClosed runs after the transition and removal. Use onClosed to restore keyboard focus to an appropriate control, as in the live example.</description></item><item><title>Accordion</title><link>https://idea-react.pages.dev/components/accordion/</link><guid isPermaLink="true">https://idea-react.pages.dev/components/accordion/</guid><description>Accordion Build vertically collapsing accordions with native HTML &lt;details> and &lt;summary> elements. The accordion uses native HTML &lt;details> and &lt;summary> elements, leveraging the name attribute to create exclusive accordions where only one item can be open at a time. This approach requires no JavaScript for core functionality and is fully accessible by default. Example Click the accordions below to expand/collapse the accordion content. Each &lt;details> element shares the same name attribute value, creating an exclusive accordion where opening one item automatically closes the others. To render an accordion that’s expanded by default, add the open attribute to the &lt;details> element. The panel height animation needs interpolate-size . Browsers without it open and close the panel at once. See Transitions to change the timing or to remove it. The animation effect depends on the prefers-reduced-motion media query. See the reduced motion accessibility guidance . Variants Set the theme prop on Accordion to apply a semantic theme color to its open items. Small Set size=&quot;sm&quot; on Accordion for a more compact layout with tighter padding, a smaller border radius, and a smaller font size. Flush Set the flush prop on Accordion to remove some borders and rounded corners so it can sit edge-to-edge with its parent container. Gap Set the gap prop on Accordion to add space between items. Each item is a separate rounded card. The gap lives on the accordion, not the panel. The panel still animates only its block-size , so the open and close transition stays smooth. Always open Omit the name attribute on each &lt;details> element to allow multiple accordion items to be open simultaneously. Expand &amp; Collapse all To enable expanding and collapsing of all accordion items at once, remove the name attribute from each &lt;details> element using JavaScript. This allows multiple accordion items to be open simultaneously. Restore the name attribute when you collapse the items again if you want exclusive behavior back. We use the following JavaScript for this demo: AccordionToggle handles the expand/collapse-all action and maintains aria-expanded for you. Nested Nest an Accordion inside an AccordionBody to create an accordion within an item. Use unique name attribute values for each level so parent and child accordions operate independently. Accessibility The native &lt;details> and &lt;summary> elements provide built-in accessibility: Screen readers announce the expanded/collapsed state automatically Keyboard navigation works out of the box (Enter/Space to toggle) The &lt;summary> element is focusable by default No ARIA attributes are required as the semantics are built into the elements CSS Variables Use CSS custom properties on the component to customize its appearance without recompiling Bootstrap. .accordion { --bs-accordion-padding-x: 1.25rem; --bs-accordion-padding-y: 1rem; --bs-accordion-color: var(--bs-fg-body); --bs-accordion-bg: var(--bs-bg-body); --bs-accordion-transition-property: 'color, background-color, border-radius'; --bs-accordion-transition-duration: 0.15s; --bs-accordion-transition-timing: ease-in-out; --bs-accordion-panel-transition-property: 'content-visibility, block-size'; --bs-accordion-panel-transition-duration: 0.2s; --bs-accordion-panel-transition-timing: ease; --bs-accordion-border-color: var(--bs-border-color); --bs-accordion-border-width: var(--bs-border-width); --bs-accordion-border-radius: var(--bs-accordion-radius, var(--bs-radius-7)); --bs-accordion-gap: 0; --bs-accordion-btn-color: var(--bs-fg-2); --bs-accordion-btn-bg: var(--bs-bg-body); --bs-accordion-btn-icon-width: 1rem; --bs-accordion-btn-icon-transform: rotate(-180deg); --bs-accordion-btn-icon-transition: transform 0.2s ease-in-out; --bs-accordion-active-color: var(--bs-fg-body); --bs-accordion-active-bg: var(--bs-bg-2); } Customize Custom icons Use the icon prop on AccordionHeader to choose an Icon font name, or icon={false} to remove it. &lt;AccordionHeader icon=&quot;plus-lg&quot;>Accordion title&lt;/AccordionHeader> Events Use the native onToggle prop on AccordionItem to respond to open-state changes. Programmatic control Pass the native open prop to AccordionItem to control its state. AccordionToggle target=&quot;#id&quot; expands or collapses all items together.</description></item></channel></rss>