Enable new mkdocs-material features

[jonaharagon]

Changes proposed in this PR:

• Enables instant link previews
• moves more translations to env variables

I'm not sure what I think about these. Give them a spin and let me know what you think.

• I have disclosed any relevant conflicts of interest in my post.
• I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project.
• I am the sole author of this work.
• I agree to the Community Code of Conduct.

[github-actions]

✅ Your preview is ready!

Name	Link
🔨 Latest commit	cf43545
😎 Preview	https://cf43545f577d--glowing-salamander-8d7127.netlify.app/

[dngray]

Taking a look at this, I'm not sure I like the preview thing. Seems like it causes a lot of clutter say when mousing over buttons on the tools page.

[redoomed1]

After a cursory test of the instant link previews, I will note that there's one case where the preview is not that useful: when hovering over the General Criteria link that is on almost every tool recommendation page.

I think that the previews for "whole page links" cover anything until the first permalink on the page, which explains the above behavior.

[jonaharagon]

We can easily make a change to make this more meaningful with this feature in mind:

[jonaharagon]

In the long term, instant link previews will be a critical component in replacing all the wikipedia links, links like those, and abbreviations in abbreviations.en.txt which aren't actually abbreviations across the website as well. For example (not in this PR, but in the future I'm looking to add an internal "privacy glossary" to provide this functionality):

[dngray]

replacing all the wikipedia links, links like those, and abbreviations in abbreviations.en.txt which aren't actually abbreviations across the website as well. For example (not in this PR, but in the future I'm looking to add an internal "privacy glossary" to provide this functionality):

Sounds like a good idea, I checked a few pages of this now and everything seems to be working great.

[privacyguides-bot]

This pull request has been mentioned on Privacy Guides. There might be relevant details there:

https://discuss.privacyguides.net/t/2024-04-08/17760/1