-
Notifications
You must be signed in to change notification settings - Fork 18
POC Card Web Component #4604
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Possible resolution:
|
Resolution: Make a POC as a base of discussion for |
@oliverschuerch refine the issue to reflect the new task of creating a POC |
POC is available here (scroll to the bottom of the cards docs to see it) The snapshots for different scenarios are here Pros and cons from what I've seen so far: Pros:
Cons:
|
Uh oh!
There was an error while loading. Please reload this page.
Originally posted by @alizedebray in #4577 (comment)
Card WebComponent POC specs
We have a lot of different but similar cord components (CSS) which could be simplified, by just implementing one web-component, which is then also able to handle (for example) adding a link delegator on the card if necessary.
Proposal
Add a card web-component, which combines our current CSS components
card
,card-button
,card-product
andcard-teaser
into a single component with props to manage how it should look and/or work.Variant
Card
.card-title
,.card-subtitle
,.card-text
,.card-links
, etc. can be used on slotted elements.Variant
card-product
post-card-section
) to offer a proper way to add more card-bodies).Variant
card-teaser
The text was updated successfully, but these errors were encountered: