-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
🌸 DesignLibrary
: CardComponent
#2110
Comments
zspencer
added a commit
that referenced
this issue
Jan 11, 2024
- #2110 This is perhaps unnecessary; since `<header>` tags are easy to write; but maybe it's actually useful?
zspencer
added a commit
that referenced
this issue
Jan 14, 2024
- #2110 This is perhaps unnecessary; since `<header>` tags are easy to write; but maybe it's actually useful?
zspencer
added a commit
that referenced
this issue
Jan 21, 2024
* ✨`CardComponent`: Has a Header Slot - #2110 This is perhaps unnecessary; since `<header>` tags are easy to write; but maybe it's actually useful? * 🌸🧹 `CardComponent`: Gray the Footer, pull Classes into HTML * 🧹 `CardComponent`: Headers have a default style OK so TIL about [ViewComponent Lambda Slots](https://viewcomponent.org/guide/slots.html#lambda-slots), which seem like a decent way for paramaterizing headers and footers. overridden. There are variants for the Header and Footer, which seems nice It could be good to update the ComponentPreview as well...
zspencer
added a commit
that referenced
this issue
Jan 25, 2024
- #2110 If we enforce a gap at the card level, it makes it hard to format things nicely in contexts where there should not be a gap between the header and footer. The `justify-between` is "enough" to ensure that the footer sticks to the bottom of the card, and the `header` and `footer` both provide padding. So no need to set that intention + enforce it multiple places; and this place seemed like the one that was least tailorable to the immediate usage context.
zspencer
added a commit
that referenced
this issue
Jan 25, 2024
- #2110 If we enforce a gap at the card level, it makes it hard to format things nicely in contexts where there should not be a gap between the header and footer. The `justify-between` is "enough" to ensure that the footer sticks to the bottom of the card, and the `header` and `footer` both provide padding. So no need to set that intention + enforce it multiple places; and this place seemed like the one that was least tailorable to the immediate usage context.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
DesignLibrary
#1187 has a 🌸DesignLibrary
:CardComponent
#2110, right?The text was updated successfully, but these errors were encountered: