configOverrides when a modal instance needs code-level overrides.
Logo Configuration
Theme Configuration
In v3, the theme system uses OKLCH color mixing to generate a complete, harmonious palette from just two colors:foregroundColor and backgroundColor. You no longer need to specify individual colors for buttons, accents, text, or dark mode variants.
Basic Theme Example
Dark Mode Configuration
Just provide dark colors forbackgroundColor and foregroundColor. The system auto-detects dark mode from the background color lightness and generates an appropriate palette:
In v3, separate dark mode color properties (
darkForegroundColor, darkBackgroundColor, darkAccentColor) are no longer needed.
The palette is auto-generated from your foregroundColor and backgroundColor, and dark/light mode is auto-detected from the background color lightness.
Use the mode property only if you need to override the auto-detection (e.g., for a background color near the light/dark boundary that gets misclassified).Foreground Mix Ratio
TheforegroundMixRatio controls how much your foregroundColor bleeds into UI surfaces like buttons, inputs, and borders. The default is 0.04.
Advanced Customization with CSS Overrides
For granular control over specific UI elements, use thecssOverrides property to set raw CSS custom properties. Overrides are applied after the palette is generated — they replace specific generated values without affecting the rest of the theme — and are scoped to the Para modal, so they never leak into your app’s styles.
Where to set overrides
The SDK can read CSS override values that already exist on partner config, but the Developer Portal does not expose a CSS override editor today.
Available CSS Variables
These are the custom properties the modal actually consumes, so overriding them takes effect:To change the font, use the
font property (below) — not a CSS override. The font family is applied directly to the modal, not through a --para-* variable.