Card content is the same on mobile and desktop, just on mobile the cards wrap the content and don’t have a set height. If you have multiple featured tags on the same topic, cards will show the tag that is shown first on the default tag list. I believe this is by alphabetical order.
Regards trending topics, you can pick the list algorithm just as on the Featured Tiles component. Right now these algorithms include latest and various top selections:
How would trending be different from top-daily or top-weekly? In any case, when there’s a new sorting and filter algorithm in Discourse core, as the “hot” one mentioned, it should work on the component as well.
This component is just showing one row of cards on desktop. And as many cards as you like in one column on mobile (there’s a maximum topic count setting).
Showing more rows on desktop is easily possible if you write custom CSS for the component. But that’s not a use case I will support with the component as such, as I believe it will need a custom layout anyways.
Okay I see… you just made me change my wording I’ve written feed twice, but I changed it to column. The goal of this component is to feature specific selected topics. I don’t doubt you could also make it work more like a dynamic feed. But if that’s your goal, I’d rather just style the existing list views to get there. You know, just use a component like Topic List Previews or Topic List Thumbnails and style the list items more like cards. Working directly on the lists is all integrated with navigational elements and filters on Discourse. You won’t get that with this component.
What’d be great is, if you could have a “pinned” featured topic (i.e. the “Welcome to this Forum” topic), that is always shown, even if topics are randomly chosen from #featured. I think that would be really awesome, not just for my use case but also many others. Could that be implemented?
Thanks for the suggestion @diabolicvincent! Though I guess I won’t implement this as a feature. One reason is that (as mentioned on the credits), I didn’t program the logic of this component. It’s quite complex already for my taste and I don’t want to mess with it myself.
More generally, philosophically, conceptually… I actually believe it’s better ui design when official content is easily distinguishable from user-generated one. In that regard I’m already not a fan of pinning topics within an otherwise dynamic list of user topics.