Fill height
In scenarios where there is a requirement for the card to fill the height of the parent container, you can use the fillHeight prop.
Fill Height Card
This card fills the available height of its container.
Fill width
By default, Card width fills the available space of the parent container. However, when wrapped in a flexbox, Card shrinks to fit the available space. To prevent this, use the fillWidth prop.
Fill Width Card
This card fills the available width in a flex container.
Normal Card
This card has normal width behavior.
Marketing Card
Use these layouts when you need to draw customers' attention to upsell and cross-sell opportunities. Use them sparingly, mainly when they'll help customers solve immediate problems.
Research insight on marketing and cross-selling
Research from Twilio has shown that cross-sell cards aren't useful when the developers are in the product focused on urgent problems. They're likely to ignore these cards, regardless of how they're presented, until they're relevant to a current project they're working on.
Upgrade to Flex
Build modern contact centers with Twilio Flex. Scale your customer service operations with our programmable contact center platform.
Enhance Your App
Add video calling capabilities to your application with Twilio Video. Create immersive experiences for your users.
Composition notes
When a Card contains text content, use the following guidelines:
- Use a Heading to highlight the most important information.
- Use a Paragraph to add additional context. Do not repeat the information in the header. Front-load the most critical information.
- When presenting multiple Cards of equal weight on a single page, structure each Card's content similarly.
Do and don't
Do
Have a clear call to action when including Buttons. Avoid including more than one primary and one secondary button.
Don't
Don't put multiple primary actions in a Card
Do
Use a Heading in your Card that appropriately reflects the information architecture of the page.
Don't
Don't use Cards to highlight multiple primary actions on a single page.
Do
Use a Heading to set a clear expectation on the Card's purpose.
Don't
Don't place multiple Heading components in a single Card.
Do
Use a consistent location on the bottom of the Card for primary actions or next steps.
Feedback
Help us improve this component by providing feedback, asking questions on Slack, or updating this file on GitHub.