Card follows the Clay component compositional philosophy, you can compose with ClayCard's low-level components to get Clay results and adapt to your use cases, but if you just follow the specification you can use the high-level ClayCard.
This documentation focuses on how you can use ClayCard low-level components to reach unspecified use cases and how to use ClayCard high-level components.
You can only leverage the body of
Card.Body to create the white card and add more elements.
Some quick example text to build on the card title and make up the bulk of the card content.
You can use the Card in horizontal format and use the
autofit utilities to create more possibilities.
So ristretto cappuccino
Wings eu, pumpkin spice robusta.
The low-level components for ClayCard have been built thinking about how you can use the components in the composition to get close to Lexicon specifications.
For some low-level components it is necessary to pass some modifier classes in order for the component to reach the Lexicon result, this was necessary since we did not want to attach the component just for this case and the low-level components could be used more flexibly and allow you to create new possibilities.
Stevie Ray Vaughn
ClayCard's high-level components predict the major cases of the Lexicon specification:
- Cards with Images
- Card for user listing
- Card for docs listing
- Card for folder
- Card for navigation
ClayCardWithInfo you can use to create cards with images and documents.
onClick Card with icon
Pick and choose your layout...