d1157b687 Fix typo -- missing word in title 34c9a9ff3 Remove Hartwell Insurance subpage broken link d42f6d8eb Fix strings.Repeat documentation 09b49debb Release 0.76.5 149877735 Merge branch 'tempv0.76.5' 72ffeb026 releaser: Add release notes to /docs for release of 0.76.5 4150d8ae8 Fixed typo: update PrevPage to Prev c3e630db1 Update index.md deb7520a8 Release 0.76.4 f58bd7134 Merge branch 'tempv0.76.4' 2581fe4bc releaser: Add release notes to /docs for release of 0.76.4 26d8417fc Release 0.76.3 34c49e06a Merge branch 'tempv0.76.3' 0de2af2ef releaser: Add release notes to /docs for release of 0.76.3 cce12c0f7 Add missing closing quotes and fix code-block lang (#1250) 8c1c80d9f Update AMP link (#1251) 7b1211ffa Fix typos in multilingual.md 29e9d70fd Update index.md 172a5480b Release 0.76.2 93ff424d3 Merge branch 'temp762' 3cad3c23a releaser: Add release notes to /docs for release of 0.76.2 610221964 Update index.md 8a9d31709 Release 0.76.1 64b245aa4 Merge branch 'temp761' f19469ff8 releaser: Add release notes to /docs for release of 0.76.1 97f0ed030 Update front-matter.md cca71f263 Update index.md 23c64f6a3 Fix typo in 0.76.0 release note 5f79e034d Update index.md b66567de2 netlify: Bump to Hugo 0.76.0 a3e30300d Release 0.76.0 3b057e8fe releaser: Add release notes to /docs for release of 0.76.0 7fa1cd912 docs: Regen docshelper 769712aec Merge commit 'e5568488051a571df48401e03f1304b95dbc9028' 70ce6ae33 pagemeta: Make BuildConfig.Render an enum a78d3849f Allow cascade to be a slice with a _target discriminator 705fea656 Add force flag to server redirects config 04e4e1cc1 tpl: Add Do Not Track (dnt) option to Vimeo shortcode 025c19fe1 Fix CLI example for PostCSS 8 0c70c47b2 markup/asciidocext: Add preserveTOC option git-subtree-dir: docs git-subtree-split: d1157b687e25054501c3bcbb735da51229f66b74
8.8 KiB
title | linktitle | description | date | publishdate | keywords | categories | menu | weight | draft | aliases | toc | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Taxonomies | Hugo includes support for user-defined taxonomies. | 2017-02-01 | 2017-02-01 |
|
|
|
80 | false |
|
true |
What is a Taxonomy?
Hugo includes support for user-defined groupings of content called taxonomies. Taxonomies are classifications of logical relationships between content.
Definitions
- Taxonomy
- a categorization that can be used to classify content
- Term
- a key within the taxonomy
- Value
- 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
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.
Movie Taxonomy Organization
To continue with the example of a movie site, the following demonstrates content relationships from the perspective of the taxonomy:
Actor <- Taxonomy
Bruce Willis <- Term
The Sixth Sense <- Value
Unbreakable <- Value
Moonrise Kingdom <- Value
Samuel L. Jackson <- Term
Unbreakable <- Value
The Avengers <- Value
xXx <- Value
From the perspective of the content, the relationships would appear differently, although the data and labels used are the same:
Unbreakable <- Value
Actors <- Taxonomy
Bruce Willis <- Term
Samuel L. Jackson <- Term
Director <- Taxonomy
M. Night Shyamalan <- Term
...
Moonrise Kingdom <- Value
Actors <- Taxonomy
Bruce Willis <- Term
Bill Murray <- Term
Director <- Taxonomy
Wes Anderson <- Term
...
Hugo Taxonomy Defaults
Hugo natively supports taxonomies.
Without adding a single line to your site config file, Hugo will automatically create taxonomies for tags
and categories
. That would be the same as manually configuring your taxonomies as below:
{{< code-toggle copy="false" >}} [taxonomies] tag = "tags" category = "categories" {{</ code-toggle >}}
If you do not want Hugo to create any taxonomies, set disableKinds
in your site config to the following:
{{< code-toggle copy="false" >}} disableKinds = ["taxonomy","term"] {{</ code-toggle >}}
{{< new-in "0.73.0" >}} We have fixed the before confusing page kinds used for taxonomies (see the listing below) to be in line with the terms used when we talk about taxonomies. We have been careful to avoid site breakage, and you should get an ERROR in the console if you need to adjust your disableKinds
section.
{{% page-kinds %}}
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 (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
Custom taxonomies other than the defaults must be defined in your site config 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 copy="false" >}} [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 config.
{{< code-toggle copy="false" >}} [taxonomies] tag = "tags" {{</ code-toggle >}}
If you want to disable all taxonomies altogether, see the use of disableKinds
in Hugo Taxonomy Defaults.
{{% note %}}
You can add content and front matter to your taxonomy list and taxonomy terms pages. See Content Organization for more information on how to add an _index.md
for this purpose.
Much like regular pages, taxonomy list permalinks are configurable, but taxonomy term page permalinks are not. {{% /note %}}
{{% warning %}}
The configuration option preserveTaxonomyNames
was removed in Hugo 0.55.
You can now use .Page.Title
on the relevant taxonomy node to get the original value.
{{% /warning %}}
Add Taxonomies to Content
Once a taxonomy is defined at the site level, any piece of content can be assigned to it, regardless of content type or content section.
Assigning content to a taxonomy is done in the front matter. Simply create a variable with the plural name of the taxonomy and assign all terms you want to apply to the instance of the content type.
{{% note %}} If you would like the ability to quickly generate content files with preconfigured taxonomies or terms, read the docs on Hugo archetypes. {{% /note %}}
Example: Front Matter with Taxonomies
{{< code-toggle copy="false">}} title = "Hugo: A fast and flexible static site generator" tags = [ "Development", "Go", "fast", "Blogging" ] categories = [ "Development" ] series = [ "Go Web Dev" ] slug = "hugo" project_url = "https://github.com/gohugoio/hugo" {{</ code-toggle >}}
Order Taxonomies
A content file can assign weight for each of its associate taxonomies. Taxonomic weight can be used for sorting or ordering content in taxonomy list templates and is declared in a content file's front matter. The convention for declaring taxonomic weight is taxonomyname_weight
.
The following TOML and YAML examples show a piece of content that has a weight of 22, which can be used for ordering purposes when rendering the pages assigned to the "a", "b" and "c" values of the tags
taxonomy. It has also been assigned the weight of 44 when rendering the "d" category page.
Example: Taxonomic weight
{{< code-toggle copy="false" >}} title = "foo" tags = [ "a", "b", "c" ] tags_weight = 22 categories = ["d"] categories_weight = 44 {{</ code-toggle >}}
By using taxonomic weight, the same piece of content can appear in different positions in different taxonomies.
{{% note "Limits to Ordering Taxonomies" %}}
Currently taxonomies only support the default weight => date
ordering of list content. For more information, see the documentation on taxonomy templates.
{{% /note %}}
Add custom metadata to a Taxonomy or Term
If you need to add custom metadata to your taxonomy terms, you will need to create a page for that term at /content/<TAXONOMY>/<TERM>/_index.md
and add your metadata in it's front matter. Continuing with our 'Actors' example, let's say you want to add a Wikipedia page link to each actor. Your terms pages would be something like this:
{{< code file="/content/actors/bruce-willis/_index.md" >}}
title: "Bruce Willis" wikipedia: "https://en.wikipedia.org/wiki/Bruce_Willis"
{{< /code >}}