# Moving to Hugo

DevFeed: [Moving to Hugo](<https://devfeed.tech/articles/moving-to-hugo-37810.md>)

Original publisher: [Read original article](<https://carlosbecker.com/posts/moving-to-hugo/>)

Author: Carlos Alexandro Becker

Published: 2018-03-19T00:00:00Z

Content type: article

Language: en

Sources: [Carlos Becker](<https://devfeed.tech/sources/carlos-becker.md>)

Topics: [Hugo](<https://devfeed.tech/topics/hugo.md>), [Jekyll](<https://devfeed.tech/topics/jekyll.md>), [build performance](<https://devfeed.tech/topics/build-performance.md>), [Netlify](<https://devfeed.tech/topics/netlify.md>), [let's encrypt](<https://devfeed.tech/topics/let-s-encrypt.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>)

Tags: [go](<https://devfeed.tech/tags/go.md>), [hugo](<https://devfeed.tech/tags/hugo.md>), [incremental](<https://devfeed.tech/tags/incremental.md>), [jekyll](<https://devfeed.tech/tags/jekyll.md>), [let-s-encrypt](<https://devfeed.tech/tags/let-s-encrypt.md>), [netlify](<https://devfeed.tech/tags/netlify.md>), [performance](<https://devfeed.tech/tags/performance.md>)

## AI overview

The author describes moving a blog from Jekyll to Hugo because of slow builds and a long feedback loop. Hugo reduced full build times to under one second and incremental builds to about 300 milliseconds. The site is deployed to Netlify with SSL from Let's Encrypt, and HTML linting uses htmltest, a Go-based port of htmlproof.

## Source excerpt

After some time, I finally decided to move my blog from Jekyll to Hugo.