mirror of
https://github.com/gohugoio/hugoDocs.git
synced 2025-09-13 11:57:23 -04:00
Fixing typos, whitespace issues and links
This commit is contained in:
parent
dc82309b96
commit
f47d6f1e31
@ -56,7 +56,7 @@ There are a few alternatives to commenting on static sites for those who do not
|
||||
* [IntenseDebate](https://intensedebate.com/)
|
||||
* [Graph Comment][]
|
||||
* [Muut](https://muut.com/)
|
||||
* [isso](https://posativ.org/isso/) (Self-hosted, Python)
|
||||
* [Isso](https://posativ.org/isso/) (Self-hosted, Python)
|
||||
* [Tutorial on Implementing Isso with Hugo][issotutorial]
|
||||
* [Utterances](https://utteranc.es/) (Open source, GitHub comments widget built on GitHub issues)
|
||||
* [Remark](https://github.com/umputun/remark) (Open source, Golang, Easy to run docker)
|
||||
|
@ -28,7 +28,7 @@ The first step will be to login to your KeyCDN account and create a new zone. Na
|
||||
|
||||

|
||||
|
||||
While the origin location doesn’t exist yet, you will need to use your new Zone URL address (or [Zonealias](https://www.keycdn.com/support/create-a-zonealias/)) in the `.gitlab-ci.yml` file that will be uploaded to your GitLab project.
|
||||
While the origin location doesn’t exist yet, you will need to use your new Zone URL address (or [Zone Alias](https://www.keycdn.com/support/create-a-zone-alias/)) in the `.gitlab-ci.yml` file that will be uploaded to your GitLab project.
|
||||
|
||||
Ensure that you use your Zone URL or Zone alias as the `BASEURL` variable in the example below. This will be the user-visible website address.
|
||||
|
||||
|
@ -114,7 +114,7 @@ Also see the [CLI Doc](/commands/hugo_mod_graph/).
|
||||
|
||||
## Vendor Your Modules
|
||||
|
||||
`hugo mod vendor` will write all the module depencies to a `_vendor` folder, which will then be used for all subsequent builds.
|
||||
`hugo mod vendor` will write all the module dependencies to a `_vendor` folder, which will then be used for all subsequent builds.
|
||||
|
||||
Note that:
|
||||
|
||||
|
@ -1,5 +1,4 @@
|
||||
---
|
||||
|
||||
title: fireship.io
|
||||
date: 2019-02-02
|
||||
description: "Showcase: \"Hugo helps us create complex technical content that integrates engaging web components\""
|
||||
|
@ -15,7 +15,7 @@ Hugo addresses all these needs, coupled with [Forestry.io](https://forestry.io/)
|
||||
|
||||
|
||||
## What we liked
|
||||
- The **multilingual** content support, especially simpel to setup.
|
||||
- The **multilingual** content support, especially simple to setup.
|
||||
- The **multiple environments** support (develop, staging, test, production, ...).
|
||||
- Although a hard start with the Go language, the power of the **Hugo's templating**.
|
||||
- The **partial layouts**, including the `internals` (e.g. social metas).
|
||||
|
@ -1,15 +1,9 @@
|
||||
---
|
||||
|
||||
title: Linode Docs
|
||||
|
||||
date: 2018-02-12
|
||||
|
||||
description: "Showcase: \"Hugo allows us to build thousands of pages in seconds.\""
|
||||
|
||||
siteURL: https://linode.com/docs/
|
||||
|
||||
siteSource: https://github.com/linode/docs
|
||||
|
||||
---
|
||||
|
||||
The documentation team at Linode has been writing guides since 2009, with the goal of helping new and experienced Linux users find the best tools and get the most out of their systems.
|
||||
|
Loading…
x
Reference in New Issue
Block a user