fix(design-qa): Fix spacing issues within Content Intro & minor bugs seen within Microsite

[proeung]

Issue

Fixes - https://jira.sdlc.merative.com/browse/MERATIVE-887

Description

Changed

• This PR addresses multiple spacing issues seen when certain bands/patterns are stacked. See the ticket (https://jira.sdlc.merative.com/browse/MERATIVE-887) for more details.
• Also, this PR fixes minor FE display issues when the list item within the Content Intro block goes into two lines.

Design Specs

• Figma Link -

Test URLs for spacing issues

• Before (Changes from main): https://main--merative2--hlxsites.hlx.page/curam
• After (Changes from this PR): https://fix-space-qa-887--merative2--proeung.hlx.page/curam

Test URLs for FE bugs seen in Microsite Missouri Landing

• Before (Changes from main): https://main--merative2--hlxsites.hlx.page/campaigns/curam/missouri
• After (Changes from this PR): https://fix-space-qa-887--merative2--proeung.hlx.page/campaigns/curam/missouri

Testing Instruction

• Take a look at the issues outlined in this ticket (https://jira.sdlc.merative.com/browse/MERATIVE-887) and ensure that those things are addressed.

[aem-code-sync[bot]]

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[bot]]

Page	Scores	Audits	Google
/campaigns/curam/missouri
/curam

[keith-kaplan]

@proeung this is looking great. A question for content entry on this page. https://fix-space-qa-887--merative2--proeung.hlx.page/curam (https://main--merative2--hlxsites.hlx.page/curam)

Should the content checkmarks section metadata still be there as it's own section? it looks like the spacing is working fine, but wanted to ensure the content entry didn't need to be one section.

[proeung]

Should the content checkmarks section metadata still be there as it's own section? it looks like the spacing is working fine, but wanted to ensure the content entry didn't need to be one section.

@keith-kaplan It should be in the same section. I forgot to move the stat into the same section as the Content Intro that has the checkmarks. Feel free to change this.

[proeung]

@sachinmesh Which section are you referring to for "We can reduce this padding to 96px instead of 160px."? The screenshot that you've provided doesn't look correct.

This component is breaking

This is an issue that's not scoped to this PR and will be handled in a separate ticket.

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/campaigns/curam/missouri
/curam

[sachinmesh]

This padding @proeung between the title and the first simple component.

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/campaigns/curam/missouri
/curam

[proeung]

@sachinmesh I just pushed a commit that should address your feedback about the spacing. Can you take a look again?

[sachinmesh]

This is good to go. Just one thing if we can update the title here to H1 instead of H2, as there is no H1 title on the page. @proeung @keith-kaplan

[proeung]

@sachinmesh Thanks for the review! Regarding your question, I think we should keep with the <h2> tag and styling from the DS instead of trying to mimic the style/specs of <h1> for this particular case. This will keep the heading size consistent per section and not create a one-off case in our stylesheet to keep with the page DOM structure and SEO. @keith-kaplan Let me know if you agree.