In June 2022, WordPress.org’s Themes Workforce started strongly urging theme authors to switch to locally hosted webfonts, following a German court docket case, which fined a website owner for violating the GDPR by using Google-hosted webfonts. For years, theme authors have been enqueuing Google Fonts from the Google CDN for higher efficiency, however this technique exposes guests’ IP addresses.
The Themes Workforce warned that pointers concerning domestically internet hosting fonts can be altering imminently and lots of theme authors moved to comply earlier than it turns into a requirement.
A ticket for bundling Google fonts with WordPress’ legacy default themes had patches and was on observe to be included in WordPress 6.1 in November. WordPress contributor Hendrik Luehrsen requested extra eyes on the ticket, saying it “instantly impacts the core WordPress viewers in Germany.” He reported that customers in Germany have been nonetheless getting emails threatening fines for utilizing fonts loaded from Google.
WordPress core committer Tonya Mork suggested exploring releasing the up to date model of every theme individually from WordPress 6.1.
“When every theme is prepared, launch it to wp.org’s theme repo,” Mork mentioned. “Customers can then replace to get domestically hosted fonts forward of when WP 6.1 is launched.”
This modified the course of the ticket and with extra scrutiny, contributors discovered the patches might use some extra work.
“Creating new theme variations for this particular change could possibly be good when they’re prepared,” Stephen Bernhardt mentioned. “Using locally hosted fonts is already advisable, however we have to repair our personal themes earlier than we are able to make this a requirement for others.” He submitted an inventory of issues and potential enhancements after reviewing the patches, and contributors are engaged on a greater method.
WordPress core committer David Baumwald changed the milestone to 6.2, as Beta 2 for six.1 was launched yesterday and the ticket nonetheless wants a last course and patch.
“Whereas I perceive the problem, that is nonetheless unhappy to see,” Luehrsen mentioned. “That is nonetheless a critical challenge in Germany (and different GDPR territories), as customers with lively Google Fonts are at present getting targeted by people exploiting the law.”
Luehrsen took to Twitter to comment on his disappointment with the ticket lacking the window for six.1.
“That is the rationale why WordPress will in all probability lose relevance,” he mentioned. “Actual customers get harm right here, however they’re in GDPR territories and this doesn’t appear to be vital.
“Might I’ve achieved extra? In all probability. However it’s considerably unhappy to see how rapidly the momentum on that ticket fizzled out. If Squarespace, Wix and types begin advertising privateness towards WordPress, we’re screwed in GDPR nations.”
Customers also can change to Bunny Fonts, an open-source, privacy-first internet font platform with no monitoring or logging that’s absolutely GDPR compliant. Bunny Fonts is suitable with the Google Fonts CSS v1 API so it will probably perform as a drop-in substitute. The Replace Google Fonts with Bunny Fonts plugin makes it simple for customers to try this with out enhancing any theme code.
Contributors are engaged on having absolutely GDPR-compliant WordPress default themes prepared for WordPress 6.2, anticipated in early 2023.