662e12f348
This commit completes the "The Revival of the Archetypes!"
If `.Site` is used in the arcetype template, the site is built and added to the template context.
Note that this may be potentially time consuming for big sites.
A more complete example would then be for the section `newsletter` and the archetype file `archetypes/newsletter.md`:
```
---
title: "{{ replace .TranslationBaseName "-" " " | title }}"
date: {{ .Date }}
tags:
- x
categories:
- x
draft: true
---
<!--more-->
{{ range first 10 ( where .Site.RegularPages "Type" "cool" ) }}
* {{ .Title }}
{{ end }}
```
And then create a new post with:
```bash
hugo new newsletter/the-latest-cool.stuff.md
```
**Hot Tip:** If you set the `newContentEditor` configuration variable to an editor on your `PATH`, the newly created article will be opened.
The above _newsletter type archetype_ illustrates the possibilities: The full Hugo `.Site` and all of Hugo's template funcs can be used in the archetype file.
Fixes #1629
|
||
|---|---|---|
| bufferpool | ||
| cache | ||
| commands | ||
| config | ||
| create | ||
| deps | ||
| docs@8c9359bab4 | ||
| docshelper | ||
| examples | ||
| helpers | ||
| hugofs | ||
| hugolib | ||
| i18n | ||
| livereload | ||
| media | ||
| output | ||
| parser | ||
| releaser | ||
| source | ||
| tpl | ||
| transform | ||
| utils | ||
| vendor | ||
| watcher | ||
| .gitignore | ||
| .gitmodules | ||
| .goxc.json | ||
| .mailmap | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| LICENSE.md | ||
| Makefile | ||
| README.md | ||
| appveyor.yml | ||
| bench.sh | ||
| benchSite.sh | ||
| goreleaser.yml | ||
| main.go | ||
| requirements.txt | ||
| snapcraft.yaml | ||
README.md
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
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 don’t 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 macOS (Darwin) and Android 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/gohugoio/hugo
Once the get completes, you should find your new hugo (or hugo.exe) executable sitting inside $GOPATH/bin/.
To update Hugo’s dependencies, use go get with the -u option.
go get -u -v github.com/gohugoio/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.
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.