From 8d0345d8980674d6e9c9c4412f11b60d4b00b08c Mon Sep 17 00:00:00 2001 From: Andreas Deininger Date: Thu, 17 Sep 2020 13:03:21 +0200 Subject: [PATCH 1/2] Fixing broken links --- userguide/content/en/about/_index.md | 2 +- userguide/content/en/docs/Getting started/_index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/userguide/content/en/about/_index.md b/userguide/content/en/about/_index.md index a442c44611..f16b34d2ec 100644 --- a/userguide/content/en/about/_index.md +++ b/userguide/content/en/about/_index.md @@ -103,7 +103,7 @@ The Docsy template currently includes built-in integration with the following to ### Make it your own -You can configure the Docsy theme as much or as little as you like, anything from changing the colours and images to adding your own type of page layout. [Learn more...](docs/adding-content/lookandfeel/) +You can configure the Docsy theme as much or as little as you like, anything from changing the colours and images to adding your own type of page layout. [Learn more...](/docs/adding-content/lookandfeel/) ### Get organized diff --git a/userguide/content/en/docs/Getting started/_index.md b/userguide/content/en/docs/Getting started/_index.md index b5e54fd249..8e9767a816 100755 --- a/userguide/content/en/docs/Getting started/_index.md +++ b/userguide/content/en/docs/Getting started/_index.md @@ -65,7 +65,7 @@ Note that versions of `PostCSS` later than 5.0.1 will not load `autoprefixer` if To use the Docsy Hugo theme, you have a couple of options: -* **Copy and edit the source for the [Docsy example site](https://github.com/google/docsy-example).** This approach gives you a skeleton structure for your site, with top-level and documentation sections and templates that you can modify as necessary. The example site uses Docsy as a [Git submodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules), so it's easy to [keep up to date](#keeping-the-theme-up-to-date). +* **Copy and edit the source for the [Docsy example site](https://github.com/google/docsy-example).** This approach gives you a skeleton structure for your site, with top-level and documentation sections and templates that you can modify as necessary. The example site uses Docsy as a [Git submodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules), so it's easy to [keep up to date](/docs/updating/). * **Build your own site using the Docsy theme.** Specify the [Docsy theme](https://github.com/google/docsy) like any other [Hugo theme](https://gohugo.io/themes/) when creating or updating your site. With this option, you'll get Docsy look and feel, navigation, and other features, but you'll need to specify your own site structure. ### Option 1: Clone the Docsy example site From 86ccb00856945409e849292193d035e737fd0ab5 Mon Sep 17 00:00:00 2001 From: Andreas Deininger Date: Thu, 17 Sep 2020 17:47:15 +0200 Subject: [PATCH 2/2] Fixing broken links --- userguide/content/en/docs/Deployment/_index.md | 2 +- userguide/content/en/docs/Getting started/_index.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/userguide/content/en/docs/Deployment/_index.md b/userguide/content/en/docs/Deployment/_index.md index 5ce890231c..a3d88e80a7 100644 --- a/userguide/content/en/docs/Deployment/_index.md +++ b/userguide/content/en/docs/Deployment/_index.md @@ -24,7 +24,7 @@ If you've just added the theme as a submodule in a local version of your site an git submodule update --init --recursive {{% /alert %}} -1. Ensure you have the tools described in [Installation and Prerequisites](#installation-and-prerequisites) installed on your local machine, including `postcss-cli` (you'll need it to generate the site resources the first time you run the server). +1. Ensure you have the tools described in [Prerequisites and installation](/docs/getting-started/#prerequisites-and-installation) installed on your local machine, including `postcss-cli` (you'll need it to generate the site resources the first time you run the server). 1. Run the `hugo server` command in your site root. By default your site will be available at http://localhost:1313/. Now that you're serving your site locally, Hugo will watch for changes to the content and automatically refresh your site. If you have more than one local git branch, when you switch between git branches the local website reflects the files in the current branch. diff --git a/userguide/content/en/docs/Getting started/_index.md b/userguide/content/en/docs/Getting started/_index.md index 8e9767a816..78357b4c61 100755 --- a/userguide/content/en/docs/Getting started/_index.md +++ b/userguide/content/en/docs/Getting started/_index.md @@ -160,7 +160,7 @@ To copy the example site: Specify the [Docsy theme](https://github.com/google/docsy) like any other Hugo theme when creating or updating your site. This gives you all the theme-y goodness but you'll need to specify your own site structure. You can either use the theme as a submodule (our recommended approach for easy updates), or just clone the theme into your project's `themes` subdirectory. -Whichever approach you use, for simplicity we recommend copying and editing our [example site configuration](#configuring-your-site) for your project, or you may get Hugo errors for missing parameters and values when you try to build your site. +Whichever approach you use, for simplicity we recommend copying and editing our [example site configuration](#basic-site-configuration) for your project, or you may get Hugo errors for missing parameters and values when you try to build your site. #### Using the Docsy theme as a submodule @@ -209,7 +209,7 @@ If you want to build and/or serve your site [locally](/docs/deployment/#serving- git submodule update --init --recursive ``` -For more information, see [Install and Use Themes](https://gohugo.io/themes/installing-and-using-themes/#install-a-single-theme) on the [Hugo](https://gohugo.io) site. +For more information, see [Theme Components](https://gohugo.io/hugo-modules/theme-components/) on the [Hugo](https://gohugo.io) site. #### Preview your site