Avatar component vs. Image variant #1732
Replies: 2 comments
-
For me it would make sense to have a component and enforce the consistency of this element which I believe it's widely used in our Products. Correct me If I'm wrong, but using an image component, it would force the developers to aply some css to a square image to make if round for example. There is nothing wrong for the developers writing css, but everytime they do, they can go off-rails. I'd like to have a component like the one I've seen in Ant, Atlassian or Goldman Sachs:
I don't think we need too many variants, just the square and the round, with different sizes and also being able to configure a Text (couple of letters), an icon or an image. Also, it would allow us to think about nice patterns like these ones: But I'm not sure. I've always heard that Halstack is not too opinionated, which means that we should allow some level of freedom in our designs.. |
Beta Was this translation helpful? Give feedback.
-
I think that creating a dedicated new A dedicated |
Beta Was this translation helpful? Give feedback.
-
As we explore the possibility of adding a new component and leveraging the actual presence of Avatar-like elements in our products, we are contemplating the best method to integrate this asset in Halstack. So far, we have screened two possible options:
Beta Was this translation helpful? Give feedback.
All reactions