You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Decided to separate out the design updates going into v2 launch.
v2 launch
Feature card sizing and layout stays the same as v1. Once content is too large for the card height, the aspect ratio will break and the card's container will expand to fit the content.
Added border style similar to card components #10072
We will add a prop to handle overflow situations (naming tbd):
When prop is set to aspect-ratio, feature card will be locked to the 2:1 aspect ratio until @sm. Content will overflow past the bottom of the feature card container.
When prop is set to flex, feature card will behave similar to v1 – card container will try adn maintain 2:1 aspect ratio and if the content would expand past that, the container would expand vertically to accommodate.
The problem
As part of the v2 updates, we are shifting
feature card – large
to a 2:1 aspect ratio for@lg
and@md
breakpointThe solution
v2 specs using v11 tokens
Updated design spec using v10 tokens
Update highlights
@lg
and@md
will use a 2:1 aspect ratio for the entire feature card@lg
and@md
, the heading type token is changed to$heading-03
@md
, the body copy type token is changed to$body-01
16px
to8px
Application/website
C4IBM.com
Business priority
Medium Priority = upcoming release but is not pressing
What time frame would this ideally be needed by (if applicable)
No response
Examples
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: