I love this podcast. My only complaint is that it’s newish and I sped through every episode and now I want more.
As someone who spent years working in bookstores and libraries, biting my tongue while selling and lending so many terrible, terrible books, these takedowns are extremely validating.
I don’t download a ton of script fonts but I’m really into Party Attack by NihStudio, maybe because it has a bolder, blockier feel than most. While you’re downloading, don’t miss their gallery of sample usages in menus, invitations, and more. Free for personal use only.
How to Publish an Updated Version of an npm Package – Cloud Four - I’ve used different tools to automate releases in the past but had no idea what they were doing under the hood. This article walks through creating a release and publishing to npm and Git with detailed explanations at every step. It’s a great starting point since understanding the manual process makes evaluating different automated strategies a lot easier.
Release Workflow | Yarn - Package Manager - Yarn’s release workflow for monorepos is an experimental feature so I’m holding off for now but I hope it pans out. The section on deferred versioning and record keeping is especially intriguing.
Tools! Trying to figure out which of these options would best serve my needs:
Auto - Intuit - Automates releases based on pull request labels. I used this at a previous job and appreciated that it didn’t require linting commit messages or any extra effort from contributors. The downside, Lerna is a must for use with monorepos.
Release It! - This seems promising. A CLI tool that can be used in interactive or continuous integration mode. The big appeal for me is a Yarn workspaces specific plugin.
Finally, recommendations are welcome so here’s my brief. I want to combine multiple packages that currently live in separate repos into a single monorepo using Yarn workspaces. Ideally, I’d like to independently version the packages without adding Lerna and use GitHub Actions for CI/CD. If you have a similar setup, let me know what’s worked for you.
Okay. It’s 2023. I just copied all the font release Tweets I’ve ever bookmarked on Twitter just in case that feature suddenly disappears. Let’s recommend some downloads.
Liquidie by Forberas is a fluid, hand drawn font. It’s free for personal use only and includes upper and lower case characters.
This is a great parallax option. Had to set it up on a Wordpress site and it was so easy to use.
These first Friday font recommendations are increasingly any day of the week and exclusively sixties inspired font recommendations. In keeping with that, it’s a perfect Wednesday for downloading Groovy Daisy by Jimtype Studio. It’s free for personal use only and is, indeed, very groovy.
Next.js and Tumblr as a CMS Part 4: Open Graph Images
Way back in my first post on using Next.js with Tumblr, I mentioned getting more control over my blog as one of the big motivations for the switch. So, I thought I’d wrap up by going over a couple of the specific things I meant by that: generating Open Graph images and adding syntax highlight to code blocks.
This was originally intended as one post but it got a little long and I’m a little slow so I’ll start with Open Graph images.
Open Graph images are the preview images you’ve probably seen when sharing a link on a social media site like Twitter or Facebook. By default, Tumblr will display a generic image with the Tumblr logo and some themes might pull in your avatar or let you upload a custom image. However, there isn’t a good way to attach different images to different posts or to dynamically generate them. My goal was for each of my posts to have a unique, text-based image displaying its title or description and type.
There are a lot of good articles on the topic but their instructions didn’t get me exactly what I wanted so I wound up picking and choosing to cobble my solution together. Dynamic Open Graph images with Next.js was so close but it uses next-api-og-image which uses chrome-aws-lambda under the hood and I couldn’t get it to work on Vercel. I even tried the suggestion to install an older version of chrome-aws-lambda but it just wouldn’t deploy. Generate Open Graph images for your static Next.js site generated images during the build process instead of on the fly but it introduced using Playwright which was invaluable. Those two articles were big influences on the code below.
Start by installing the necessary playwright packages:
Two things to note: 1) for convenience, I store my base URL as an environmental variable so you’ll probable need to replace NEXT_PUBLIC_BASE_URL and 2) we’ll be using query params to pass the post headline and type.
The content URL points to a route we’ll create in pages/api/og-image.js. I’ve truncated a lot of the HTML and CSS since those will depend on how you want your image to look:
Now, if you visit that URL while developing locally, you should see an HTML page so you can inspect and tweak your designs. In production, Playwright will launch a headless browser, open a new page and insert your HTML, and then take and return a PNG screenshot.
And that’s how I set up my Open Graph images. Next time I’ll actually finish the series with syntax highlighting for code blocks.
A couple days late but Hello Margarine by Prioritype Co is a fun font. Maybe I’m in a real sixties mood lately but I’m loving the groovy, bell-bottoms-y style. And it comes in regular, outline, and shadow varieties. Free for personal use only.