copy update: /aws/fips

[andesol]

QA

• Compare with copy doc

Issue

https://warthogs.atlassian.net/browse/WD-18368

[webteam-app]

Demo

Jenkins

demos.haus

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.32%. Comparing base (c4540a6) to head (3310663).
Report is 24 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #14675   +/-   ##
=======================================
  Coverage   72.32%   72.32%           
=======================================
  Files         120      120           
  Lines        3404     3404           
  Branches     1172     1174    +2     
=======================================
  Hits         2462     2462           
  Misses        917      917           
  Partials       25       25           

[andesol]

@eliman11 (Not sure whether you can have a look at this, let me know if not)

This is the current layout for the cta block:

The requirement is to add two new links for the newest ubuntu LTS, one for ARM64, one for Graviton (see copy doc), while keeping the old links. Problem is: this doesn't seem to work with the space available in the current layout, where all the links are in one line.

This is my proposal to move the secondary links to a new line:

But it looks a bit off to me... Do you have any suggestion about how to handle this?

[eliman11]

@andesol Thanks for flagging! I agree - we usually try to limit hero sections to just 3 CTAs. I've asked a question to the stakeholder on the copydoc to just have those first two CTAs since the other links are repeated further down the page. Will try to figure out a workaround if not.

[eliman11]

Just received feedback from the stakeholder - they're happy to only have the most recent LTS in the hero and deleting the other links. I'd suggest using the secondary button in that case like in the screenshot below. Thanks!

[mtruj013]

Thanks @andesol, a few minor comments:

[andesol]

@mtruj013 Thanks for your thorough review! I think I fixed it. Please have another look when you have time.

[mtruj013]

Thanks @andesol! LGTM, pending one minor change: