Notable changes in my life, on my website, and in other projects.
I wrapped up the first project of the next iteration on the site! This was mostly behind-the-scenes changes that sets me up to be able to make changes that will be meaningful to you.
Progress on the current project has been slow so far, partially because I took a week off to bounce around a few cabins in Michigan (US) with my family. Now that I'm back at it, I'm working on some improvements to individual posts before beginning to introduce new types of content on the site.
I'm anxious to share these updates with you!
New blog posts and videos I published last month.
Creating and saving images with node-canvas was a really fun one to put together for LogRocket. When I write pieces like this, I work to stay focused on the goal at hand. But I always want to say more. Sometimes to add background or introductory information, and other times to explore next steps. Here I did both and published the following related articles on my blog:
The Next Evolution of Stackbit kicked off a series of posts for Stackbit in which I got introspective on what Stackbit is and where we're going. But I think my favorite piece of the month for Stackbit was What Made the Essence of Jamstack Possible, which was born while exploring The Missing Piece of the Jamstack. The types of articles get to the core of why Stackbit exists and what drew me to the product.
100 Free CSS Resources is the fourth of five guest articles from Pratham published on the blog. The final will likely emerge in November.
Articles and news I read last month that I found interesting, with some commentary.
It was fun to play a role in Dom's piece on 11 Considerations for the Future of Jamstack Web Development. It helped me think about where we've come from and where we're going with web development. It's likely to spark several related articles from me in the coming months. Rest assured, 2022 is going to be a fascinating year in the evolution of web dev. Of course, I couldn't have responded to all these questions without mentioning Astro or Slinkity, and I'm glad Bryan picked up on it!
(Speaking of Slinkity) Building The SSG I've Always Wanted: An 11ty, Vite And JAM Sandwich was probably the best thing I read this month. It's essentially the birth story of Slinkity. But it does such a great job walking through that journey that it brings to life not just the case for Slinkity, but why we're seeing this trend of component-based SSGs that ship less JS to the client (like Astro). It's long, but it is absolutely worth a read. This stuff is going to be the talk of the town for the near future.
Tweets like this one from Jaon Lengstorf are showing a compelling reason to look more seriously into low-JS tools. Many folks are playing around with these solutions that ship less JS to the clients and seeing major performance benefits. It doesn't mean it's a silver bullet, but it's shifting the conversation, and that's important.
What's New in Gatsby 4 marks the official public release of Gatsby 4! We saw Gatsby lose a large market share to Next.js throughout 2020. I can't wait to see if this release is what they needed to pull some developers who left for Next.js (like me) back into the mix.
Remix announced a $3 million seed round, which also seems promising in building the competition with Next and Gatsby in this space — React-based front-end frameworks. I don't know much about Remix, but this news has been hyped quite a bit, so I'm interested to see where it goes.
Serverless introduced Serverless Cloud Public Preview. It's been years since I used Serverless directly. At that time it was a much better alternative than using AWS Lambda directly. But since then services like Netlify Functions have gotten so easy to use, I haven't gone back to Serverless. I wonder if we'll hear more from the community in using Serverless following this announcement.
Write 5x more but write 5x less is advice that speaks to me. It says: "The average person should write 5x more things than they do. The average written thing should be 5x shorter than it is." I love this advice and have been trying to keep it in mind since coming across it this month.
6 Concrete Tips That Will Make Your React Pull Requests Easier To Review is super useful if you are new to creating creating or reviewing pull requests, or if you feel like it's not a super productive process on your team.
Proposal for CSS @when from Chris Coyier led me down a rabbit hole with CSS this month — a topic with which I don't often spend much time these days. It is a good summary, but the GitHub discussion is almost more valuable of a read. It has some great insight into thinking through naming conventions when setting standards.
The Future of CSS: Cascade Layers (CSS @layer) is a proposal that could fundamentally change the way we write CSS today. Cascading may not work exactly the same thing in a few years.
Less Absolute Positioning With Modern CSS is a clever trick to getting around absolute positioning. When it seems like we should be out of innovations in CSS, something new comes along.
Twitter conversation from Jeff Escalante that has a slew of great Next.js plugins.
Is Deno Still a Thing? A Look at the Status of the Node Killer
New tools that I've recently discovered. They aren't necessarily new.
Heroicons are beautiful hand-crafted SVG icons,by the makers of Tailwind CSS.
unDraw Illustrations are open source and free to use. I love that people provide this great work to the community for free. I hope that you'll avoid putting meaningless illustrations on your website like everyone else.
Canva is a design tool that has apparently been around for awhile, but I just came across it this month.
Projector is also a design/presentation too, but seems to be more focused on collaboration.
Beau is a tool to help build no-code workflows for your clients. I didn't totally understand the use case, but they have so nicely outlined a handful of possible use cases on their home page.
Motion One is a simple animation library, supposedly faster because it is built on top of the Web Animations API. I haven't tried it yet, but I like the design of the API at first glance.
PlanetScale calls itself the database for developers. (Aren't all databased for developers?) I've asked around and have yet to find a clear way that this product is distinguished from other DBaaS or BaaS tools. That said, I'd still like to try it, just haven't gotten around to it yet.
Thunder Client is a lightweight REST API client that you can use directly inside VS Code. No need to download a separate app like Postman or Insomnia. (I've been using Postman most frequently lately.)
Happy Scribe is a video editing service with built-in transcription. I've played around with it a bit and I love it. I think the pricing is super reasonable for what it is. If you edit quick videos for a blog, check it out. It's not necessarily great for all use cases, and so I ended up ditching it. But I could see it being extremely useful for some folks.
I came across a handful of developers talking about their favorite component UI libraries for React. This is what I found as a result. I don't know much about any of these, but I love the idea of primitive UI libraries that don't require loads of CSS to create specific styling or theming.
Marko is a framework I've yet to share here. It's credited with being of the first frameworks to do partial hydration, which is finally making its way to the mainstream.
React Bricks is a site builder for React-based projects. We looked at this a bit at Stackbit and think it's missing some of the key ingredients that make Stackbit so powerful, but this definitely has a nice feel to it.
The CSS-Tricks newsletter #273 focused on weird browsers. Chris Coyier said, "Perhaps for what we're losing in browser engine diversity, we'll gain in browser UI/UX diversity." Then I went down a rabbit hole and found several browsers gaining some traction today, each focused on a slightly different case:
GistPad is a tool for managing Gists with VS Code.
giscus brings a commenting system to your website using GitHub discussions. This is a thing I've been wanting to do for quite some time, but figured I'd have to write it myself. It seems limited right now, but I'm curious to see if this changes over time.
And last, I'll leave you with this, which is absolutely amazing.
That's all for this month. See you soon!
As always, I welcome feedback on this newsletter (and any content I put out there). Say hello on Twitter.
There are countless ways to learn CSS. Here are 100 resources in various categories to get you started.
When writing some script or program that works with markdown files, it's nice to not have to generate them manually. Here's a script to get the job done for you.