4e7e1815bFix some typosd23d8f5c4Remove 'fundamentals' category from function pages52fa65e15Mention Chroma as the preferred syntax highlighter64ca535dbMerge commit '8762aee8afe30bec6f1fbc9560749983dc44d60b'8762aee8aSquashed 'themes/gohugoioTheme/' changes from 396b859f..6f3a8bf503f0673a9Move the gopher to the theme320e268cdSpellinge45b640f7More layout lookup workfe0ad9d9dSync the YAML config menu example with TOML'sb9505fc70Remove template reference to ordinal numbers0fa2532d3Remove deprecated Hugoidx, add native hugo solution2152b907cFix a link in the last commit47614f416Manually specifying heading anchors in Markdown content9d6770d2aRelease notes 0.37.1e1eed8b27Remove some unused imagese960046f5releaser: Prepare repository for 0.38-DEV4fa83a4eereleaser: Add release notes to /docs for release of 0.37.146c879995releaser: Bump versions for release of 0.37.1fb3ac5a3ereleaser: Prepare repository for 0.38-DEV4870c8e7bUpdate archetypes.md232c0b578Merge commit '2b18014fd0aa99e9f1a5610ba875101351a90de3'2b18014fdSquashed 'themes/gohugoioTheme/' changes from fe71e360..396b859f62567e9aaAdd some "writing guidelines"7cfd530d2Revise the archetype docs5d4c3c03cUpdate data-templates.mde5fee3099Update page-bundles.mdca7f03c8dUpdate page-bundles.md2a7fdc269Fix typo 'vailable' to 'available' line 53999b75201LastMod should be Lastmod?099f46ca5Fix spacing in content-management/types.md6bcdc58efWord choice improvements20e8a21f6update rss linking docs7ef44d262Add some missing configuration entriesf1c7aa568Sort config list5cb8ceadeCreate a proper definition list for the configuration settings25dffe4acSend custom dimensions in GA55df01a34Fix broken gtag6c8772aadAdd site to GA confige63acb894Remove conflicting release note for 0.35f30083a23Add branch to GA config99caedb96Set the small-multiples to draft4a33c70abPolish the Small Multiples showcase7b2f1ea2eAdd small multiples showcasee78e96baeAdd new sponsorc42943041updated to new Forestry logoe07eda273Add OS env to faq414f0dbc6Release Hugo 0.3785f0cc324Merge branch 'temp37'1e6da9497Rebuild images75e97adfcreleaser: Add release notes to /docs for release of 0.3750b887cb0releaser: Bump versions for release of 0.377acf73ba3Merge commit '900b5f6cfe5a377ef369d26cd700201be4cf6b06'819d02c30Merge commit '374d184e6747678364fd61f5faf328ec9205eb6b'c7eacf018Fix typos in development contribution doc git-subtree-dir: docs git-subtree-split:4e7e1815b7
6.1 KiB
A Fast and Flexible Static Site Generator built with love by bep, 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, ease of 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 metadata, 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, 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
The Hugo Documentation
The Hugo documentation now lives in its own repository, see https://github.com/gohugoio/hugoDocs. But we do keep a version of that documentation as a git subtree in this repository. To build the sub folder /docs as a Hugo site, you need to clone this repo:
git clone git@github.com:gohugoio/hugo.git
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.
