The world’s fastest framework for building websites.
Find a file
Bjørn Erik Pedersen 3ce904669a Rewrite TestRSSOutput to use Afero
When we have a virtual filesystem, we might as well test as close to the iron as possible.
2016-10-14 16:41:55 +02:00
bufferpool
commands Use example.org for replace-this-with-your-hugo-site.com 2016-10-14 09:51:39 +02:00
create
docs Use example.org for replace-this-with-your-hugo-site.com 2016-10-14 09:51:39 +02:00
examples
helpers Add context to asciidoc/-tor error logging 2016-10-13 13:48:43 +02:00
hugofs
hugolib Rewrite TestRSSOutput to use Afero 2016-10-14 16:41:55 +02:00
livereload
parser parser: Use strings.Contains instead of strings.Index 2016-09-11 12:23:15 +02:00
source Replace some leftover os.Stat with hugofs.Source 2016-09-11 20:00:38 +02:00
target Redirect to main language from root 2016-09-06 18:32:17 +03:00
tpl Add workaround for block template crash 2016-10-14 11:01:49 +02:00
transform
utils
vendor vendor: Update Viper 2016-10-10 13:41:14 +02:00
watcher
.gitignore Add vendoring with govendor 2016-09-19 00:10:10 +02:00
.goxc.json
.mailmap
.travis.yml travis: Reintroduce asciidoctor to build 2016-10-06 09:31:57 +02:00
bench.sh
CONTRIBUTING.md Contributing: Link the "How to contribute" tutorial 2016-09-28 17:25:24 +02:00
Dockerfile Update Dockerfile to pull in missing test dependency 2016-10-01 13:02:35 +02:00
LICENSE.md
main.go
Makefile Add vendoring with govendor 2016-09-19 00:10:10 +02:00
README.md Readme: Clarify usage of Gitter 2016-09-28 14:51:40 +02:00
requirements.txt
snapcraft.yaml snap: Add "network-bind" plug for "hugo server" to work 2016-10-09 10:10:50 -06:00
wercker.yml

Hugo

A Fast and Flexible Static Site Generator built with love by spf13 and friends in Go.

Website | Forum | Developer Chat (no support) | Documentation | Installation Guide | Contribution Guide | Twitter

GoDoc Linux and OS X Build Status Windows Build Status Dev chat at https://gitter.im/spf13/hugo Go Report Card

Overview

Hugo is a static HTML and CSS website generator written in Go. It is optimized for speed, easy use and configurability. Hugo takes a directory with content and templates and renders them into a full HTML website.

Hugo relies on Markdown files with front matter for meta data. And you can run Hugo from any directory. This works well for shared hosts and other systems where you dont have a privileged account.

Hugo renders a typical website of moderate size in a fraction of a second. A good rule of thumb is that each piece of content renders in around 1 millisecond.

Hugo is designed to work well for any kind of website including blogs, tumbles and docs.

Supported Architectures

Currently, we provide pre-built Hugo binaries for Windows, Linux, FreeBSD, NetBSD and OS X (Darwin) for x64, i386 and ARM architectures.

Hugo may also be compiled from source wherever the Go compiler tool chain can run, e.g. for other operating systems including DragonFly BSD, OpenBSD, Plan 9 and Solaris.

Complete documentation is available at Hugo Documentation.

Choose How to Install

If you want to use Hugo as your site generator, simply install the Hugo binaries. The Hugo binaries have no external dependencies.

To contribute to the Hugo source code or documentation, you should fork the Hugo GitHub project and clone it to your local machine.

Finally, you can install the Hugo source code with go, build the binaries yourself, and run Hugo that way. Building the binaries is an easy task for an experienced go getter.

Install Hugo as Your Site Generator (Binary Install)

Use the installation instructions in the Hugo documentation.

Build and Install the Binaries from Source (Advanced Install)

Add Hugo and its package dependencies to your go src directory.

go get -v github.com/spf13/hugo

Once the get completes, you should find your new hugo (or hugo.exe) executable sitting inside $GOPATH/bin/.

To update Hugos dependencies, use go get with the -u option.

go get -u -v github.com/spf13/hugo

Contributing to Hugo

For a complete guide to contributing to Hugo, see the Contribution Guide.

We welcome contributions to Hugo of any kind including documentation, themes, organization, tutorials, blog posts, bug reports, issues, feature requests, feature implementations, pull requests, answering questions on the forum, helping to manage issues, etc.

The Hugo community and maintainers are very active and helpful, and the project benefits greatly from this activity.

Throughput Graph

Asking Support Questions

We have an active discussion forum where users and developers can ask questions. Please don't use the Github issue tracker to ask questions.

Reporting Issues

If you believe you have found a defect in Hugo or its documentation, use the Github issue tracker to report the problem to the Hugo maintainers. If you're not sure if it's a bug or not, start by asking in the discussion forum. When reporting the issue, please provide the version of Hugo in use (hugo version).

Submitting Patches

The Hugo project welcomes all contributors and contributions regardless of skill or experience level. If you are interested in helping with the project, we will help you with your contribution. Hugo is a very active project with many contributions happening daily. Because we want to create the best possible product for our users and the best contribution experience for our developers, we have a set of guidelines which ensure that all contributions are acceptable. The guidelines are not intended as a filter or barrier to participation. If you are unfamiliar with the contribution process, the Hugo team will help you and teach you how to bring your contribution in accordance with the guidelines.

For a complete guide to contributing code to Hugo, see the Contribution Guide.

Analytics