The world’s fastest framework for building websites.
Find a file
2016-11-22 23:43:55 +01:00
bufferpool bufpool: Add package doc 2016-04-10 01:34:15 +02:00
commands commands, hugolib, parser, tpl: Use errors.New instead of fmt.Errorf 2016-11-22 23:43:55 +01:00
create all: Unify case of config variable names 2016-10-24 20:56:00 +02:00
docs docs: Add Pages to variables section 2016-11-22 09:57:03 +01:00
examples all: Unify case of config variable names 2016-10-24 20:56:00 +02:00
helpers all: Use jww instead of fmt for printing 2016-11-22 22:06:48 +01:00
hugofs all: Unify case of config variable names 2016-10-24 20:56:00 +02:00
hugolib commands, hugolib, parser, tpl: Use errors.New instead of fmt.Errorf 2016-11-22 23:43:55 +01:00
livereload livereload: Add missing GoDoc 2016-03-24 14:05:08 +01:00
parser commands, hugolib, parser, tpl: Use errors.New instead of fmt.Errorf 2016-11-22 23:43:55 +01:00
source commands, hugolib, source, target, tpl: Get rid of some fmt statements 2016-11-22 23:43:55 +01:00
target commands, hugolib, source, target, tpl: Get rid of some fmt statements 2016-11-22 23:43:55 +01:00
tpl commands, hugolib, parser, tpl: Use errors.New instead of fmt.Errorf 2016-11-22 23:43:55 +01:00
transform transform: Return any read or write error from Apply 2016-11-04 00:44:49 +01:00
utils utils: Add godoc 2016-03-23 00:04:28 +01:00
vendor vendor: Update deps 2016-11-16 13:28:21 +01:00
watcher Update import path of fsnotify 2016-04-20 22:28:26 +08:00
.gitignore Fix case issues with Params 2016-11-22 17:33:52 +01:00
.goxc.json add more architectures to .goxc 2015-12-08 16:46:43 -05:00
.mailmap Add .mailmap to get a more correct author log 2015-01-28 16:50:36 +01:00
.travis.yml Bump Travis to Go 1.7.3 2016-10-19 21:53:56 +02:00
bench.sh Add benchmark for sort and reverse 2015-07-21 21:08:20 +02:00
CONTRIBUTING.md Enhance commit message guidelines 2016-11-04 19:37:41 +01:00
Dockerfile Update Dockerfile to pull in missing test dependency 2016-10-01 13:02:35 +02:00
LICENSE.md Change the license to Apache 2.0 2015-11-23 22:16:36 -05:00
main.go Exit with error code on any error 2016-03-11 10:57:13 +01:00
Makefile Use govendor sync instead of get 2016-10-14 23:41:02 +02:00
README.md Readme: Clarify usage of Gitter 2016-09-28 14:51:40 +02:00
requirements.txt Bump Pygment version to 2.1.3 2016-03-13 22:16:00 +01:00
snapcraft.yaml snap: Add "network-bind" plug for "hugo server" to work 2016-10-09 10:10:50 -06:00

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