The world’s fastest framework for building websites.
Find a file
Bjørn Erik Pedersen 004fcddc80 Remove superfluous p-tags around shortcodes
This commit replaces the regexp driven `replaceShortcodeTokens` with a handwritten one.

It wasnt't possible to handle the p-tags case without breaking performance.

This fix actually improves in that area:

```
benchmark                           old ns/op     new ns/op     delta
BenchmarkParsePage                  142738        142667        -0.05%
BenchmarkReplaceShortcodeTokens     665590        575645        -13.51%
BenchmarkShortcodeLexer             176038        181074        +2.86%

benchmark                           old allocs     new allocs     delta
BenchmarkParsePage                  87             87             +0.00%
BenchmarkReplaceShortcodeTokens     9631           9424           -2.15%
BenchmarkShortcodeLexer             274            274            +0.00%

benchmark                           old bytes     new bytes     delta
BenchmarkParsePage                  141830        141830        +0.00%
BenchmarkReplaceShortcodeTokens     52275         35219         -32.63%
BenchmarkShortcodeLexer             30177         30178         +0.00%
```

Fixes #1148
2015-06-21 22:51:12 +02:00
bufferpool Fix some Go Lint errors 2015-03-06 15:58:14 +01:00
commands Make removal of accents in taxonomy and section paths optional 2015-06-16 19:25:48 +02:00
create Apply gofmt -s 2015-03-05 23:57:38 +01:00
docs Add new tutorial for multilingual sites 2015-06-16 12:17:09 +02:00
examples Fix multilingual styling with small screen. 2015-05-07 21:16:38 +02:00
helpers Remove superfluous return 2015-06-16 22:31:51 +02:00
hugofs Add support for Ace base and inner templates 2015-03-26 17:22:35 +01:00
hugolib Remove superfluous p-tags around shortcodes 2015-06-21 22:51:12 +02:00
livereload livereload: apply some Golint rules 2015-03-07 12:58:51 +01:00
parser Update test logs for uniformity and consistency 2015-05-08 22:27:00 -04:00
source Add some tests for IgnoreFiles 2015-06-03 18:54:15 +02:00
target Make sure target destination has the right path separator. 2015-06-11 21:16:51 +02:00
tpl Add last template function 2015-06-15 21:18:38 +02:00
transform Apply gofmt -s 2015-05-25 12:54:13 +02:00
utils Apply gofmt -s 2015-03-05 23:57:38 +01:00
watcher Switch from fsnotify.v0 to fsnotify.v1 API (watcher) 2015-03-10 09:59:55 -06:00
.gitignore Add convenience script to run benchmarks 2015-05-14 23:17:45 +02:00
.goxc.json adding goxc config file 2015-05-25 21:47:41 -04:00
.mailmap Add .mailmap to get a more correct author log 2015-01-28 16:50:36 +01:00
.travis.yml Let travis test against go-tip 2015-06-11 20:53:43 +02:00
bench.sh Add convenience script to run benchmarks 2015-05-14 23:17:45 +02:00
LICENSE.md adding hugo 2013-07-04 11:32:55 -04:00
main.go More proofreading and minor revisions to Hugo docs 2014-09-08 11:41:10 -04:00
Makefile Added top level .Hugo variable with version, commit and generator information + docs 2015-01-19 01:22:23 +01:00
README.md Remove section about the buildDate being configurable 2015-04-06 16:30:49 +02:00
wercker.yml Create wercker.yml 2014-01-15 11:02:24 -05:00

Hugo

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

Website | Forum | Chat | Documentation | Installation Guide | Twitter

Build Status wercker status Build status Join the chat at https://gitter.im/spf13/hugo

Overview

Hugo is a static site 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 meant 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.

Clone the Hugo Project (Contributor)

  1. Make sure your local environment has the following software installed:

  2. Fork the Hugo project on GitHub.

  3. Clone your fork:

     git clone https://github.com/YOURNAME/hugo
    
  4. Change into the hugo directory:

     cd hugo
    
  5. Install the Hugo projects package dependencies:

     go get -u -v github.com/spf13/hugo
    
  6. Use a symbolic link to add your locally cloned Hugo repository to your $GOPATH, assuming you prefer doing development work outside of $GOPATH:

     rm -rf "$GOPATH/src/github.com/spf13/hugo"
     ln -s `pwd` "$GOPATH/src/github.com/spf13/hugo"
    

    Go expects all of your libraries to be found in$GOPATH.

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

We welcome contributions to Hugo of any kind including documentation, themes, organization, tutorials, blog posts, bug reports, issues, feature requests, feature implementation, 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

If you have any questions about how to contribute or what to contribute please ask on the forum

Code Contribution Guideline

We welcome your contributions. To make the process as seamless as possible, we ask for the following:

  • Go ahead and fork the project and make your changes. We encourage pull requests to discuss code changes.
  • When youre ready to create a pull request, be sure to:
    • Have test cases for the new code. If you have questions about how to do it, please ask in your pull request.
    • Run go fmt
    • Squash your commits into a single commit. git rebase -i. Its okay to force update your pull request.
    • This blog article is a good resource for learning how to write good commit messages, the most important part being that each commit message should have a title/subject in imperative mode without trailing period: "Return error on wrong use of the Paginator", NOT "Returning some error." Also, if your commit references one or more GitHub issues, always end your commit message body with See #1234 or Fixes #1234. Replace 1234 with the GitHub issue ID. The last example will close the issue when the commit is merged into master.
    • Make sure go test ./... passes, and go build completes. Our Travis CI loop (Linux) and AppVeyor (Windows) will catch most things that are missing.

Building Hugo with Your Changes

cd /path/to/hugo
go build -o hugo main.go
mv hugo /usr/local/bin/

Adding compile information to Hugo

When Hugo is built using the above steps, the version sub-command will include the mdate of the Hugo executable, similar to the following:

Hugo Static Site Generator v0.13-DEV buildDate: 2014-12-24T04:46:03-07:00

Instead, it is possible to have the version sub-command return information about the git commit used and time of compilation using build flags.

To do this, replace the go build command with the following (replace /path/to/hugo with the actual path):

go build -ldflags "-X /path/to/hugo/hugolib.CommitHash `git rev-parse --short HEAD 2>/dev/null` -X github.com/spf13/hugo/hugolib.BuildDate `date +%FT%T%z`"

This will result in hugo version output that looks similar to:

Hugo Static Site Generator v0.13-DEV-8042E77 buildDate: 2014-12-25T03:25:57-07:00

Alternatively, just run make — all the “magic” above is already in the Makefile. 😉

Running Hugo

cd /path/to/hugo
go install github.com/spf13/hugo/hugolib
go run main.go

Complete documentation is available at Hugo Documentation.

Analytics Bitdeli Badge