Description
The IllustratedMessage component currently supports the danger and unavailable status. Since these already represent semantic status variants, it raises the question of whether the component should provide a more complete set of status options.
Discussion
Should IllustratedMessage support additional semantic states such as:
Would offering the full set of common status variants make the component more consistent and easier to adopt, or would it blur the component's intended purpose?
Another question is whether IllustratedMessage is gradually evolving into a large, illustrated version of an alert component. With the introduction of a status property, its role becomes less about representing an empty state and more about communicating semantic feedback.
Description
The
IllustratedMessagecomponent currently supports thedangerandunavailablestatus. Since these already represent semantic status variants, it raises the question of whether the component should provide a more complete set of status options.Discussion
Should IllustratedMessage support additional semantic states such as:
Would offering the full set of common status variants make the component more consistent and easier to adopt, or would it blur the component's intended purpose?
Another question is whether IllustratedMessage is gradually evolving into a large, illustrated version of an alert component. With the introduction of a status property, its role becomes less about representing an empty state and more about communicating semantic feedback.