I decided to switch Hugo themes, from Kiera to Mainroad. I wanted a theme with a sidebar and more options to tweak. I had a lot of trouble installing the new theme, as there was a bug which turned out to be due to Netlify having a known issue with Hugo themes. It took me quite a while to find out the cause, which this overly chirpy Netlify Support Engineer summarized as follows:
Just as Docker was the original change agent for the containers revolution, a single company was behind the JAMstack movement: Netlify. So I reached out to Netlify’s co-founder and CEO Matt Biilmann, to talk about Netlify’s journey so far and its current place in the developer ecosystem. Source: Why Netlify Is Tech Agnostic and Its Role in JAMstack Development
Lambros Petrou, Software Engineer at Facebook and ex-AWS, has a good post comparing Netlify, Vercel and AWS as jamstack platforms: If you focus only on Jamstack applications, my recommendation would be to go with Vercel. It has amazing performance, and the zero-config approach really does wonders for the majority of the popular frameworks. Recommending Next.js for one more time 😃If you are going to find uses for Netlify’s add-ons, then it’s a great choice as well!
And by “static” pages we don’t mean, like, 1994 static. The vast majority of Netlify pages are dynamic — they are just interacting with the browser instead of needing to be built server-side. Netlify co-founder and CEO Matt Biilmann, speaking with The New Stack in September 2017.
I’ve started a new, experimental, blog on the open source ‘static site generator’ Hugo. It’s being deployed by Netlify, via GitHub. This was inspired by my recent column about static site generators (SSG) on The New Stack, where I’m a senior editor and weekly columnist. Specifically, I wrote about Gatsby and the fast-growing web development trend known as JAMstack. Read my column for the details, but the upshot: this is a new, cloud native, way of publishing a website.