docs: Update content references to gohugoio/hugo

docs/content/tutorials/creating-a-new-theme.md

@@ -422,7 +422,7 @@ All that's left is to add some content, as well as a theme to display it.
 
 Hugo doesn't ship with a default theme. However, a large number of themes
 are easily available: for example, at
-[hugoThemes](https://github.com/spf13/hugoThemes).
+[hugoThemes](https://github.com/gohugoio/hugoThemes).
 Also, Hugo comes with a command to generate them.
 
 We're going to generate a new theme called Zafta.

docs/content/tutorials/hosting-on-bitbucket.md

@@ -92,7 +92,7 @@ pipelines:
           script:
             - apt-get update -y && apt-get install wget
             - apt-get -y install git
-            - wget https://github.com/spf13/hugo/releases/download/v0.18/hugo_0.18-64bit.deb
+            - wget https://github.com/gohugoio/hugo/releases/download/v0.18/hugo_0.18-64bit.deb
             - dpkg -i hugo*.deb
             - git clone https://github.com/eliasson/liquorice themes/liquorice
             - hugo --theme=liquorice --baseURL https://__baseurl__ --buildDrafts

docs/content/tutorials/how-to-contribute-to-hugo.md

@@ -12,7 +12,7 @@ weight: 10
 
 ## Introduction
 
-Hugo is an open source project and lives by the work of its [contributors](https://github.com/spf13/hugo/graphs/contributors). Help to make Hugo even more awesome. There are plenty of [open issues](https://github.com/spf13/hugo/issues) on GitHub and we need your help.
+Hugo is an open source project and lives by the work of its [contributors](https://github.com/gohugoio/hugo/graphs/contributors). Help to make Hugo even more awesome. There are plenty of [open issues](https://github.com/gohugoio/hugo/issues) on GitHub and we need your help.
 
 This tutorial is intended for people who are new to Git, GitHub or open source projects in general. It should help to overcome most of the barriers that newcomers encounter. It describes step by step what you need to do.
 
@@ -98,12 +98,12 @@ We assume that you've set up your `GOPATH` (see the section above if you're unsu
 
 > When you create a repository on GitHub, it exists as a remote repository. You can create a local clone of your repository on your computer and sync between the two locations.
 
-We're going to clone the [master Hugo repository](https://github.com/spf13/hugo). That seems counter-intuitive, since you won't have commit rights on it. But it's required for the Go workflow. You'll work on a copy of the master and push your changes to your own repository on GitHub.
+We're going to clone the [master Hugo repository](https://github.com/gohugoio/hugo). That seems counter-intuitive, since you won't have commit rights on it. But it's required for the Go workflow. You'll work on a copy of the master and push your changes to your own repository on GitHub.
 
 So, let's clone that master repository with govendor:
 
 ```sh
-govendor get -v github.com/spf13/hugo
+govendor get -v github.com/gohugoio/hugo
 ```
 
 ### Fork the repository
@@ -114,7 +114,7 @@ If you're not familiar with this term, GitHub's [help pages](https://help.github
 
 #### Fork by hand
 
-Open the [Hugo repository](https://github.com/spf13/hugo) on GitHub and click on the "Fork" button in the top right.
+Open the [Hugo repository](https://github.com/gohugoio/hugo) on GitHub and click on the "Fork" button in the top right.
 
 ![Fork button](/img/tutorials/how-to-contribute-to-hugo/forking-a-repository.png)
 
@@ -125,7 +125,7 @@ Now open your fork repository on GitHub and copy the remote url of your fork. Yo
 Switch back to the terminal and move into the directory of the cloned master repository from the last step.
 
 ```sh
-cd $GOPATH/src/github.com/spf13/hugo
+cd $GOPATH/src/github.com/gohugoio/hugo
 ```
 
 Now Git needs to know that our fork exists by adding the copied remote url:
@@ -157,8 +157,8 @@ The output should look similar:
 ```sh
 digitalcraftsman	git@github.com:digitalcraftsman/hugo.git (fetch)
 digitalcraftsman	git@github.com:digitalcraftsman/hugo.git (push)
-origin	https://github.com/spf13/hugo (fetch)
-origin	https://github.com/spf13/hugo (push)
+origin	https://github.com/gohugoio/hugo (fetch)
+origin	https://github.com/gohugoio/hugo (push)
 ```
 
 
@@ -213,7 +213,7 @@ The Go code styleguide maybe is opinionated but it ensures that the codebase loo
 govendor fmt +local
 ```
 
-Once you made your additions commit your changes. Make sure that you follow our [code contribution guidelines](https://github.com/spf13/hugo/blob/master/CONTRIBUTING.md):
+Once you made your additions commit your changes. Make sure that you follow our [code contribution guidelines](https://github.com/gohugoio/hugo/blob/master/CONTRIBUTING.md):
 
 ```sh
 # Add all changed files
@@ -322,7 +322,7 @@ If you modified your commit history in the last step GitHub will reject your try
 
 ## Open a pull request
 
-We made a lot of progress. Good work. In this step we finally open a pull request to submit our additions. Open the [Hugo master repository](https://github.com/spf13/hugo/) on GitHub in your browser.
+We made a lot of progress. Good work. In this step we finally open a pull request to submit our additions. Open the [Hugo master repository](https://github.com/gohugoio/hugo/) on GitHub in your browser.
 
 You should find a green button labeled with "New pull request". But GitHub is clever and probably suggests you a pull request like in the beige box below:
 
@@ -339,7 +339,7 @@ Last but not least you should accept the contributor license agreement (CLA). A
 
 ### Automatic builds
 
-We use the [Travis CI loop](https://travis-ci.org/spf13/hugo) (Linux and OS X) and [AppVeyor](https://ci.appveyor.com/project/spf13/hugo/branch/master) (Windows) to compile Hugo with your additions. This should ensure that everything works as expected before merging your pull request. This in most cases only relevant if you made changes to the codebase of Hugo.
+We use the [Travis CI loop](https://travis-ci.org/gohugoio/hugo) (Linux and OS X) and [AppVeyor](https://ci.appveyor.com/project/gohugoio/hugo/branch/master) (Windows) to compile Hugo with your additions. This should ensure that everything works as expected before merging your pull request. This in most cases only relevant if you made changes to the codebase of Hugo.
 
 <img src="/img/tutorials/how-to-contribute-to-hugo/ci-errors.png" alt="Automic builds and their status">
 
@@ -349,4 +349,4 @@ If you have questions leave a comment in the pull request. We are willing to ass
 
 ## Where to start?
 
-Thank you for reading this tutorial. Hopefully, we see you again on GitHub. There are plenty of [open issues](https://github.com/spf13/hugo/issues) on GitHub. Feel free to open an issue if you think you found a bug or you have a new idea to improve Hugo. We are happy to hear from you.
+Thank you for reading this tutorial. Hopefully, we see you again on GitHub. There are plenty of [open issues](https://github.com/gohugoio/hugo/issues) on GitHub. Feel free to open an issue if you think you found a bug or you have a new idea to improve Hugo. We are happy to hear from you.

docs/content/tutorials/installing-on-mac.md

@@ -116,7 +116,7 @@ All three locations will work for you. I'm going to document the second option,
 
 ### Step 2: Download the Tarball
 
-1. Open <https://github.com/spf13/hugo/releases> in your browser.
+1. Open <https://github.com/gohugoio/hugo/releases> in your browser.
 
 2. Find the current release by scrolling down and looking for the green tag that reads "Latest Release."
 
@@ -199,13 +199,13 @@ install go`.
 ### Step 1: Get the Source
 
 If you want to compile a specific version, go to
-<https://github.com/spf13/hugo/releases> and download the source code
+<https://github.com/gohugoio/hugo/releases> and download the source code
 for the version of your choice.  If you want to compile Hugo with all
 the latest changes (which might include bugs), clone the Hugo
 repository:
 
 ```
-git clone https://github.com/spf13/hugo
+git clone https://github.com/gohugoio/hugo
 ```
 
 ### Step 2: Compiling
@@ -215,7 +215,7 @@ fetch Hugo's dependencies:
 
 ```
 mkdir -p src/github.com/spf13
-ln -sf $(pwd) src/github.com/spf13/hugo
+ln -sf $(pwd) src/github.com/gohugoio/hugo
 
 # set the build path for Go
 export GOPATH=$(pwd)

docs/content/tutorials/installing-on-windows.md

@@ -34,14 +34,14 @@ You'll need a place to store the Hugo executable, your content (the files that y
 
 ## Technical users
 
-1. Download the latest zipped Hugo executable from the [Hugo Releases](https://github.com/spf13/hugo/releases) page.
+1. Download the latest zipped Hugo executable from the [Hugo Releases](https://github.com/gohugoio/hugo/releases) page.
 2. Extract all contents to your `..\Hugo\bin` folder.
 3. The hugo executable will be named as `hugo_hugo-version_platform_arch.exe`. Rename that executable to `hugo.exe` for ease of use.
 4. In PowerShell or your preferred CLI, add the `hugo.exe` executable to your PATH by navigating to `C:\Hugo\bin` (or the location of your hugo.exe file) and use the command `set PATH=%PATH%;C:\Hugo\bin`. If the `hugo` command does not work after a reboot, you may have to run the command prompt as administrator.
 
 ## Less technical users
 
-1. Go the [Hugo Releases](https://github.com/spf13/hugo/releases) page.
+1. Go the [Hugo Releases](https://github.com/gohugoio/hugo/releases) page.
 2. The latest release is announced on top. Scroll to the bottom of the release announcement to see the downloads. They're all ZIP files.
 3. Find the Windows files near the bottom (they're in alphabetical order, so Windows is last) – download either the 32-bit or 64-bit file depending on whether you have 32-bit or 64-bit Windows. (If you don't know, [see here](https://esupport.trendmicro.com/en-us/home/pages/technical-support/1038680.aspx).)
 4. Move the ZIP file into your `C:\Hugo\bin` folder.