Not GDPR compliant out of the box

[mixonic]

Addon docs uses Google fonts via

ember-cli-addon-docs/index.js

Line 227 in b330f9a

return `<link href="https://fonts.googleapis.com/css?family=Crimson+Text:400,600" rel="stylesheet">`;

As Google may use their fonts service to analyze user behavior (at the least gathering IP addresses), and there is no clear way for a user to opt-out, addon docs websites may not be GDPR compliant out of the box.

This could be resolved by having the site serve the font asset, not using a custom font at all, or by finding a GDPR compliant font hosting service.

At the least, a documented workaround should be available.

[mixonic]

@SergeAstapov @RobbieTheWagner @miguelcobain I'm happy to solve this any of a few ways if you can give me a rough approval for what you think reasonable. Options available seem like:

1. Add a build-time configuration that allows users to disable the font link. Add this to the docs. (requires a minor release)
2. Change the default fonts to be appropriate system serif/sans fonts, and describe in the docs how to set a custom font. (would be a major release)
3. Download and check the font into the assets of the theme so they come from the same domain instead of Google. (requires a minor release)

[RobbieTheWagner]

@mixonic addon docs is mostly unmaintained now, since it won't work with v2 addons, embroider, or fastboot. If anyone wants to put in some time to help with those things, I would love to keep it going, but as of right now, there isn't really a path forward.

[mixonic]

@RobbieTheWagner I'll keep that in mind, but I'd still love to address this issue upstream instead of forking for it. I'll take your vote as "do the least effort thing unless you are fixing one of these other three issues as well".

[RobbieTheWagner]

Yeah, that's an accurate assessment. I'm fine with any fix.