-
Notifications
You must be signed in to change notification settings - Fork 159
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
[CTA, cardlink] Missing card link option for CTA #5740
Comments
Adding to the 4/21 Engineering Huddle meeting agenda. Revisit the next steps in the 4/22 adopter issues review meeting. |
Roberta to reach out to Jeff about management. Epic? research issue? Schedule? |
Decision will be made after the dev research is finished. (#5859 ) sprint 21-10 |
Had a discussion with @IgnacioBecerra & @photodow on
|
FYI team here's the func spec for Looks like we'd need this bug resolved soonish as |
@shixiedesign @jeffchew I have added this issue as a blocker to (#6246) Andy is working on the Feature Section, but it is 13 story points and we expect the work to move into next sprint. The code freeze for the July 7 release is June 25, the middle of sprint 21-13. I have added this issue to sprint 21-13 and added it to the June 21 engineering meeting agenda. |
@RobertaJHahn If this issue is a blocker to 6246, should someone start on it sooner since 6246 is a sprint must have. |
@shixiedesign This work has been removed as a dependency in the issue for the Feature Section component based on the discussions in the engineering stand up today. This work will be done, but staged at a later time. |
### Related Ticket(s) #6246 DDS Tickets: #6118 HC JIRA Ticket: https://jsw.ibm.com/browse/HC-1971 ### Description - This PR adds the "Feature Section" layout component/pattern that's needed in the new "Service" landing page template that will be implemented in the AEM CMS. - This component is a variant of HC's [Module 11A](https://pages.github.ibm.com/MSC-Cloud/hc_fractal/components/detail/11a--default.html) and this iteration is the first version that will be going into the MVE state of the "Service" landing page. ### Design & Functional Specs - https://github.com/carbon-design-system/carbon-for-ibm-dotcom-website/wiki/Feature-section ![component--feature-card-block-large--visual-specs--max copy](https://user-images.githubusercontent.com/1815714/121596789-ea58b600-ca0d-11eb-9789-aaa4be7e7d58.jpg) ### Changelog **New Components/Props** - `<dds-feature-section>` – this new layout component is a variant/extension of the `<dds-feature-card>`. - `<dds-feature-section-card-link>` – this component is an extension of the `<dds-card-link>` and needed because the feature section component requires a card-link with higher max-width. - `media-alignment` - a prop `(right (default) | left)` that can be passed as an attribute. **Removed** - N/A **Note** - The current implementation of the `<dds-card-link>` UI component doesn't offer CTA types such as Video, document, external, etc. The component looks to be extended from the `dds-card`, where it should be using `dds-cta-card` component. - Looks like this is a known issue (see - #5740) **Testing Instructions** - Visit the `Feature section` - `/?path=/story/components-feature-section--default` - Ensure that the component matches with the design specs for all breakpoints. <!-- React and Web Component deploy previews are enabled by default. --> <!-- To enable additional available deploy previews, apply the following --> <!-- labels for the corresponding package: --> <!-- *** "package: services": Services --> <!-- *** "package: utilities": Utilities --> <!-- *** "package: styles": Carbon Expressive --> <!-- *** "RTL": React / Web Components (RTL) --> <!-- *** "feature flag": React / Web Components (experimental) -->
HC JIRA Ticket: https://jsw.ibm.com/browse/HC-2151 The implementation of this issue will be accounted for within this PR - #6934 (comment). |
Thank you @proeung 🙏 👍 !! |
Looks like over time our CTA cards have misaligned. Misaligned between libraries, misaligned between specs, styles and intent.
Here is the problem:
In short, react and web components do not line up. React's CTA depends on Card link while Web components depends on Card. So changing card link in CSS impacts one differently than the other and impacts unwanted changes to other components. Also, Card link isn't to specs visually and functionally. Thirdly we missed a step which might have caused some of these problems, and don't account for both card and card link being used as a CTA.
Here is a small visual to see the difference. The red is where it breaks down and the problems line up.
Here is my proposal:
card link
this requires a functional spec update as well.a quick visual to help see the new dependency tree I'm proposing.
HC Developer: Putra Bonaccorsi
HC Jira Ticket: https://jsw.ibm.com/browse/HC-2151
DDS Consulting Dev: Ari
The text was updated successfully, but these errors were encountered: