mirror/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2025-08-29 22:29:56 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge commit 'efa74c5c6e6ff1daddeb5834ea7c69bed2acf171'

Browse Source
This commit is contained in:
Bjørn Erik Pedersen
2020-06-16 14:19:31 +02:00
parent 6408c1cbc8 efa74c5c6e
commit 0a9172672a
74 changed files with 112 additions and 156 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/content/en/hugo-modules/configuration.md
View File

@@ -58,7 +58,7 @@ Any of the above can be omitted.
min
: The minimum Hugo version supported, e.g. `0.55.0`
max
max
: The maximum Hugo version supported, e.g. `0.55.0`
extended
@@ -73,7 +73,7 @@ extended
ignoreConfig = false
disable = false
[[module.imports]]
path = "my-shortcodes"
path = "my-shortcodes"
{{< /code-toggle >}}
path

8
docs/content/en/hugo-modules/use-modules.md
View File

@@ -33,10 +33,10 @@ hugo mod init github.com/gohugoio/myShortcodes
Also see the [CLI Doc](/commands/hugo_mod_init/).
## Use a Module for a Theme
The easiest way to use a for a theme is to import it in the config.
The easiest way to use a Module for a theme is to import it in the config.
1. Initialize the hugo module system: `hugo mod init github.com/<your_user>/<your_project>`
2. Import the theme in your `config.toml`:
2. Import the theme in your `config.toml`:
```toml
[module]
@@ -87,7 +87,7 @@ One way to do local development of a module imported in a project is to add a re
replace github.com/bep/hugotestmods/mypartials => /Users/bep/hugotestmods/mypartials
```
If you have the `hugo server` running, the configuration will be reloaded and `/Users/bep/hugotestmods/mypartials` put on the watch list.
If you have the `hugo server` running, the configuration will be reloaded and `/Users/bep/hugotestmods/mypartials` put on the watch list.
## Print Dependency Graph
@@ -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: