At Nozzle.io, we take SEO, site performance, and user/developer experience very seriously. Over the last year, we’ve launched many sites using different static site tools that claim to solve these goals, but we have yet to find one that satisfies our requirements completely. Though each tool was unique and useful in its own way, we managed to pare down our list to the two following libraries:

Last year I wrote an article introducing the general concepts behind static site generators. This time around I’d like to dive into some specific (yet still basic) details about a popular static site generator called Hugo, comparing it to its most well-known “dynamic” ancestor, WordPress.

The answer to these challenges almost invariably involves creating an API — a way of exposing data in such a way that it can be requested and manipulated by virtually any type of system, regardless of its underlying technology stack.

It had to have SSL which would be easy to setup. It had to use Docker. It had to work via git pushes

Host Your Static Site as a Gitlab Page Behind a KeyCDN Pull Zone

How we used YAML front-matter to massively change the layout for different posts on our agency’s new website

Last month, Netlify introduced their implementation of HTTP/2 Server Push. We started using this and have have noticed significantly faster websites. Here is how to configure Middleman to use this feature.

In converting my Pelican blog over to Hugo, I needed to learn a new templating system. I miss a few things that Pelican did, like categories based on folders and not front matter. However, I can see advantages of allowing more organization in these folders, without affecting final position on the web.

Gatsby is an incredible static site generator that allows for React to be used as the underlying rendering engine to scaffold out a static site that truly has all the benefits expected in a modern web application.

In this article I’m going to go through the basics of setting up a Jekyll site, GitHub Pages and Staticman. If you’re just interested in Staticman please skip down a bit!

I realise this type of trick has been done a few times with ever so slightly different syntax, but here is my spin on the whole thing

This post tells you how to start small with just the bare minimum files and directories to build a Hugo site without errors.

Now that I have 8 static websites deployed into AWS using S3 and CloudFront I need to automate the deployment process so that I can make changes quickly and get them to production with less effort. To that end I have developed some scripts and configurations that automate the deployment of this site to a QA environment and production when changes are pushed to either branch.

Hexo being primarily a blog framework we’ll show you how you can integrate a Snipcart housed buy-button into your blog platform. You’ll never know when you’ll want to give the option to your reader to buy a product you’re writing about, so why not offer it directly on your page?

Adding a typeform to your Hugo site is as easy as you would expect with a static site.

Hugo is a light weight, fast and modern static website engine written in go. It literally takes just milliseconds to build your entire site. For the given lightness, it is highly flexible as well.

Tips for how to setup Hugo and Madoko inside of an Alpine Linux-based Docker image for Gitlab CI/CD

In this blog post the JavaScript is written with jQuery, the APIs implemented with Azure Functions and the markup generated with Hugo.

In today’s post we will be showing how to deploy a Hugo site to Bluemix using the Cloud Foundry command line and build tools.

During the last 18 months, working on my Web site became a daunting task—be that for developing, redesigning it, writing a blog post, or making updates to my speaking and workshop pages. My then static site generator, Jekyll, is why. And a change has long been overdue…

I wanted to allow users to authenticate with their github accounts, but Netlify did’t have support for 3rd party OAuth providers (learn more here). It allows you to create account in their app, connect your repository with the web and let them to serve it via their fast CDN network. But I didn’t need serving via other service. I just needed to let users edit the webs with knowing nothing about GIT. That is why I wrote netlify-cms-github-oauth-provider.

Building a Hugo website on CircleCI 2.0 is fast and simple, so let’s start here. We’ll walk through snippets of an example .circleci/config.yml with the whole file at the end of this post.

The problem with Disqus is that this one JavaScript file you embed to your website makes about 50 requests when a page loads. And that is a lot!

SON Feed is an alternative to Atom and RSS that uses JSON instead of XML. I figured I could add support for it in less than the time it would take to enjoy my coffee and maybe some readers would find it useful.

At work my company’s product team has been using GitHub wiki for years for all of our use facing documentation. As they have grown from a small open source project to a much larger team with a more fully featured enterprise offering, they had outgrowing using GitHub wiki. We went out in search of a set of tools to build our own self hosted documentation web site with the following set of requirements…

Recently a new specification was launched to recreate RSS in JSON, JSON Feed. For folks who may not be aware, RSS is an XML spec (well, multiple ones) for sharing content between sites.

One of the great advantages of headless CMS’ is that they are able to be consumed by a wide variety of different applications and build tools, rather than being tied specifically to a web frontend. And today we’ll be talking about using GraphCMS to create a static site - an architecture that suits many use cases much better than using a dynamic site or single page app.

A problem I came across when building Trying to work was how do I display “Google-like” dynamic opening times using only liquid—Jekyll’s templating language? Well, as it turns out, quite easily.

The solution below uses your RSS feed from Medium, parses it and stores each post as a ‘virtual document’, in a newly created Jekyll collection. From here you’re able to access the title and content of each post, which can then be displayed on whatever page you want.