Variant

Add a Variant property to your component for designers to choose from a predefined list of options.

Syntax

1
// Prop definition
2
props.Variant({
3
    name: string,
4
    options: string[],
5
    group?: string,
6
    tooltip?: string,
7
    defaultValue?: string,
8
})
9
10
// Prop value
11
string

Prop Definition

Define the Variant prop in your Webflow code component with a name and list of options. Optionally, you can add a group, tooltip text, and a default value that matches one of the pre-defined options.

1
props.Variant({
2
    name: string,
3
    options: string[],
4
    group?: string,
5
    tooltip?: string,
6
    defaultValue?: string,
7
})

Properties

• name: The name for the property.
• group: The group for this property. (optional)
• tooltip: The tooltip for the property. (optional)
• options: Array of available variant options.
• defaultValue: Default selected option. (optional)

Example

1
import { declareComponent } from '@webflow/react';
2
import { props } from '@webflow/data-types';
3
import { MyComponent } from "./MyComponent";
4
5
export default declareComponent(MyComponent, {
6
    name: "MyComponent",
7
    description: "A component with a Variant property",
8
    props: {
9
        style: props.Variant({
10
            name: "Button Style",
11
            group: "Style",
12
            options: ["Primary", "Secondary", "Tertiary"],
13
            defaultValue: "Primary"
14
        })
15
    }
16
});

Prop Value

The Variant prop provides a string value representing the selected option to your React component.

1
string

Properties

• n/a

Webflow properties panel

Example

1
import React from "react";
2
3
interface MyComponentProps {
4
    style?: "Primary" | "Secondary" | "Tertiary";
5
}
6
7
export const MyComponent = ({ style }: MyComponentProps) => {
8
    return (
9
        <button className={`button button--${style?.toLowerCase()}`}>
10
        Click me
11
        </button>
12
    );
13
}

When to use

Use a Variant prop when you want designers to:

• Choose from predefined visual styles
• Switch between component variations / themes
• Control component appearance

Best practices

• Use clear, descriptive option names
• Provide a sensible default value
• Keep options list manageable