mirror of
https://github.com/gohugoio/hugo.git
synced 2025-09-02 22:52:51 +02:00
Merge commit '5be51ac3db225d5df501ed1fa1499c41d97dbf65'
This commit is contained in:
@@ -1,14 +1,8 @@
|
||||
---
|
||||
title: Taxonomies
|
||||
description: Hugo includes support for user-defined taxonomies.
|
||||
categories: [content management]
|
||||
keywords: [taxonomies,metadata,front matter,terms]
|
||||
menu:
|
||||
docs:
|
||||
parent: content-management
|
||||
weight: 150
|
||||
weight: 150
|
||||
toc: true
|
||||
categories: []
|
||||
keywords: []
|
||||
aliases: [/taxonomies/overview/,/taxonomies/usage/,/indexes/overview/,/doc/indexes/,/extras/indexes]
|
||||
---
|
||||
|
||||
@@ -19,24 +13,24 @@ Hugo includes support for user-defined groupings of content called **taxonomies*
|
||||
### Definitions
|
||||
|
||||
Taxonomy
|
||||
: a categorization that can be used to classify content
|
||||
: A categorization that can be used to classify content
|
||||
|
||||
Term
|
||||
: a key within the taxonomy
|
||||
: A key within the taxonomy
|
||||
|
||||
Value
|
||||
: a piece of content assigned to a term
|
||||
: A piece of content assigned to a term
|
||||
|
||||
## Example taxonomy: movie website
|
||||
|
||||
Let's assume you are making a website about movies. You may want to include the following taxonomies:
|
||||
|
||||
* Actors
|
||||
* Directors
|
||||
* Studios
|
||||
* Genre
|
||||
* Year
|
||||
* Awards
|
||||
- Actors
|
||||
- Directors
|
||||
- Studios
|
||||
- Genre
|
||||
- Year
|
||||
- Awards
|
||||
|
||||
Then, in each of the movies, you would specify terms for each of these taxonomies (i.e., in the [front matter] of each of your movie content files). From these terms, Hugo would automatically create pages for each Actor, Director, Studio, Genre, Year, and Award, with each listing all of the Movies that matched that specific Actor, Director, Studio, Genre, Year, and Award.
|
||||
|
||||
@@ -75,60 +69,16 @@ Moonrise Kingdom <- Value
|
||||
...
|
||||
```
|
||||
|
||||
## Default taxonomies
|
||||
|
||||
Hugo natively supports taxonomies.
|
||||
|
||||
Without adding a single line to your [site configuration] file, Hugo will automatically create taxonomies for `tags` and `categories`. That would be the same as manually [configuring your taxonomies](#configure-taxonomies) as below:
|
||||
|
||||
{{< code-toggle config=taxonomies />}}
|
||||
|
||||
If you do not want Hugo to create any taxonomies, set `disableKinds` in your [site configuration] to the following:
|
||||
|
||||
{{< code-toggle file=hugo >}}
|
||||
disableKinds = ["taxonomy","term"]
|
||||
{{</ code-toggle >}}
|
||||
|
||||
{{% include "content-management/_common/page-kinds.md" %}}
|
||||
|
||||
### Default destinations
|
||||
|
||||
When taxonomies are used---and [taxonomy templates] are provided---Hugo will automatically create both a page listing all the taxonomy's terms and individual pages with lists of content associated with each term. For example, a `categories` taxonomy declared in your configuration and used in your content front matter will create the following pages:
|
||||
|
||||
* A single page at `example.com/categories/` that lists all the terms within the taxonomy
|
||||
* [Individual taxonomy list pages][taxonomy templates] (e.g., `/categories/development/`) for each of the terms that shows a listing of all pages marked as part of that taxonomy within any content file's [front matter]
|
||||
- A single page at `example.com/categories/` that lists all the terms within the taxonomy
|
||||
- [Individual taxonomy list pages][taxonomy templates] (e.g., `/categories/development/`) for each of the terms that shows a listing of all pages marked as part of that taxonomy within any content file's [front matter]
|
||||
|
||||
## Configure taxonomies
|
||||
## Configuration
|
||||
|
||||
Custom taxonomies other than the [defaults](#default-taxonomies) must be defined in your [site configuration] before they can be used throughout the site. You need to provide both the plural and singular labels for each taxonomy. For example, `singular key = "plural value"` for TOML and `singular key: "plural value"` for YAML.
|
||||
|
||||
### Example: adding a custom taxonomy named "series"
|
||||
|
||||
{{% note %}}
|
||||
While adding custom taxonomies, you need to put in the default taxonomies too, _if you want to keep them_.
|
||||
{{% /note %}}
|
||||
|
||||
{{< code-toggle file=hugo >}}
|
||||
[taxonomies]
|
||||
tag = "tags"
|
||||
category = "categories"
|
||||
series = "series"
|
||||
{{</ code-toggle >}}
|
||||
|
||||
### Example: removing default taxonomies
|
||||
|
||||
If you want to have just the default `tags` taxonomy, and remove the `categories` taxonomy for your site, you can do so by modifying the `taxonomies` value in your [site configuration].
|
||||
|
||||
{{< code-toggle file=hugo >}}
|
||||
[taxonomies]
|
||||
tag = "tags"
|
||||
{{</ code-toggle >}}
|
||||
|
||||
If you want to disable all taxonomies altogether, see the use of `disableKinds` in [Hugo Taxonomy Defaults](#default-taxonomies).
|
||||
|
||||
{{% note %}}
|
||||
You can add content and front matter to your taxonomy list and taxonomy terms pages. See [Content Organization](/content-management/organization/) for more information on how to add an `_index.md` for this purpose.
|
||||
{{% /note %}}
|
||||
See [configure taxonomies](/configuration/taxonomies/).
|
||||
|
||||
## Assign terms to content
|
||||
|
||||
@@ -148,7 +98,7 @@ The following show a piece of content that has a weight of 22, which can be used
|
||||
|
||||
### Example: taxonomic `weight`
|
||||
|
||||
{{< code-toggle >}}
|
||||
{{< code-toggle file=hugo >}}
|
||||
title = "foo"
|
||||
tags = [ "a", "b", "c" ]
|
||||
tags_weight = 22
|
||||
@@ -172,4 +122,4 @@ wikipedia: "https://en.wikipedia.org/wiki/Bruce_Willis"
|
||||
[documentation on archetypes]: /content-management/archetypes/
|
||||
[front matter]: /content-management/front-matter/
|
||||
[taxonomy templates]: /templates/types/#taxonomy
|
||||
[site configuration]: /getting-started/configuration/
|
||||
[site configuration]: /configuration/
|
||||
|
Reference in New Issue
Block a user