[card] redefine interface

[yinonov]

is a visual container without semantics typically used in a group to present collections of related information.
Vivid care about having a single look & feel and introduces an opinionated characteristics to card.
still, there are often cases where authors need to deviate from that authored characteristics. therefore we'd like to introduce a solution for more than 1 type of use.

adopting stacking slots approach to wrap the opinionated layout with slots and enable authors the ability to allow any content in card

[rachelbt]

a long time ago we discussed the slot names in the card and meta was suggested by you for the footer of the card.
The "circle" slot was supposed to be action / top action:
https://docs.google.com/document/d/1FLMPYki_qo0YBvXvAI_DPsM4yBqn_bLSWiDfA0fiwHs/edit

[yinonov]

think of this in comparison to a dialog. what should be the API?

[yinonov]

@jshenkman does card respect all elevation dps? or only answers to a single value?
if so, note that this redefined approach makes elevation API redundant as same UI can be easily achieved by card

[rachelbt]

when rethinking about the card areas we should also take in mind its spacing.
When theres more than one card in a row - I guess that we would like the footer/action to be aligned to the bottom like this:

and not this (the state currently):

[yinonov]

when rethinking about the card areas we should also take in mind its spacing. When theres more than one card in a row - I guess that we would like the footer/action to be aligned to the bottom like this:

and not this (the state currently):

right, can occur on grids. good one

[yinonov]

include #1135

[jshenkman]

@jshenkman does card respect all elevation dps? or only answers to a single value? if so, note that this redefined approach makes elevation API redundant as same UI can be easily achieved by card

Card needs to have at least a few elevation values, but not necessarily all of them.
Some examples for this would be -

1. Cards with elevation 0dp so they can have a flat style design with no elevation and only outline
2. Cards with a default elevation of 8dp
3. Card with changing elevation to represent hover state, for example, 8dp to 16dp or 0dp to 12dp

If you want some visual examples lmk @rachelbt :)

[jshenkman]

Another requirement that was brought up by designers is supporting a few text styles in the title/header.
Currently, we support one style - Subtitle-2. It would be helpful to allow some more text styles specifically body-1-bold and subtitle-1.

A similar implementation can be seen in Spectrum by Adobe

[rachelbt]

Another requirement that was brought up by designers is supporting a few text styles in the title/header. Currently, we support one style - Subtitle-2. It would be helpful to allow some more text styles specifically body-1-bold and subtitle-1.

A similar implementation can be seen in Spectrum by Adobe

@yinonov are we going to support this or we will leave default slot fo the variations?

[yinonov]

Spectrum apply the same practice of slotted content overriding