Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
26 lines (18 sloc) 3.51 KB
title titleHtml tags postRank
Now Deploying to Netlify
Now Deploying to <img src="/img/ab5f9d4b.jpg" alt="netlify’s Avatar" class="z-avatar z-avatar-eq">Netlify
popular-posts
3

As my time at {% assign imgObj = "filamentgroup" | avatarObject %}{% img imgObj, defaultImageOptions %}Filament Group draws to a close, I am very excited to share with y'all that I am joining {% assign imgObj = "netlify" | avatarObject %}{% img imgObj, defaultImageOptions %}Netlify!

Given my own open source work with {% assign imgObj = "eleven_ty" | avatarObject %}{% img imgObj, defaultImageOptions %}Eleventy over the past two years, this might seem like an incredibly obvious transition. Obvious transitions are good!

I have been very impressed with the founders of Netlify: {% assign imgObj = "Chr_Bach" | avatarObject %}{% img imgObj, defaultImageOptions %}Chris Bach and {% assign imgObj = "biilmann" | avatarObject %}{% img imgObj, defaultImageOptions %}Matt Biilmann. I was first introduced to Matt years ago when our paths crossed working on the font loading for the {% assign imgObj = "smashingmag" | avatarObject %}{% img imgObj, defaultImageOptions %}Smashing Magazine relaunch. He had written a great PostCSS plugin to handle automatic class management for font loading.

For me Smashing Magazine was the watershed moment for JAMstack1, similar to what Filament Group (and friends) did for {% assign imgObj = "rwd" | avatarObject %}{% img imgObj, defaultImageOptions %}Responsive Web Design with the {% assign imgObj = "BostonGlobe" | avatarObject %}{% img imgObj, defaultImageOptions %}Boston Globe. The Smashing Magazine launch showed that not only is a large-scale JAMstack implementation possible, but it can be a more efficient way to work with the potential to deliver a higher quality final product. The JAMstack gives more power to front-end developers by properly decoupling the front-end from the back while simultaneously delivering performance improvements. It allows front-end developers to focus on their specialty.

Sites that move to this architecture really have the opportunity to see some big wins in both developer experience and user experience (as if they were ever in disagreement).

At this point it's pretty clear that Responsive Web Design has won. The few lone hold-outs are left defending the User-Agent string—that’s not a hill you want to die on. Are there a few bad implementations of Responsive Web Design? Sure. But it's the clear winner to deliver your site to the infinite landscape of real world devices.

I believe the same revolution is happening with JAMstack and I’m excited to play a part of it at Netlify.


  1. Jump back to the reference. I’m pretty sure {% assign imgObj = "davatron5000" | avatarObject %}{% img imgObj, defaultImageOptions %}Dave Rupert said this first or at least something to this effect at {% assign imgObj = "jamstackconf" | avatarObject %}{% img imgObj, defaultImageOptions %}JAMstack_conf.
You can’t perform that action at this time.