Maintenance: Add nofollow & noopener to external links

[sthulb]

Why is this needed?

It's possible that Google and other search engines have given aws.dev special status. Malicious actors could use this to raise the profile of their SEO standing.

Which area does this relate to?

Other

Solution

To combat any potential for this being an issue, we should add rel="nofollow noopener" to external links.

• https://www.semrush.com/blog/nofollow-links/
• https://www.elegantthemes.com/blog/wordpress/rel-noopener-noreferrer-nofollow#noopener

Acknowledgment

• This request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[heitorlessa]

good catch! It's a good candidate to create our first markdownlint custom rule - we'll surely miss this eventually

[leandrodamascena]

When I was working on issue #2260 I spent time researching this and it may not be necessary to add the nofollow attribute as it is automatically added by newer browsers.

References:
https://chromestatus.com/feature/6140064063029248
https://bugs.chromium.org/p/chromium/issues/detail?id=898942
https://bugs.webkit.org/show_bug.cgi?id=155166
https://bugzilla.mozilla.org/show_bug.cgi?id=1222516

[sthulb]

Cool, we can drop noopener then and just add nofollow which is observed by search engines

[leandrodamascena]

Nice @sthulb! Can you send the PR or do we wait a bit and do it next week? Just let me know.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under 2.23.0 version!