cb18a5183Fix broken link07a0198bfConfig: Place Google Analytics tag ID under the services key4bf0c719fFix typo50d8ad1afFix muiltilingual menu definition instructions1a32519a9Fix typos6f34ca8e0Explain usage of front matter to target a template5bd977257Improve goldmark config docs447632938Remove Docker notes from installation instructions84741d173Update reference to hugo.work0338d7c71Fix menu templatef5d2f5ed4Fix typos in content/en/functions/fmta3a40ff99Add return type to functions85ac3e779Remove outdated feature imaged47d889e4Fix signatures7551ba28fDocument safe.JSStr functione77993be0Document keyVals function4dba20db3Update themebabf91544Update echoparam8c8203efaAdjust related functions4cb1b30fcFix exampleba95eca64Improve showcase prose5d3dcf366Add Overmind Studios showcase8d634ac70Change code blocks from indented to fencedcfab978e6Add missing code fences407dd5c47Limit related pages for functions to other functions9fa67d981Fix .Site.LastChange doc393aa16d0netlify: Hugo 0.119.0f864af97adocs: Even more about images.Process9d772d5f0docs: More about images.Processbc655f869docs: Regen docshelper41c3536d1Merge commit '9aec42c5452b3eb224888c50ba1c3f3b68a447e9'918ed53f4Add images.Process filter573645883Add $image.Processa1151b0fdAdd images.Opacity filter git-subtree-dir: docs git-subtree-split:cb18a5183f
Hugo Docs
Documentation site for Hugo, the very fast and flexible static site generator built with love in Go.
Contributing
We welcome contributions to Hugo of any kind including documentation, suggestions, bug reports, pull requests etc. Also check out our contribution guide. We would love to hear from you.
Note that this repository contains solely the documentation for Hugo. For contributions that aren't documentation-related please refer to the hugo repository.
Pull requests shall only contain changes to the actual documentation. However, changes on the codebase of Hugo and the documentation shall be a single, atomic pull request in the hugo repository.
Spelling fixes are most welcomed, and if you want to contribute longer sections to the documentation, it would be great if you had the following criteria in mind when writing:
- Short is good. People go to the library to read novels. If there is more than one way to do a thing in Hugo, describe the current best practice (avoid "… but you can also do …" and "… in older versions of Hugo you had to …".
- For example, try to find short snippets that teaches people about the concept. If the example is also useful as-is (copy and paste), then great. Don't list long and similar examples just so people can use them on their sites.
- Hugo has users from all over the world, so easy to understand and simple English is good.
Edit the theme
If you want to do docs-related theme changes, the simplest way is to have both hugoDocs and gohugoioTheme cloned as sibling directories, and then run:
HUGO_MODULE_WORKSPACE=hugo.work hugo server --ignoreVendorPaths "**"
Branches
- The
masterbranch is where the site is automatically built from, and is the place to put changes relevant to the current Hugo version. - The
nextbranch is where we store changes that are related to the next Hugo release. This can be previewed here: https://next--gohugoio.netlify.com/
Build
To view the documentation site locally, you need to clone this repository:
git clone https://github.com/gohugoio/hugoDocs.git
Also note that the documentation version for a given version of Hugo can also be found in the /docs sub-folder of the Hugo source repository.
Then to view the docs in your browser, run Hugo and open up the link:
▶ hugo server
Started building sites ...
.
.
Serving pages from memory
Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)
Press Ctrl+C to stop