-
Notifications
You must be signed in to change notification settings - Fork 156
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
[Card] Allow text link on Card in all situations #7631
Comments
Hi @GeoPei! The design team reached out to your original question in slack, I've copied @shixiedesign's response here:
Closing this ticket based on the comment from @shixiedesign, but if you feel you have a use case feel free to reopen this ticket and add details. |
Thanks @annawen1 for pulling in my response from Slack and @GeoPei, we have been discussing this internally again, and we realize what you @GeoPei are trying to do (heading + copy + CTA text) is necessary for UX, esp. when people skip reading the copy, and people often do. We were more worried about 4 types of texts (heading + copy + CTA text + eyebrow). So considering this requested feature makes a good design, I think we will proceed to allow CTA text, so reopening this issue. I will capture the recommendation of using only up to 3 types of text in the usage guidance webpage for Cards. |
convert to an epic, func specs update, WC and pure React dev, QA and website, no e2e test update schedule the React dev before WC |
The problem
Hi team
My client hopes to add link text to the link of each card in the card group component, but we found that there is no component that can be used, could you please help to update the component?
Thank you.
The solution
we want to add the link text on the card group component, now we just add title, description, link.
Application/website
https://www.ibm.com/strategic-partnerships/fr-fr/ois/
Business priority
High Priority = pressing release
What time frame would this ideally be needed by (if applicable)
No response
Examples
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: