Welcome to the very first issue of The Spinneret! This is an idea I've had for awhile. It's taken different forms over the last few months, but has led to this — a blog article and email newsletter that consolidates what's happening in my sphere of web development.
I can't, in good conscious, release this without addressing the injustice being fought throughout the United States and the world. In a time like this, silly articles like this one aren't important. Equality, comfort, safety, health — those are the things that matter.
I continue to write because it makes me happy. It calms me down and brings me comfort. And if you get something out of it, that's a bonus for me. But what's more important is that we do something to fight for justice and equality, or at least to support those doing the fighting.
Okay. Here we go!
I took more than a week off in May to unplug in a cabin in the woods with my family. It was a much needed break! But it meant I didn't publish as much as I normally would in a month. However, there were still a few articles I enjoyed writing:
I've been exploring the idea of Static APIs over the last few months, trying to add a new tutorial here and there. Last month I added a quick tutorial on Building a Static API with Eleventy. I also got some love from @chriscoyier on CSS Tricks!
I try to put out one article each month for Ample on the Jamstack. This month we squeezed two in there:
I'll be slow to get back into writing upon my return from the woods, but I expect to have another Static API tutorial in June. I'm also beginning to explore screencasts and video content to provide some variation in the content I produce. We'll see how that goes!
While I had my head down banging out code on a couple hot projects this last month, I was able to take a bit of time and talk shop with my team. Here were my three favorite topics:
Building off my article on settling down in a Jamstack world, it's been tough to work efficiently (by standardizing) without missing cool new tools on the scene. We've struggled much with what CMS we should recommend on any given project.
That led to a conversation on whether we should build some tooling to abstract the front from the back end — so that we can use any data source, but the structure of our data looks the same to whatever static site generator we use.
The very next day after this conversation I discovered Sourcebit from Stackbit. I haven't explored it yet, but plan to dig in over the coming months to see if that (or something inspired by that) will solve our problems. I also suspect I'll have several articles coming along this theme of settling down without losing touch.
I've spent a lot of time working with gatsby-transformer-remark over the last couple months, and that's not letting up any time soon. I'm trying to build a system for structured content with Gatsby to make it feel like I've got a structured database when all I really have are a bunch of local markdown files.
There will be much that comes out of this, including blog posts and tutorials. This is the current problem I'm solving, but it continues to evolve.
;["1", "7", "11"].map(parseInt)
// => [1, NaN, 3]
These are the two that caught my attention:
My team has been working more and more with React lately. React hooks are pretty amazing (sometimes). In looking to solve specific problems, we've found a couple nice resources that I'm sure I'll return to:
I'm very excited about this! I haven't tried to work with it yet, but I suspect I will soon.
Photo Credit: Forbes
I'd assume that in a month in which Jamstack Conf takes place, that's all the news I'm focused on. Oh, but it wasn't. Here's what else is happening:
Note: While I was unable to attend Jamstack Conf, I plan to include a separate writeup of the content, which I will link to in next month's issue.
I came across all of these tools and apps for the first time in May. Buttondown is the only one I've used so far, and I'm at the very early stages. So I don't have commentary to share here, just a list of links:
I hope you enjoyed this first edition of The Spinneret! As always, I welcome feedback via Twitter.
I'll see you next time!