hugo/docs
Bjørn Erik Pedersen 1e19a98451 releaser: Prepare repository for 0.26-DEV
[ci skip]
2017-07-07 09:34:13 +02:00
..
archetypes Merge commit 'dd78d5b23fe597f4461aa4199401b4e07c0612e2' as 'docs' 2017-06-26 20:46:06 +02:00
content releaser: Add release notes to /docs for release of 0.25 2017-07-07 09:29:08 +02:00
data docs: Regenerate the docs helpers 2017-07-06 10:36:13 +02:00
layouts docs: Merge docs commit '37c69054e294bf554be03cf7e4c01e1f586e6943' 2017-07-06 10:25:46 +02:00
static docs: Merge docs commit '37c69054e294bf554be03cf7e4c01e1f586e6943' 2017-07-06 10:25:46 +02:00
temp Merge commit 'dd78d5b23fe597f4461aa4199401b4e07c0612e2' as 'docs' 2017-06-26 20:46:06 +02:00
.gitignore Merge commit 'dd78d5b23fe597f4461aa4199401b4e07c0612e2' as 'docs' 2017-06-26 20:46:06 +02:00
config.toml releaser: Prepare repository for 0.26-DEV 2017-07-07 09:34:13 +02:00
README.md docs: Merge docs commit '37c69054e294bf554be03cf7e4c01e1f586e6943' 2017-07-06 10:25:46 +02:00

Hugo Docs

Documentation site for Hugo, the very fast and flexible static site generator built with love in GoLang.

Branches

  • The master branch is the current Hugo version and will be auto-deployed to gohugo.io/.
  • Anything not relevant to the current Hugo version goes into the dev branch.
  • Changes in hugo/docs will, in general, be merged once every release, but can be manually merged/cherry picked if needed. This goes both ways.
  • All contributions that is not tightly coupled with code changes, should be made directly to hugoDocs.
  • But we also merge PRs into hugo/docs, but preferably changes that is related to the code in the PR itself

To summarize, we have two branches in this repository: master (current Hugo) and dev (next Hugo).