|
|
@@ -142,11 +142,11 @@ the value should be the same as the one in the front-matter, not the slugified v |
|
|
|
Gets the whole taxonomy of a specific kind. |
|
|
|
|
|
|
|
```jinja2 |
|
|
|
{% set categories = get_taxonomy_url(kind="categories") %} |
|
|
|
{% set categories = get_taxonomy(kind="categories") %} |
|
|
|
``` |
|
|
|
|
|
|
|
### `load_data` |
|
|
|
Loads data from a file or URL. Supported file types include *toml*, *json* and *csv*. |
|
|
|
Loads data from a file or URL. Supported file types include *toml*, *json* and *csv*. |
|
|
|
Any other file type will be loaded as plain text. |
|
|
|
|
|
|
|
The `path` argument specifies the path to the data file relative to your base directory, where your `config.toml` is. |
|
|
@@ -214,8 +214,8 @@ By default, the response body will be returned with no parsing. This can be chan |
|
|
|
|
|
|
|
#### Data Caching |
|
|
|
|
|
|
|
Data file loading and remote requests are cached in memory during build, so multiple requests aren't made to the same endpoint. |
|
|
|
URLs are cached based on the URL, and data files are cached based on the files modified time. |
|
|
|
Data file loading and remote requests are cached in memory during build, so multiple requests aren't made to the same endpoint. |
|
|
|
URLs are cached based on the URL, and data files are cached based on the files modified time. |
|
|
|
The format is also taken into account when caching, so a request will be sent twice if it's loaded with 2 different formats. |
|
|
|
|
|
|
|
### `trans` |
|
|
|