From 4ac6e828100c5b250f5fb0dbcea71164fbb5fe75 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B8rn=20Erik=20Pedersen?= Date: Sun, 16 Jul 2017 14:38:15 +0200 Subject: [PATCH] Update content references to new gohugoio org --- content/about/roadmap.md | 12 +-- content/about/what-is-hugo.md | 2 +- content/content-management/archetypes.md | 2 +- content/content-management/formats.md | 4 +- content/content-management/organization.md | 2 +- content/content-management/taxonomies.md | 6 +- content/content-management/toc.md | 2 +- content/content-management/types.md | 2 +- content/contribute/_index.md | 2 +- content/contribute/development.md | 24 ++--- content/contribute/documentation.md | 4 +- content/contribute/themes.md | 2 +- content/functions/base64.md | 4 +- content/functions/emojify.md | 2 +- content/functions/findRe.md | 2 +- content/functions/param.md | 2 +- .../getting-started/directory-structure.md | 2 +- content/getting-started/quick-start.md | 2 +- .../hosting-on-bitbucket.md | 2 +- content/mailing-list.md | 2 +- content/news/0-16.md | 2 +- content/news/0-19.md | 2 +- content/news/0-20-1.md | 8 +- content/news/0-20-2.md | 2 +- content/news/0-20-3.md | 8 +- content/news/0-20-4.md | 10 +- content/news/0-20-5.md | 2 +- content/news/0-20-6.md | 10 +- content/news/0-20-7.md | 6 +- content/news/0-20.md | 58 ++++++------ content/news/0-21.md | 92 +++++++++---------- content/news/0-22-1.md | 12 +-- content/news/0-22.md | 62 ++++++------- content/news/press-and-articles.md | 2 +- content/news/release-notes.md | 18 ++-- content/templates/alternatives.md | 2 +- content/templates/files.md | 8 +- content/templates/internal.md | 2 +- content/templates/menu-templates.md | 2 +- content/templates/shortcode-templates.md | 2 +- content/templates/taxonomy-templates.md | 2 +- content/themes/installing-and-using-themes.md | 6 +- content/tools/migrations.md | 2 +- content/tools/starter-kits.md | 2 +- content/troubleshooting/eof-error.md | 2 +- 45 files changed, 203 insertions(+), 203 deletions(-) diff --git a/content/about/roadmap.md b/content/about/roadmap.md index 678013ba4..0bc0b02aa 100644 --- a/content/about/roadmap.md +++ b/content/about/roadmap.md @@ -34,16 +34,16 @@ In no particular order, here are some other features currently being worked on: Feel free to [contribute to Hugo's development][devcontribute], [improve Hugo's documentation][doccontribute], or [open a new issue][newissue] if you have an idea for a new feature. -[#98]: https://github.com/spf13/hugo/issues/98 -[#1014]: https://github.com/spf13/hugo/issues/1014 -[#1435]: https://github.com/spf13/hugo/issues/1435 -[#1436]: https://github.com/spf13/hugo/issues/1436 +[#98]: https://github.com/gohugoio/hugo/issues/98 +[#1014]: https://github.com/gohugoio/hugo/issues/1014 +[#1435]: https://github.com/gohugoio/hugo/issues/1435 +[#1436]: https://github.com/gohugoio/hugo/issues/1436 [devcontribute]: /contribute/development/ [doccontribute]: /contribute/documentation/ [hosting and deployment]: /hosting-and-deployment/ [migrate]: /tools/migrations/ -[milestones]: https://github.com/spf13/hugo/milestone/14 -[newissue]: https://github.com/spf13/hugo/issues/ +[milestones]: https://github.com/gohugoio/hugo/milestone/14 +[newissue]: https://github.com/gohugoio/hugo/issues/ [related forum thread]: https://disourse.gohugo.io/t/web-based-editor/155 [themes]: /themes/ [themescontrib]: /contribute/themes/ diff --git a/content/about/what-is-hugo.md b/content/about/what-is-hugo.md index 5499415ad..c61fa2d40 100644 --- a/content/about/what-is-hugo.md +++ b/content/about/what-is-hugo.md @@ -46,7 +46,7 @@ Hugo is for people building a blog, a company site, a portfolio site, documentat [Amazon S3]: http://aws.amazon.com/s3/ [Azure]: https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/ [CloudFront]: http://aws.amazon.com/cloudfront/ "Amazon CloudFront" -[contributing to it]: https://github.com/spf13/hugo +[contributing to it]: https://github.com/gohugoio/hugo [DreamHost]: http://www.dreamhost.com/ [Firebase]: https://firebase.google.com/docs/hosting/ "Firebase static hosting" [GitHub Pages]: https://pages.github.com/ diff --git a/content/content-management/archetypes.md b/content/content-management/archetypes.md index df91793b6..f58f5aeee 100644 --- a/content/content-management/archetypes.md +++ b/content/content-management/archetypes.md @@ -139,7 +139,7 @@ title = "my new post" We see that the `title` and `date` key-values have been added in addition to the `tags` and `categories` key-values from `archetypes/default.md`. {{% note "Ordering of Front Matter" %}} -You may notice that content files created with `hugo new` do not respect the order of the key-values specified in your archetype files. This is a [known issue](https://github.com/spf13/hugo/issues/452). +You may notice that content files created with `hugo new` do not respect the order of the key-values specified in your archetype files. This is a [known issue](https://github.com/gohugoio/hugo/issues/452). {{% /note %}} ## Custom Archetypes diff --git a/content/content-management/formats.md b/content/content-management/formats.md index a963500ea..ac9099426 100644 --- a/content/content-management/formats.md +++ b/content/content-management/formats.md @@ -107,7 +107,7 @@ markdown: mmark ``` {{% warning %}} -Thare are some features not available in Mmark; one example being that shortcodes are not translated when used in an included `.mmark` file ([#3131](https://github.com/spf13/hugo/issues/3137)), and `EXTENSION_ABBREVIATION` ([#1970](https://github.com/spf13/hugo/issues/1970)) and the aforementioned GFM todo lists ([#2270](https://github.com/spf13/hugo/issues/2270)) are not fully supported. Contributions are welcome. +Thare are some features not available in Mmark; one example being that shortcodes are not translated when used in an included `.mmark` file ([#3131](https://github.com/gohugoio/hugo/issues/3137)), and `EXTENSION_ABBREVIATION` ([#1970](https://github.com/gohugoio/hugo/issues/1970)) and the aforementioned GFM todo lists ([#2270](https://github.com/gohugoio/hugo/issues/2270)) are not fully supported. Contributions are welcome. {{% /warning %}} ## MathJax with Hugo @@ -231,7 +231,7 @@ Markdown syntax is simple enough to learn in a single sitting. The following are [emojis]: https://www.webpagefx.com/tools/emoji-cheat-sheet/ [fireball]: https://daringfireball.net/projects/markdown/ [gfmtasks]: https://guides.github.com/features/mastering-markdown/#syntax -[helperssource]: https://github.com/spf13/hugo/blob/77c60a3440806067109347d04eb5368b65ea0fe8/helpers/general.go#L65 +[helperssource]: https://github.com/gohugoio/hugo/blob/77c60a3440806067109347d04eb5368b65ea0fe8/helpers/general.go#L65 [hl]: /tools/syntax-highlighting/ [hlsc]: /content-management/shortcodes/#highlight [hugocss]: /css/style.css diff --git a/content/content-management/organization.md b/content/content-management/organization.md index 73732f86d..dc8dc89cd 100644 --- a/content/content-management/organization.md +++ b/content/content-management/organization.md @@ -124,7 +124,7 @@ http://yoursite.com/events/chicago/lollapalooza/ ``` {{% note %}} -As of v0.20, Hugo does not recognize nested sections. While you can nest as many content *directories* as you'd like, any child directory of a section will still be considered the same section as that of its parents. Therefore, in the above example, `{{.Section}}` for `lollapalooza.md` is `events` and *not* `chicago`. See the [related issue on GitHub](https://github.com/spf13/hugo/issues/465). +As of v0.20, Hugo does not recognize nested sections. While you can nest as many content *directories* as you'd like, any child directory of a section will still be considered the same section as that of its parents. Therefore, in the above example, `{{.Section}}` for `lollapalooza.md` is `events` and *not* `chicago`. See the [related issue on GitHub](https://github.com/gohugoio/hugo/issues/465). {{% /note %}} ## Paths Explained diff --git a/content/content-management/taxonomies.md b/content/content-management/taxonomies.md index 6af129732..d809fdcbd 100644 --- a/content/content-management/taxonomies.md +++ b/content/content-management/taxonomies.md @@ -152,7 +152,7 @@ tags = [ "Development", "Go", "fast", "Blogging" ] categories = [ "Development" ] series = [ "Go Web Dev" ] slug = "hugo" -project_url = "https://github.com/spf13/hugo" +project_url = "https://github.com/gohugoio/hugo" +++ ``` @@ -165,7 +165,7 @@ title: "Hugo: A fast and flexible static site generator" categories: ["Development"] categories: ["Go Web Dev"] slug: "hugo" -project_url: "https://github.com/spf13/hugo" +project_url: "https://github.com/gohugoio/hugo" --- ``` @@ -187,7 +187,7 @@ project_url: "https://github.com/spf13/hugo" "Go Web Dev" ], "slug": "hugo", - "project_url": "https://github.com/spf13/hugo" + "project_url": "https://github.com/gohugoio/hugo" } ``` diff --git a/content/content-management/toc.md b/content/content-management/toc.md index 52ae51845..de4d9266a 100644 --- a/content/content-management/toc.md +++ b/content/content-management/toc.md @@ -18,7 +18,7 @@ toc: true --- {{% note "TOC Heading Levels are Fixed" %}} -Currently, the `{{.TableOfContents}}` [page variable](/variables/page/) does not allow you to specify which heading levels you want the TOC to render. [See the related GitHub discussion (#1778)](https://github.com/spf13/hugo/issues/1778). As such, the resulting `` is going to start at `

` when pulling from `{{.Content}}`. +Currently, the `{{.TableOfContents}}` [page variable](/variables/page/) does not allow you to specify which heading levels you want the TOC to render. [See the related GitHub discussion (#1778)](https://github.com/gohugoio/hugo/issues/1778). As such, the resulting `` is going to start at `

` when pulling from `{{.Content}}`. {{% /note %}} ## Usage diff --git a/content/content-management/types.md b/content/content-management/types.md index 106ab4a25..0c6754a11 100644 --- a/content/content-management/types.md +++ b/content/content-management/types.md @@ -69,7 +69,7 @@ If you have multiple content files in your `events` directory that are of the `s {{% /note %}} {{% warning %}} -With the "everything is a page" data model introduced in v0.18 (see [Content Organization](/content-management/organization/)), you can use `_index.md` in content directories to add both content and front matter to [list pages](/templates/lists/). However, `type` and `layout` declared in the front matter of `_index.md` are *not* currently respected at build time as of v0.19. This is a known issue [(#3005)](https://github.com/spf13/hugo/issues/3005). +With the "everything is a page" data model introduced in v0.18 (see [Content Organization](/content-management/organization/)), you can use `_index.md` in content directories to add both content and front matter to [list pages](/templates/lists/). However, `type` and `layout` declared in the front matter of `_index.md` are *not* currently respected at build time as of v0.19. This is a known issue [(#3005)](https://github.com/gohugoio/hugo/issues/3005). {{% /warning %}} ### Create Views diff --git a/content/contribute/_index.md b/content/contribute/_index.md index 0dd6a60f1..1df15f6c9 100644 --- a/content/contribute/_index.md +++ b/content/contribute/_index.md @@ -20,4 +20,4 @@ toc: false Hugo relies heavily on the enthusiasm and participation of the open-source community. We need your support in both its development and documentation. -Hugo's contribution guidelines are [detailed in a `CONTRIBUTING.md`](https://github.com/spf13/hugo/blob/master/CONTRIBUTING.md) in the Hugo source repository on GitHub. +Hugo's contribution guidelines are [detailed in a `CONTRIBUTING.md`](https://github.com/gohugoio/hugo/blob/master/CONTRIBUTING.md) in the Hugo source repository on GitHub. diff --git a/content/contribute/development.md b/content/contribute/development.md index d30d41f2e..832960ec7 100644 --- a/content/contribute/development.md +++ b/content/contribute/development.md @@ -133,12 +133,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: ```sh -go get -v -u github.com/spf13/hugo +go get -v -u github.com/gohugoio/hugo ``` ### Fork the repository @@ -149,7 +149,7 @@ If you're not fimiliar 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](/images/contribute/development/forking-a-repository.png) @@ -160,7 +160,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: @@ -192,8 +192,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) ``` ## The Hugo Git Contribution Workflow @@ -247,7 +247,7 @@ The Go code styleguide maybe is opiniated but it ensures that the codebase looks go fmt ./... ``` -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 @@ -358,7 +358,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 labeld with "New pull request". But GitHub is clever and probably suggests you a pull request like in the beige box below: @@ -374,7 +374,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. ![Automic builds and their status](/images/contribute/development/ci-errors.png) @@ -398,7 +398,7 @@ Feel free to [open an issue][newissue] if you think you found a bug or you have [codecademy]: https://www.codecademy.com/learn/learn-git -[contributors]: https://github.com/spf13/hugo/graphs/contributors +[contributors]: https://github.com/gohugoio/hugo/graphs/contributors [docscontrib]: /contribute/documentation/ [forums]: https://discourse.gohugo.io [gitbook]: https://git-scm.com/ @@ -406,8 +406,8 @@ Feel free to [open an issue][newissue] if you think you found a bug or you have [godl]: https://golang.org/dl/ [goinstall]: https://golang.org/doc/install [gvm]: https://github.com/moovweb/gvm -[issues]: https://github.com/spf13/hugo/issues -[newissue]: https://github.com/spf13/hugo/issues/new +[issues]: https://github.com/gohugoio/hugo/issues +[newissue]: https://github.com/gohugoio/hugo/issues/new [releases]: /getting-started/ [setupgopath]: https://golang.org/doc/code.html#Workspaces [thinkful]: https://www.thinkful.com/learn/github-pull-request-tutorial/ diff --git a/content/contribute/documentation.md b/content/contribute/documentation.md index 237a3af11..e4fe0f7b9 100644 --- a/content/contribute/documentation.md +++ b/content/contribute/documentation.md @@ -39,7 +39,7 @@ hugo new /.md ``` {{% note "`title:`, `date:`, and Field Order" %}} -`title` and `date` fields are added automatically when using archetypes via `hugo new`. Do not be worried if the order of the new file's front matter fields on your local machine is different than that of the examples provided in the Hugo docs. This is a known issue [(#452)](https://github.com/spf13/hugo/issues/452). +`title` and `date` fields are added automatically when using archetypes via `hugo new`. Do not be worried if the order of the new file's front matter fields on your local machine is different than that of the examples provided in the Hugo docs. This is a known issue [(#452)](https://github.com/gohugoio/hugo/issues/452). {{% /note %}} ### Adding a New Function @@ -382,7 +382,7 @@ Similar to [contributing to Hugo development](/contribute/development/), the Hug [archetypes]: /content-management/archetypes/ [bqsyntax]: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#blockquotes [charcount]: http://www.lettercount.com/ -[`docs/static/images/showcase/`]: https://github.com/spf13/hugo/tree/master/docs/static/images/showcase/ +[`docs/static/images/showcase/`]: https://github.com/gohugoio/hugo/tree/master/docs/static/images/showcase/ [ghforking]: https://help.github.com/articles/fork-a-repo/ [hugodev]: /contribute/development/ [shortcodeparams]: content-management/shortcodes/#shortcodes-without-markdown diff --git a/content/contribute/themes.md b/content/contribute/themes.md index 1384276b9..a4cb865ed 100644 --- a/content/contribute/themes.md +++ b/content/contribute/themes.md @@ -151,4 +151,4 @@ If you add screenshots to the README, please make use of absolute file paths ins {{% /note %}} [artistexample]: https://github.com/digitalcraftsman/hugo-artists-theme/tree/master/exampleSite -[themeissuenew]: https://github.com/spf13/hugoThemes/issues/new \ No newline at end of file +[themeissuenew]: https://github.com/gohugoio/hugoThemes/issues/new \ No newline at end of file diff --git a/content/functions/base64.md b/content/functions/base64.md index f0bdc83eb..1b5a3c029 100644 --- a/content/functions/base64.md +++ b/content/functions/base64.md @@ -50,8 +50,8 @@ Using base64 to decode and encode becomes really powerful if we have to handle responses from APIs. ```golang -{{ $resp := getJSON "https://api.github.com/repos/spf13/hugo/readme" }} +{{ $resp := getJSON "https://api.github.com/repos/gohugoio/hugo/readme" }} {{ $resp.content | base64Decode | markdownify }} ``` -The response of the GitHub API contains the base64-encoded version of the [README.md](https://github.com/spf13/hugo/blob/master/README.md) in the Hugo repository. Now we can decode it and parse the Markdown. The final output will look similar to the rendered version on GitHub. +The response of the GitHub API contains the base64-encoded version of the [README.md](https://github.com/gohugoio/hugo/blob/master/README.md) in the Hugo repository. Now we can decode it and parse the Markdown. The final output will look similar to the rendered version on GitHub. diff --git a/content/functions/emojify.md b/content/functions/emojify.md index 8228d75c1..def7f4676 100644 --- a/content/functions/emojify.md +++ b/content/functions/emojify.md @@ -35,4 +35,4 @@ I :heart: Hugo! [config]: /getting-started/configuration/ [emojis]: http://www.emoji-cheat-sheet.com/ [sc]: /templates/shortcode-templates/ -[scsource]: https://github.com/spf13/hugo/tree/master/docs/layouts/shortcodes +[scsource]: https://github.com/gohugoio/hugo/tree/master/docs/layouts/shortcodes diff --git a/content/functions/findRe.md b/content/functions/findRe.md index 9797a875c..34cb27520 100644 --- a/content/functions/findRe.md +++ b/content/functions/findRe.md @@ -42,7 +42,7 @@ Hugo uses Golang's [Regular Expression package](https://golang.org/pkg/regexp/), If you are just learning RegEx, or at least Golang's flavor, you can practice pattern matching in the browser at . {{% /note %}} - + +code: https://github.com/gohugoio/hugo/blob/e445c35d6a0c7f5fc2f90f31226cd1d46e048bbc/tpl/template_embedded.go#L147 --> {{% warning %}} While the following internal templates are called similar to partials, they do *not* observe the partial template lookup order. diff --git a/content/templates/menu-templates.md b/content/templates/menu-templates.md index 0be6aaef0..791825d16 100644 --- a/content/templates/menu-templates.md +++ b/content/templates/menu-templates.md @@ -55,7 +55,7 @@ The following is an example: {{end}} {{end}} -
  • Questions and Issues
    • +
  • Questions and Issues
  • Edit this Page
    • diff --git a/content/templates/shortcode-templates.md b/content/templates/shortcode-templates.md index 74d57a688..272483828 100644 --- a/content/templates/shortcode-templates.md +++ b/content/templates/shortcode-templates.md @@ -359,7 +359,7 @@ More shortcode examples can be found in the [shortcodes directory for spf13.com] [config]: /getting-started/configuration/ "Learn more about Hugo's built-in configuration variables as well as how to us your site's configuration file to include global key-values that can be used throughout your rendered website." [Content Management: Shortcodes]: /content-management/shortcodes/#using-hugo-s-built-in-shortcodes "Check this section if you are not familiar with the definition of what a shortcode is or if you are unfamiliar with how to use Hugo's built-in shortcodes in your content files." [source organization]: /getting-started/directory-structure/#directory-structure-explained "Learn how Hugo scaffolds new sites and what it expects to find in each of your directories." -[docsshortcodes]: https://github.com/spf13/hugo/tree/master/docs/layouts/shortcodes "See the shortcode source directory for the documentation site you're currently reading." +[docsshortcodes]: https://github.com/gohugoio/hugo/tree/master/docs/layouts/shortcodes "See the shortcode source directory for the documentation site you're currently reading." [figure]: /content-management/shortcodes/#figure [hugosc]: /content-management/shortcodes/#using-hugo-s-built-in-shortcodes [lookup order]: /templates/lookup-order/ "See the order in which Hugo traverses your template files to decide where and how to render your content at build time" diff --git a/content/templates/taxonomy-templates.md b/content/templates/taxonomy-templates.md index fc71a7198..c3e12400d 100644 --- a/content/templates/taxonomy-templates.md +++ b/content/templates/taxonomy-templates.md @@ -18,7 +18,7 @@ aliases: [/taxonomies/displaying/,/templates/terms/,/indexes/displaying/,/taxono toc: true --- - Hugo includes support for user-defined groupings of content called **taxonomies**. Taxonomies are classifications that demonstrate logical relationships between content. See [Taxonomies under Content Management](/content-management/taxonomies) if you are unfamiliar with how Hugo leverages this powerful feature. diff --git a/content/themes/installing-and-using-themes.md b/content/themes/installing-and-using-themes.md index 05294653e..e2c1eed31 100644 --- a/content/themes/installing-and-using-themes.md +++ b/content/themes/installing-and-using-themes.md @@ -30,7 +30,7 @@ Hugo currently doesn’t ship with a “default” theme. This decision is inten ## Installing Themes -The community-contributed themes featured on [themes.gohugo.io](//themes.gohugo.io/) are hosted in a [centralized GitHub repository][themesrepo]. The Hugo Themes Repo at is really a meta repository that contains pointers to a set of contributed themes. +The community-contributed themes featured on [themes.gohugo.io](//themes.gohugo.io/) are hosted in a [centralized GitHub repository][themesrepo]. The Hugo Themes Repo at is really a meta repository that contains pointers to a set of contributed themes. {{% warning "Get `git` First" %}} Without [Git](https://git-scm.com/) installed on your computer, none of the following theme instructions will work. Git tutorials are beyond the scope of the Hugo docs, but [GitHub](https://try.github.io/) and [codecademy](https://www.codecademy.com/learn/learn-git) offer free, interactive courses for beginners. @@ -41,7 +41,7 @@ Without [Git](https://git-scm.com/) installed on your computer, none of the foll You can install *all* available Hugo themes by cloning the entire [Hugo Theme repository on GitHub][themesrepo] from within your working directory. Depending on your internet connection the download of all themes might take a while. ```bash -git clone --depth 1 --recursive https://github.com/spf13/hugoThemes.git themes +git clone --depth 1 --recursive https://github.com/gohugoio/hugoThemes.git themes ``` Before you use a theme, remove the .git folder in that theme's root folder. Otherwise, this will cause problem if you deploy using Git. @@ -111,4 +111,4 @@ The `themename` in the above examples must match the name of the specific theme [flag]: /getting-started/usage/ "See the full list of flags in Hugo's basic usage." [install]: /getting-started/installing/ [config]: /getting-started/configuration/ "Learn how to customize your Hugo website configuration file in yaml, toml, or json." -[themesrepo]: https://github.com/spf13/hugoThemes \ No newline at end of file +[themesrepo]: https://github.com/gohugoio/hugoThemes \ No newline at end of file diff --git a/content/tools/migrations.md b/content/tools/migrations.md index 489fbd5b4..227bdd222 100644 --- a/content/tools/migrations.md +++ b/content/tools/migrations.md @@ -20,7 +20,7 @@ toc: true This section highlights some projects around Hugo that are independently developed. These tools try to extend the functionality of our static site generator or help you to get started. {{% note %}} -Do you know or maintain a similar project around Hugo? Feel free to open a [pull request](https://github.com/spf13/hugo/pulls) on GitHub if you think it should be added. +Do you know or maintain a similar project around Hugo? Feel free to open a [pull request](https://github.com/gohugoio/hugo/pulls) on GitHub if you think it should be added. {{% /note %}} Take a look at this list of migration tools if you currently use other logging tools like Jekyll or WordPress but intend to switch to Hugo instead. They'll take care to export your content into Hugo-friendly formats. diff --git a/content/tools/starter-kits.md b/content/tools/starter-kits.md index 1f30bf873..5d43d4e4d 100644 --- a/content/tools/starter-kits.md +++ b/content/tools/starter-kits.md @@ -29,7 +29,7 @@ The following starter kits are developed by active members of the Hugo community * [hugulp][]. hugulp is a tool to optimize the assets of a Hugo website. The main idea is to recreate the famous Ruby on Rails Asset Pipeline, which minifies, concatenates and fingerprints the assets used in your website. -[addkit]: https://github.com/spf13/hugo/edit/master/docs/content/tools/starter-kits.md +[addkit]: https://github.com/gohugoio/hugo/edit/master/docs/content/tools/starter-kits.md [amp]: https://www.ampproject.org/ [Blaupause]: https://github.com/fspoettel/blaupause [GOHUGO AMP]: https://github.com/wildhaber/gohugo-amp diff --git a/content/troubleshooting/eof-error.md b/content/troubleshooting/eof-error.md index 1d372fa16..6e715cde7 100644 --- a/content/troubleshooting/eof-error.md +++ b/content/troubleshooting/eof-error.md @@ -46,4 +46,4 @@ As of v0.13, Hugo's parser has been enhanced to accommodate archetype files with ## Related Hugo Issues -* https://github.com/spf13/hugo/issues/776 +* https://github.com/gohugoio/hugo/issues/776