TheCloud/hugoDocs
1
0
Fork 0
mirror of https://github.com/gohugoio/hugoDocs.git synced 2025-09-13 17:55:16 -04:00
Code Issues Packages Projects Releases Wiki Activity

Explain use of disableKinds to remove default taxonomy

Browse Source 
Fixes rdwatters/hugo-docs-concept#158
This commit is contained in:
Ryan Watters 2017-07-03 14:42:38 -05:00 committed by Anthony Fok
parent 73d616c56b
commit 469e504c7e
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
config.toml
View File

@ -81,7 +81,7 @@ twitter = "GoHugoIO"
## As of v0.20, all content files include a default "categories" value that's the same as the section. This was a cheap future-proofing method and should/could be changed accordingly. ## As of v0.20, all content files include a default "categories" value that's the same as the section. This was a cheap future-proofing method and should/could be changed accordingly.
[taxonomies] [taxonomies]
tag = "tags" tag = "tags"
category = "categories"
# High level items # High level items

10
content/content-management/taxonomies.md
View File

@ -84,13 +84,13 @@ Moonrise Kingdom <- Content
## Hugo Taxonomy Defaults ## Hugo Taxonomy Defaults
Hugo natively supports taxonomies, which means there are architectural patterns for rendering your project's taxonomies baked into Hugo's core. Hugo natively supports taxonomies, which means there are architectural patterns for rendering your project's taxonomies baked into Hugo's core.
{{% note %}} Without adding a single line to your site's configuration file, Hugo will automatically create taxonomies for `tags` and `categories`. If you do not want Hugo to create these taxonomies---even though the values may be added to your content files' front matter---set `disableKinds` in your site's configuration to the following:
Users of versions older than v0.20 may notice that Hugo built `/tags` and `/categories` as long as these fields were called in at least a single content file. A previous hack involved setting these values to empty strings. This is *not* a proper workaround.
As of v0.20, Hugo does *not* automatically generate default taxonomies for your site. If your site configuration contains no key-values in the taxonomies field, Hugo will not build anything. ```toml
{{% /note %}} disableKinds = ["taxonomy","taxonomyTerm"]
```
### Default Destinations ### Default Destinations