-
Notifications
You must be signed in to change notification settings - Fork 7
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
TDS Testimonial without drop-shadow #192
Comments
@agorovyi thinks that from Dev perspective this should not be too hard to accomplish, however we need design approval. |
my team has consulted with @gkychow and he approved this design |
Hi @karlasamantha, This was reviewed by the DPA and we agree the community testimonial component can be enhanced to completely remove the card surrounding the component. If anyone wants a testimonial within a card, they can do so manually. Designer comments: go ahead with removing the card We need a designer and developer pair to work on this. When a card is neededBefore <Testimonial
testimonial={`“My office is where ever my customers are. TELUS helps me stay connected whether I'm making a sale or doing payroll.”`}
title="Dave Smith, Foreman"
additionalInfo="Pinnacle Reforestation"
/> After <Card>
<Testimonial
testimonial={`“My office is where ever my customers are. TELUS helps me stay connected whether I'm making a sale or doing payroll.”`}
title="Dave Smith, Foreman"
additionalInfo="Pinnacle Reforestation"
/>
</Card> |
hey @karlasamantha can anyone on your team make changes based on @theetrain comments: has to be designer/developer pair. |
hey @varunj90 I can work on the dev part, unfortunately my team does not have a designer. can I try pairing with Gary if he's available? |
yes @karlasamantha please connect with @gkychow if he has cycles, otherwise the core team designers can assist, let us know :) |
BREAKING CHANGE: removes card from community-testimonial component #192
See #215 |
hey @karlasamantha thanks for making a PR, in order for the code to be approved, can you send us the updated designs for this PR. all components need to be consistent both in design and code. let us know. |
Hey @varunj90 does this one work? let me know. |
can you share the design file link on sketch/invision? it will have to be reviewed by another designer as well. exactly how we are doing in code |
@varunj90 ah gotcha! I'll ask Gary to send them over. Thanks! |
Hey hey y'all! After speaking with CX and CPP (Site Builder team), the consensus is to build the TDS community component and the Site Builder component in the same manner. This will remove any confusion and disparity when working with both, as a designer, developer, and content practitioner. I'll be able to help you with the artwork for Sketch DSM library. Adding the screenshot from our discussion to confirm that the component itself does not contain padding; the parent container will have that if you so choose to use a card or not. Thank you @karlasamantha! Let's rock and roll! |
Need to confirm with CX that the testimonial should be set at 20px font size as per design in TDS component. Live example shows it displaying at 16px font size (as per Site Builder component). We want to be as consistent and have our components be 1:1 for TDS and Site Builder components where possible. Testimonial in the wild at 16px font-size: https://www.telus.com/en/about/careers (middle of page) |
@karlasamantha confirmed with CX that testimonials should align with 20px font-size for the body text. Please update both TDS community component and Site Builder component accordingly, where possible. |
@donnavitan okay, the Site Builder block is only a wrapper for TDS testimonial component, so I'll update the component and as soon as the update is released it'll update Site Builder. |
BREAKING CHANGE: removes card from community-testimonial component #192
BREAKING CHANGE: removes card from community-testimonial component #192
This has been released in testimonial 2.0.0! https://github.com/telus/tds-community/releases/tag/%40tds%2Fcommunity-testimonial%402.0.0 |
This has been released in DSM 1.0.19 |
Question statement
Recommendation
Design intent
Acceptance criteria
This section is intentionally left blank. See story writing process.
User stories
(This section is intentionally left blank. User stories and acceptance criteria go here.)
Example:
Scenario: Displaying the component
Given text is provided
Then the text is displayed as a child
And the text size matches core-text
medium
Out of scope
(This section is intentionally left blank. Features or items that were deliberately left out of scope during design intent or may be mistaken as within scope are noted here. Link to related issues if possible.)
Meta
The text was updated successfully, but these errors were encountered: