Quick tips, more video content, website updates, and a myriad of new tools I've discovered. Come see what happened in my Jamstack world in February 2021.
As the number of subscriptions to this newsletter increases, I'll look to refine what I do here to make it as beneficial as possible to you.
As an early follower in this adventure, I want you to help influence that direction. I'd love your feedback! The easiest way to get in touch with me is on Twitter.
A lot happened in February and the format of this newsletter has changed slightly as a result. Here are the highlights:
New blog posts and videos I published last month
Here are links to the majority of pieces I published this month. I've continued to write about component organization as I work toward a big piece that pulls them all together. I also introduced the concept of Quick Tips. I'm not sure if these will end up being exclusively videos or articles, but for now there's a little of each.
Subscribe here to get the content earlier.
Notable changes made to my website codebase and other projects.
Articles and news I read last month that I found interesting, with some commentary.
Gatsby announced v3.0 at its conference. I didn't attend the conference, but spent some time with the recap. I used to be an avid user of Gatsby and worked in it almost daily. Today I prefer Next.js for more complex projects.
I'm exited to see so much development from Gatsby. I think the more competition we have, the better, and Gatsby had been kind of quiet in 2020 (maybe partially in response to the negative press).
This release is a little concerning to me, though. They made Gatsby builds waaaaay faster ... on their Gatsby Cloud platform. Again, more competition is good. But they seem to be pushing hard to their paid services as a way to deal with the unpleasantness of the product.
In other words, I read that Gatsby is working on performance, but only sort of. And I didn't see a mention of considering page speed performance, which, in my experience, was abysmal.
Jamstack Conf 2021 announced! I'm already signed up! Really hoping to see multiple tracks this time around. The Jamstack space is now mainstream and the attendees are likely to vary widely in skillset and focus. I hope the content follows suit.
Blitz launched a new website and beta version of the product. I haven't personally used this, but I like following the progress because it's such an interesting project to me. It's a full-stack framework, built on Next.js, which is built on React. It seems like such a risky move to build a framework on another framework. And yet, it might also be a brilliant move. I'm curious to see where this goes.
This article got a lot of attention: Choosing between Netlify, Vercel and Digital Ocean. It's way off the mark, IMO. It totally misses the nuance between Netlify and Vercel. It calls out Vercel for a sneaky pricing page, which is silly. Most pricing pages do this, and Vercel's has a link to the fine print. If you want to use something, you need to take the responsibility of doing research on yourself. (And, generally speaking, if you're making money by using a service, you should probably be paying for the service.)
In the end, it comes down to this recommendation:
If you have a small project: Go with netlify.
If you have a larger project: Use Digital Ocean.
I wouldn't choose Vercel anymore because of that dark pattern pricing strategy.
This is terrible advice. It has nothing to do with addressing the problem you are trying to solve. It's not a matter of small v large.
Because I can't give you a straight answer in a sentence, it makes me think I should write an article to add the necessary nuance here! Yeah, okay. I'll do that in March!
And here are some other quick-hitters.
New tools that I've recently discovered. They aren't necessarily new.
I came across a ton of new tools this last month. I think that is, in large part, a result of starting this new job and working with new people every day. So it may slow down in months to come. But maybe not.
Here they are, in alphabetical order (because I couldn't come up with any better way to organize them):
Phew! That was a lot. I hope you got something out of it.
See you next time!
Help your content editors enjoy their CMS experience by designing a content schema that balances productivity and flexibility.