cfd74b57dAdd a config file update step.5957d8815Wrap cache configuration in code-toggle914405c0ecapitalization and indentation fix for taxonomies page (#1159)223b80f42Fix page kinds shortcode not rendering on Taxonomies page (#1158)a9b6fa984Clarify weight description.29e121681Warn about zero weights in front matter.27ce7ba8cRelease 0.73.0e9596b2eeMerge branch 'temp73'074a270cdreleaser: Add release notes to /docs for release of 0.73.04f56a9fc0width fix of expanding code box in documentation (#1156)f27254d60css fix of expanding code box in documentation (#1155)43b576178Fix incorrect directory name in quick-start (#1154)16726eacfAdd GroupByLastmod73c31758eFix for broken link again (#1151)d07067295Fix broken link (#1144)bc0b484d1Rename taxonomy kinds from taxonomy to term, taxonomyTerm to taxonomy674d71842Fix Typo on Docker section of installation pageb87778165Merge commit 'efa74c5c6e6ff1daddeb5834ea7c69bed2acf171'c7cdebed3tpl/crypto: Add hmac260130cc0Allow hook template per section/type1f70519d8releaser: Add release notes to /docs for release of 0.72.08516d540cMerge commit '9e1dcefc5f559944b70d2fa520f6acd5c56a69f2'c49195c69common/maps: Add Scratch.Values78072df81Add redirect support to the server90ca0af6bFix typo in install instructions git-subtree-dir: docs git-subtree-split:cfd74b57d9
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 code base 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.
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