Maintenance: enable `privacy` plugin in documentation

[dreamorosi]

Summary

The MkDocs Material plugin we use in our docs has a built-in privacy plugin that does this:

The privacy plugin offers a streamlined solution for automatically self-hosting external assets. With just a single line of configuration, the plugin can automatically identify and download external assets, making GDPR compliance as effortless as it can possibly be.

Why is this needed?

We should enable it since it will improve our docs posture and privacy for our customers.

Which area does this relate to?

Other

Solution

Add the plugin to the mkdocs.yml file:

Acknowledgment

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

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[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.