HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gohugoio
hugo
Go2013–2026
gohugoio / hugo

hugo

The world’s fastest framework for building websites.

64Distinct people
72Mentions
1Explicit recommenders
90.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The world’s fastest framework for building websites.

GitHub

Where it is used

What people are saying

My problem is the mirroring itself. I don't want, taking your example, /posts/post1 just because post1 is under posts. You can get around this with some SSGs but this doesn't…

alan_n used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year72 dated mentions

Observed mentions: 2013-08-05 22:35:31 UTC to 2026-05-24 23:04:04 UTC.

0369122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 11 mentions; 6 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 3 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC211
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC826
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC716
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC1165
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC918
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC505
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC918
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC615
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC431
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC404

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
A fast and flexible static site generator built with love by bep, spf13, and friends in Go. Website | Installation | Documentation | Support | Contributing | Mastodon Overview Hugo is a static site generator written in Go, optimized for speed and designed for flexibility. With its advanced templating system and fast asset pipelines, Hugo renders a complete site in seconds, often less. Due to its flexible framework, multilingual support, and powerful taxonomy system, Hugo is widely used to create: Corporate, government, nonprofit, education, news, event, and project sites Documentation sites Image portfolios Landing pages Business, professional, and personal blogs Resumes and CVs Use Hugo's embedded web server during development to instantly see changes to content, structure, behavior, and presentation. Then deploy the site to your host, or push changes to your Git provider for automated builds and deployment. Hugo's fast asset pipelines include: CSS Processing – Bundle, transform, minify, create source maps, perform SRI hashing, and integrate with PostCSS. Image processing – Convert, resize, crop, rotate, adjust colors, apply filters, overlay text and images, and extract metadata JavaScript bundling – Transpile TypeScript and JSX to JavaScript, bundle, tree shake, minify, create source maps, and perform SRI hashing. Sass processing – Transpile Sass to CSS, bundle, tree shake, minify, create source maps, perform SRI hashing, and integrate with PostCSS Tailwind CSS processing – Compile Tailwind CSS utility classes into standard CSS, bundle, tree shake, optimize, minify, perform SRI hashing, and integrate with PostCSS And with Hugo Modules, you can share content, assets, data, translations, themes, templates, and configuration with other projects via public or private Git repositories. See the features section of the documentation for a comprehensive summary of Hugo's capabilities. Sponsors       Editions Hugo is available in two editions. Use the standard edition unless you need additional features. Feature standard deploy Core features ✔️ ✔️ Direct cloud deployment (1) ❌ ✔️ (1) Deploy your site directly to a Google Cloud Storage bucket, an AWS S3 bucket, or an Azure Storage container. See details. Installation Install Hugo from a prebuilt binary, package manager, or package repository. Please see the installation instructions for your operating system: macOS Linux Windows DragonFly BSD, FreeBSD, NetBSD, and OpenBSD Build from source To build Hugo from source you must install: Git Go version 1.27.0 or later Standard edition To build and install the standard edition: CGO_ENABLED=0 go install github.com/gohugoio/hugo@latest Deploy edition To build and install the deploy edition: CGO_ENABLED=0 go install -tags withdeploy github.com/gohugoio/hugo@latest Documentation Hugo's documentation includes installation instructions, a quick start guide, conceptual explanations, reference information, and examples. Please submit documentation issues and pull requests to the documentation repository. Support Please do not use the issue queue for questions or troubleshooting. Unless you are certain that your issue is a software defect, use the forum. Hugo's forum is an active community of users and developers who answer questions, share knowledge, and provide examples. A quick search of over 20,000 topics will often answer your question. Please be sure to read about requesting help before asking your first question. Contributing You can contribute to the Hugo project by: Answering questions on the forum Improving the documentation Monitoring the issue queue Creating or improving themes Squashing bugs Please submit documentation issues and pull requests to the documentation repository. If you have an idea for an enhancement or new feature, create a new topic on the forum in the "Feature" category. This will help you to: Determine if the capability already exists Measure interest Refine the concept If there is sufficient interest, create a proposal. Do not submit a pull request until the project lead accepts the proposal. For a complete guide to contributing to Hugo, see the Contribution Guide. License For the Hugo source code, see LICENSE. We also bundle some libraries in binary/WASM form: libwebp, BSD-3-Clause license Katex, MIT license QuickJS, License
Read the full README on GitHub

What Hacker News says

4 sources
LOL Actually one my hopeful future additions is to maintain (or use discovery) a list of name-to-repo mappings. ie. I would love for users to be able to just do: $ bingo install hugo ... installing github.com/gohugoio/hugo I don't really want the concept of any project _owning_ a name, so in the cases where multiple projects were mapped/discovered for a given name, we'd want to ask the user which one they wanted to install.
In Bingo – The missing package manager for Go binaries (Homebrew for “go install”)
(I was on xmas vacay so missed the initial post) Wow what a nice random surprise - Thanks OP for the call out! Go already makes installing go apps extremely easy, ie: go install package-url What Bingo tries to do is make _managing_ that installed binary just as easy. Once installed, you can then manage the installation by the binary's name. An example I personally use: $ bingo install github.com/gohugoio/hugo # ... two versions later $ bingo update hugo I'm happy to try to answer any questions - else I'll be perusing the comments looking for places to chime in. Thanks again, -TW
In Bingo – The missing package manager for Go binaries (Homebrew for “go install”)
Oh my, here we go again: The first post on a general language thread is bashing Go and hyping Rust ... that in itself is a very sad and problematic story as some inexperienced devs fall into the trap of this kind of promotion that Rust is the silver bullet for all kind of applications / projects. Rust has it's place. Go has it's place. Java has it's place. There's so much more than pure language feature for successful projects. The language is not even in the top 3. But more importantly I disagree to your actual assessment: Go code is very easy to read and understand. You're at the core of the problem at hand at once. No over abstractions or complex syntax or complex language features. Go has very few quirks (every language has them, people thinking "their" language is free of them are just being ignorant). I found very few real world iss
Read the rest
ues caused by language quirks in Go production code (just as with Java or .NET). Much more important for quality code are engineering decisions, structure and processes. As Go is easy to write, read and understand it leaves more mental capacity to those often underrated areas. Go is a memory managed language. That alone makes it much easier to understand and maintain than every other language where you need to do it yourself. Again, more room for engineering decisions. As Go has a very large and extremely useful standard lib you have much less issues with unmaintained third party libs. Imaging a large Rust codebase and all it's dependencies to one-person-maintained libs. A maintenance nightmare thinking 10 years ahead. Just look at some good quality Go code, e.g. Hugo https://github.com/gohugoio/hugo/blob/master/navigation/menu... I've picked an arbitrary file. There might be issues in it, but look how easy to read and understand it is. Regarding Rust: I have no general interest in talking bad about it, but need to make a point. Just as a real world reminder think of the Actix story. One part is the unsafe issue. How many people in the world would be able to understand the actual code and could have cleaned it up? Maybe 50? Fortunately there was a happy end. But how much time and energy did it take to get it on track again? What if Actix had not been the most popular and known framework? All our companies Go servers (still mostly Java apps) are build with the standard lib. One thing less to worry about in the long run.
In Green vs. Brown Programming Languages

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.