Skip to content

Empty state

Empty state content

Implementations

The component EmptyState is available in the following technologies:

CSS Components
cssreactvue
Web Components
webreactvueangular

Parameters

Parameters

Parameters are the attributes that can be used to customize the component when using it in a project. They apply to the WebComponents implementation and wrappers and to the Vue and React CSS implementations. Some parameters names change between the implementations, in order to follow the conventions of each technology and framework.

For example, the param model is named ngModel in Angular, modelValue in Vue, but stays as model in React.

By default, all the parameters are optional or can be set in different, except for the ones marked as required

The parametrization of the component can be done with the following custom params or properties:

NameTypeSlottableDescription
image-srcstringThe URL of the image to display
image-altstringThe alt text of the image
pictogramstringThe name of the pictogram to display
headerstringThe title of the empty state
contentstringThe content of the empty state
button-textstringThe text of the button
button-iconstringThe icon of the button
button-icon-rightbooleanWhether the icon should be displayed on the right side of the button
customobject

A record of key-value pairs to set the CSS custom tokens. It's a complex attribute set as an JS object in stringified JSON format.

Example:

html
<z-empty-state custom='{"fill":"#06e7a3"}' />
custom-strstring

The stringified version of the custom property. It follows the pattern key:value;key:value;, with the possibility of setting multiple values and spaces between the punctuation characters.

Example:

html
<z-empty-state custom-str="fill:#06e7a3" />
z-themestring

Sets the theme of the component. The possible values are light and dark.

html
<z-empty-state z-theme="dark" />

From Figma to code

You can check the Figma implementation here. This are the available properties:

  • Size select

Customization

INFO

Check everything about the customization mechanics in the "How it works" documentation.

No customization tokens yet implemented for this component

Accessibility

...