- Issue created by @jldust
- Status changed to Needs review
about 1 year ago 10:41pm 13 November 2023 - Status changed to Needs work
about 1 year ago 10:58pm 13 November 2023 - ๐บ๐ธUnited States philip_stier Denver, Colorado
Iโm sorry @jldust, but I donโt think โTeaserโ and โCardโ should be the same thing. I also donโt think that these should be 3 separate components. Teaser should be one component with all of the different variations inside of it. Same with Cards.
- ๐บ๐ธUnited States jldust
@philip_stier I'm happy to rename them, in this case teaser already existed so that is what I based them off of. Do you have a preference on Card vs Teaser?
Regarding the structure, it is based on the structure of SDC and is the intended format of all components currently. You can view some of the demos here: https://git.drupalcode.org/project/sdc_examples/-/tree/1.x/components?re...
- ๐บ๐ธUnited States jnettik Denver, CO
My two cents after looking at the alpha4 teaser component... I will have to significantly rebuild this on every project I use it on or just avoid it entirely. It's so cover engineered and I don't know what I'd need most of it for. IMO most teasers can be one component if all we're doing is restyling a title, image, optional body, and link. I don't know why it's passing in categories and category colors (set to a random list of pre-defined options?) and tags and dates and times... We don't need this to try and predict every single possible option we may or may not need. Keep it simple and let people build on top of that. As is, this is going to cost time on projects rather than save it.
- ๐บ๐ธUnited States jldust
We are marking this closed in favor of the duplicate issue Simplify Teaser component ๐ Simplify Teaser component Needs work
- Status changed to Closed: duplicate
9 months ago 5:56pm 20 March 2024