Configuration
ConfigProvider is bestax-bulma's extension point for app-wide choices that Bulma itself can't express in React: a class-prefix namespace for the Bulma CSS classes your components emit, and a default icon library every Icon should fall back to. It works through React context, so any setting you provide applies to every descendant component — no prop drilling.
CSS Variables
Bulma v1 introduces comprehensive support for CSS custom properties (CSS variables), enabling runtime customization without Sass compilation. bestax-bulma gives you a first-class React surface for all 500+ of them through the Theme component: named, camelCase props for the common variables, a bulmaVars escape hatch for the long tail, and automatic scoping so themes compose via React context — no manual style-sheet injection, no string concatenation, fully type-checked.
Sass Customization
Sass customization is the build-time half of bestax's two-layer theming story. You set Bulma's Sass variables once at build time to bake in defaults (brand colors, fonts, radii); then bestax's Theme component lets you adjust any of them at runtime via CSS variables. The two layers are designed to work together — Sass defines what ships, Theme adjusts what renders.
Bulma V1
bestax-bulma is built for Bulma v1 — the version released in 2024 that introduced CSS custom properties, true CSS Grid, and skeleton loading — and it layers on a curated set of components Bulma doesn't ship. It's not a neutral wrapper around Bulma's markup; it's a React library that extends Bulma with the pieces real apps need (Carousel, Dialog, Autocomplete, Rate, Slider, Taginput, Toast, Sidebar, and more) while keeping the Bulma classes you already know.
Responsiveness
This guide covers how Bestax components handle responsive design. Bestax extends Bulma with React components and additional UI on top of Bulma's CSS, so the responsive props and breakpoints you'll see here inherit directly from Bulma — you just drive them through Bestax's typed React API.