New rounds of funding for Netlify and Vercel, 23 new tools, a new search feature on the website, and so much more.
Notable changes in my life, on my website, and in other projects.
While I have lots of words to share in this lengthy (and long overdue) newsletter, I haven't published anything in the last two months!
It's not because I ate too many sandwiches, and only partially because I was either sick or taking care of sick kids. But mostly for two reasons.
First, we (soft) launched Stackbit v2 public beta. It took a lot to get here and there's a long way to go, but I'm excited about the progress. I think it looks great and it has a ton of potential. Though I've worn many hats in the process, my biggest contribution to this effort was leading the new documentation site, which itself is a massive work-in-progress.
And second, I've put the figurative pencil down to focus on website improvements. These changes are in preparation for the next generation of seancdavis.com, and I'm very excited for what's to come. Here are some of the changes introduced since the last newsletter:
There's a long way to go, but this is a great start in getting there.
If you want to learn more, check out closed pull requests or reply to this message to chat.
Articles and news I read last month that I found interesting, with some commentary.
I found lots and lots of great reads over the last couple months. Let's start with some news.
Netlify snags $105M Series D to fuel Jamstack-focused web development, which also came with these announcements:
Next.js released v12. Vercel has followed that up announcement with other huge news, including:
Tailwind v3 Released. Tailwind continues to be a polarizing topic. I'm a fan. Excited to upgrade and see what this version has in store.
Learning to future-proof sites using headless CMS and different SSGs. This is playing into the markdown layer or middle layer that I've been suggesting for quite some time. (It always makes me think I should revisit building something in the space.)
Does the Next Generation of Static Site Generators Make Building Sites Better? Some thoughts from Chris Coyier after discovering îles, yet another SSG.
How to Add Authentication to Your 11ty Site. This is great! 11ty is great because it's soooo simple right out of the box. But that makes it feel like it's limited. Being able to extend and build on it like this is fantastic, and really showcases its power.
After some digging, I found that the article came from this tweet. The comments are insightful, including the discussion with Rich Harris (coiner of said term).
Generate a Pull Request of Static Content With a Simple HTML Form. Very cool idea. I love how creative people are with the content layer for their static sites.
Git basics: Conventional commits. Love organizational processes like this. It's a simple structure that is built to serve posterity. It is so nice to be able to thank your past self when you can easily find what you're looking for.
How defensive coding leads to bloat. This is a great lesson on how what is a good idea in principle can have negative consequences based on how it is implemented. Love the idea of Validate the edges, trust the insides.
I decreased my average load time by 381ms. This asks the really difficult question "Do I even need Google Analytics?" I don't want to answer it for myself, but it's got me thinking about it. 😊
From no-code to some-code. This is a super interesting idea — using Notion to get your feet wet with development. But I wouldn't do it in this way. 1) You have zero control over the HTML and it could change tomorrow. Base any styles or interactivity on the structure and you have a lot of work to do when Notion changes something. 2) Content and code become coupled and that's nasty for keeping up to date.
Did you know you can review GitHub PRs by hitting period and then exploring the code? Game. Changer.
Hammer Factories. A coworker of mine dug this older post up. Though this contains totally unnecessary domestic violence jokes, the underlying message is valuable. Another colleague summarized it well: "People will write bad code, and frameworks are too hard to use. 90% of the time manual data entry will suffice."
And just so we don't forget to have a little fun along the way.
What’s the best Wi-Fi name you’ve seen?— Elmira 🦄☁️ (@elmiracodes) November 6, 2021
New tools that I've recently discovered. They aren't necessarily new.
Also lots and lots of finds. Here they are, loosely categorized:
îles: Yet another SSG. This one is focused on the newer concept of partial hydration. And it's built with all the hot topics — Vite, Vue, and MDX. At first glance it looks like Astro, with less stuff. I don't want to dismiss it entirely before I try it, and yet, I don't see myself trying it anytime soon.
Elder.js: An SEO-first Svelte-based framework. And yet another SSG. I have to really see something in a front-end framework to make me want to try it, simply because the market is so saturated. I haven't found that with Elder. But again, I shouldn't dismiss entirely before I try. This might just be the perfect solution for your next project.
Solid looks to be a React alternative focused on performance. Here's a comparison. I don't know how many folks are choosing to ditch React because of performance. Maybe there's a play here, but with React as established as it is, I think we're going to need more than this to see something really catch on.
Lit: Simple and fast web components. Lit suggests you don't need as much boilerplate and can use simple components.
Medusa: Seems like a self-hosted take on headless commerce.
Snipcart: The hosted counterpart.
Shopify Hydrogen: A React-based framework for commerce, using Shopify as the back end. I have mixed feelings about this. On one hand, it's super powerful and opinionated and will get you going quickly. On the other hand, it's locking you in, which may or may not be okay when it comes to a commerce provider.
OneGraph: API integrations tool. I've added many of these in the past. I love the pattern. OneGraph was just acquired by Netlify, which makes me curious to see how this becomes more tightly integrated into Netlify.
Rows: The spreadsheet with superpowers. Looks like an Airtable alternative.
AppFlowy.IO: The open source Notion alternative.
Fig: Your terminal, reimagined. This is in its early days, but I'm using this thing and I love it. The integration feels seamless and it's super helpful. I like it as someone who's been writing code for awhile, but I could see it being supremely helpful to beginners.
Lorem.Space: Calls itself an "API for placeholder images, but useful!"
Fontfacer.io: A helpful little tool to generate CSS snippets based on font files.
ImageOptim: An image optimizer for Mac. I've been using this for the past month and it is delightful. I still prefer a service like Imgix or Cloudinary, but this is great when you can't use those cloud-based tools.
Sourcegraph: Universal code search. It's a smart search utility tool that enables you to search across your entire ecosystem of code. Cool idea. Probably only useful at the enterprise level.
Core Web Vitals Checker from Calibre. I've had trouble getting this to work for my site. I get varying results, but I really like the idea.
Finicky: Always open the right browser. Finicky is a macOS application that allows you to set up rules that decide which browser is opened for every link or URL. Sounds super cool, though I'm happy enough with Chrome profiles at this point.
Ninja Keys: Keyboard shortcuts interface for your website. There have been more and more of these popping up. It's becoming such a popular pattern, I bet we end up seeing a small number rise above the rest.
Scoutbar: Oh look, another one. I do like the positioning statement of this one: "Help you build a better navigation experience." It makes me think we may see a future where this becomes the norm when visiting a website. Does seancdavis.com need one?
This is Stackbit's (my employer's) category, so I tend to run across these frequently.
ImageKit.io: The right way to manage & deliver images on the web. Looks to be like an Imgix or Cloudinary. But the reason this caught my attention is because they just released a video API. I'm starting to see more folks move away from YouTube and toward HTML video. This is something to keep your eye on.
That's all for this issue. See you soon!
As always, I welcome feedback on this newsletter (and any content I put out there). Say hello on Twitter.