EmptyState

The <EmptyState> component is used to communicate that a container, list, or page currently has no data to display. It provides visual confirmation that the lack of data is a valid system state, ensuring users do not mistake the empty space for a loading error or a bug.

It serves as a bridge between an empty screen and a populated one, offering context and guidance.

Anatomy

The EmptyState component typically consists of the following elements:

Appearance

The appearance of a component can be customized using the variant and size props. These props adjust the visual style and dimensions of the component, available values are based on the active theme.

Usage

The <EmptyState> component is ideal for scenarios where a user might expect to see content, but the data set is empty despite a successful page load.

Use this component to confirm that the lack of data is a valid state in the following situations:

• Initial States: When a user visits a feature or dashboard for the first time and has no data due to a lack of activity.
• User-Cleared States: When a user has successfully resolved, deleted, or triaged all items in a list.
• No Results (Search & Filter): When a list or table is empty because no items match the current search query or applied filters.

import { Button, EmptyState, Table } from '@marigold/components';export default () => (  <Table aria-label="Events Table">    <Table.Header>      <Table.Column>Event Name</Table.Column>      <Table.Column>Date</Table.Column>      <Table.Column>Venue</Table.Column>      <Table.Column>Status</Table.Column>    </Table.Header>    <Table.Body      emptyState={() => (        <EmptyState          title="No events found"          description="There are currently no events to display. Add new events to see them here."          action={            <Button size="small" variant="primary">              Add New Event            </Button>          }        />      )}    >      {[]}    </Table.Body>  </Table>);

Best Practices

Timing is critical when displaying empty states. Always show a loading indicator (Skeleton or Spinner) while data is being fetched, and only reveal the empty state after the request completes and confirms no results exist. This prevents the "Flash of Empty Content" - a jarring flicker that can confuse users and make the interface feel unstable.

It's equally important to distinguish between empty and error states. Use the <EmptyState> component exclusively for successful operations that return no data. For system failures, network errors, or other exceptions, use a <Toast> notification instead. This clear separation helps users understand whether they need to take action or simply recognize that no content exists yet.

Content Strategy

Effective <EmptyState> content serves as a conversation with the user, bridging the gap between a blank screen and their first successful interaction. Since an empty screen can be mistaken for a system error, the messaging should immediately reassure users that everything is functioning as expected. The text must confirm that the application is working correctly and that the lack of data is a valid state.

Accessibility

The <EmptyState> component is accessible by default through its required title, which provides screen readers with clear context about the empty state. The decorative illustration is marked with aria-hidden="true", ensuring assistive technologies correctly ignore it and focus on the meaningful text content.

Props

EmptyState

Alternative components

• Loader: Use for loading states before data is fetched. Unlike EmptyState, loaders indicate that content is actively being retrieved and will appear shortly.

• Toast: Use for error states or system failures. When something goes wrong during data retrieval, a Toast provides immediate feedback without replacing the main content area.