From f2bd58f73b12564b7b0424fe22aa51bdc77dd00c Mon Sep 17 00:00:00 2001 From: bt Date: Tue, 28 Nov 2023 13:42:29 -0500 Subject: --- posts/webfonts.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'posts') diff --git a/posts/webfonts.md b/posts/webfonts.md index 4f69c0d..120c54b 100644 --- a/posts/webfonts.md +++ b/posts/webfonts.md @@ -1,6 +1,5 @@ -# Stop Using Custom Web Fonts - -2023-03-14 +[[!meta title="Stop Using Custom Web Fonts"]] +[[!meta date="2023-03-14"]] I recently read an excellent post by Manu Moreale titled [A rant on web font licenses](https://manuelmoreale.com/a-rant-on-web-font-licenses). I highly recommend you give it a read (it's relatively short) since Manu makes a solid argument against existing font licenses. After reading, I found myself thinking about it throughout the rest of the day. @@ -32,4 +31,4 @@ A lot of designers I've worked with or talked to in the past tend to be big supp It might be small in the grand scheme of things, but having an extra HTTP request (or more) for your custom fonts and requiring your users to consume more bandwidth on their end is not "eco". As designers we should cut the fat and reduce software bloat in the small areas that we're able to: the front end. -My hope is that even one designer reading this decides to rollout a web app or marketing page without dumping a bunch of custom fonts on their users. It's just the *nice* thing to do. \ No newline at end of file +My hope is that even one designer reading this decides to rollout a web app or marketing page without dumping a bunch of custom fonts on their users. It's just the *nice* thing to do. -- cgit v1.2.3-54-g00ecf