auro-hyperlink: CTA size

[braven112]

Is your feature request related to a problem? Please describe.

Buttons and Hyperlink CTA's are different sizes and we would like to standardize these so that implmenters can use them as needed without having to customize them or get frustrated when having them side by side.

Describe the solution you'd like

Reduce the size of the hyperlink CTA to match the size of auro-button

Describe alternatives you've considered

Each time these are implemented the implementer could resize the hyperlink CTA with CSS

Additional context

Overall goal is to make buttons and hyperlink CTA's follow the same design patterns so implementers can use the appropriate component, use them together without any extra work.

Blueprint: https://www.figma.com/file/TSFOFDwWQxmpPpYQ2F06lH/Hyperlink?type=design&node-id=2233-2573&mode=design&t=Q8oscXA2ktquOAo9-0

Exit criteria

Hyperlink CTA matches the size of auro-button.

[blackfalcon]

Buttons and Hyperlink CTA's are different sizes and we would like to standardize these so that implmenters can use them as needed without having to customize them or get frustrated when having them side by side.

The size difference is intentional, not accidental.

Here is an article that supports what was decided https://www.isoftstoneinc.com/insights/call-to-action-links-are-not-buttons/

This really isn’t a question of how to identify your CTAs as links, but how to differentiate your CTAs from your buttons. A call to action needs to stand out, but it also needs to look different than buttons do.

[blackfalcon]

I would argue that what is missing is a sizing option of the CTA, not simply making the CTA look exactly like the form button.

[braven112]

Yeah we want both.

• We are looking to standardize the size so that they can be used next to each other if needed. Designers don't want them to look visually different by default but I understand why it was done that way originally.

• The traditional marketing "CTA" should also be customizable as you are suggesting. If we implement this with a semantic token name defined in the root the implementer can create any size CTA they want by overriding this token per marketing placement.

[leeejune]

The small CTA button also does not match the exact specs on the blueprint nor does it match the slim version of auro-button.