github/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2024-11-21 20:46:30 -05:00
Code Issues Projects Releases Packages Wiki Activity
hugo/docs
History
Bjørn Erik Pedersen 4c220c4ac2 Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 
Fixes #3709
2017-07-18 10:33:58 +02:00
..
archetypes Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
content Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
data Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
layouts/shortcodes Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
static Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
temp Merge commit 'dd78d5b23fe597f4461aa4199401b4e07c0612e2' as 'docs' 2017-06-26 20:46:06 +02:00
themes Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
.gitignore Merge commit 'dd78d5b23fe597f4461aa4199401b4e07c0612e2' as 'docs' 2017-06-26 20:46:06 +02:00
.gitmodules Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
config.toml Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
LICENSE.md Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
netlify.toml Merge commit '6dbde8d731f221b027c0c60b772ba82dad759943' 2017-07-18 10:33:58 +02:00
README.md docs: Merge docs commit '37c69054e294bf554be03cf7e4c01e1f586e6943' 2017-07-06 10:25:46 +02:00

README.md

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).