Skip to content
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

feat(leadspace): add leadspace brand logo style #309

Merged
merged 11 commits into from
Aug 10, 2023

Conversation

nimithshetty17
Copy link

Issue

Fixes #MERATIVE-776

Description

We have a "Leadspace" block created in Franklin, however, we need to add a variation where the brand logo can be inserted into the block table within the Sharepoint docs.

New

image

Design Specs

If applicable, add the direct link to the design specs of the component/feature that's part of this PR.

Test URLs

Testing Instruction

To test the leadspace with brand logo and its responsiveness with respect to the design across all devices.

@aem-code-sync
Copy link

aem-code-sync bot commented Aug 3, 2023

Hello, I'm Franklin Bot and I will run some test suites that validate the page speed.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-run PSI Checks

@aem-code-sync
Copy link

aem-code-sync bot commented Aug 3, 2023

Page Scores Audits Google
/block-library/blocks/leadspace PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

Copy link

@sachinmesh sachinmesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked only the product logo leadspace. Let me know, if other leadspace are also needs to be checked.

  1. On desktop, the height should be 55px for product logos
image

mobile and tablet the height should be 45px for the product logos

image

@nimithshetty17 @proeung @keith-kaplan

@aem-code-sync
Copy link

aem-code-sync bot commented Aug 3, 2023

Page Scores Audits Google
/block-library/blocks/leadspace PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

@nimithshetty17
Copy link
Author

@sachinmesh - Please have a look now.

Copy link

@sharathmrft sharathmrft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nimithshetty17
1.Video player is not playing the video
image

  1. There is variations in the Buttons size
    image

@sachinmesh
Copy link

sachinmesh commented Aug 3, 2023

HI @nimithshetty17
The primary CTA missing the arrow style. Rest is good to go.

image

@nimithshetty17
Copy link
Author

@sachinmesh - Arrow is added as well.

Copy link

@sachinmesh sachinmesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is good to go now, as the arrow is also added in the primary CTA of the product specific leadspace.
image

@proeung @nimithshetty17 @keith-kaplan @sharathmrft

Copy link

@proeung proeung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, however I'm seeing some design issues.

  • The line-height of the inline link/tertiary button is off.
  • The arrow icon within the primary button is too big. It should be 24px by 24px.

Screenshot 2023-08-03 at 2 33 40 PM

@aem-code-sync
Copy link

aem-code-sync bot commented Aug 4, 2023

Page Scores Audits Google
/block-library/blocks/leadspace PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

@nimithshetty17
Copy link
Author

@proeung - Updated all the changes requested. Please let me know if there are any concerns.

@aem-code-sync
Copy link

aem-code-sync bot commented Aug 4, 2023

Page Scores Audits Google
/block-library/blocks/leadspace PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

Copy link

@proeung proeung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nimithshetty17 Your latest changes looks good, but I noticed that you were using a new arrow icon (arrow-right.svg) in the button. Just wanted to note that we already have an arrow icon SVG within the /icons directory within this repo (https://github.com/hlxsites/merative2/blob/main/icons/arrow.svg?short_path=f27ac62) and there's no need to upload a separate version.

Sharepoint format for primary button: Speak to sales:arrow:

Things to change/clean up:

  • Remove this duplicate arrow SVG that you've uploaded (see link ).
  • Push up a commit to adjust the existing arrow.svg code to use the following SVG code with the proper viewBox value of 24x24px for consistent scaling.

Screenshot 2023-08-04 at 11 59 45 AM

<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
<path d="M3.75 12.6152H20.25" stroke="white" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
<path d="M13.5 5.86523L20.25 12.6152L13.5 19.3652" stroke="white" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
</svg>

Once, these changes are in, we can mark this PR as ready for merge.

cc: @keith-kaplan

@aem-code-sync
Copy link

aem-code-sync bot commented Aug 7, 2023

Page Scores Audits Google
/block-library/blocks/leadspace PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

@nimithshetty17
Copy link
Author

@proeung - I have committed the changes for the arrow icon. Please let me know if there are any concerns.

Copy link

@proeung proeung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nimithshetty17 LGTM!

This PR is blocked from being merged until @sharathmrft has reviewed and approved it.

@sharathmrft
Copy link

@nimithshetty17 @proeung
A small observation underline is thick in tab and mobile for Inline/Tertiary link as shown below rest is good to go.

image

@Shalini-SB @keith-kaplan

@sachinmesh sachinmesh added the Ready to merge Label for the pull requests that are ready to merge label Aug 9, 2023
@proeung proeung removed the Ready to merge Label for the pull requests that are ready to merge label Aug 9, 2023
@aem-code-sync
Copy link

aem-code-sync bot commented Aug 9, 2023

Page Scores Audits Google
/block-library/blocks/leadspace PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

Copy link

@proeung proeung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sharathmrft Thanks for the review. Yeah, I noticed the odd line height issue for the tertiary link on the mobile breakpoint as well. @nimithshetty17 Can you fix this?

@aem-code-sync
Copy link

aem-code-sync bot commented Aug 10, 2023

Page Scores Audits Google
/block-library/blocks/leadspace PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

@aem-code-sync
Copy link

aem-code-sync bot commented Aug 10, 2023

Page Scores Audits Google
/block-library/blocks/leadspace PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

@nimithshetty17
Copy link
Author

@sharathmrft - Please review this now.

@aem-code-sync
Copy link

aem-code-sync bot commented Aug 10, 2023

Page Scores Audits Google
/block-library/blocks/leadspace PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

Copy link

@proeung proeung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nimithshetty17 Looks like you've added different line height values to the tertiary link for mobile (line-height-160) and desktop (line-height-120), which is incorrect.

I went a head and push up a commit (20d2f12) to fix and clean up the format of the code. Tertiary link line height is looking inconsistent on all breakpoints now. I'm going to mark and merge this PR down.

Screenshot 2023-08-10 at 9 38 43 AM
Screenshot 2023-08-10 at 9 38 52 AM

@proeung proeung merged commit f4ea97e into hlxsites:main Aug 10, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants