Zola aliases support?

[Akselmo]

Hey there, I am at process setting up sveltia.

The only thing I'm lacking right now is somehow getting automatically
created aliases entries.

For example, when I post something like cool-blog-post.md, I use Kate snippets
to generate an alias like this:

aliases = ["/2026/04/21/2026-04-21-cool-blog-post.md.html"]

Is there any way to do this? I could not get string transformations work inside a field, maybe I'm doing something wrong.

So in summary, blogpost called Cool Blog Post on date 2026-04-21 should get an alias field like: aliases = ["/2026/04/21/2026-04-21-cool-blog-post.md.html"]

Thanks for any help!

[husenunicorn]

I’m not entirely sure about your specific use case, but it seems like a Relation Field might be what you’re looking for. In my case, I use it to handle “Related Articles,” allowing me to link or reference specific pieces of content that are connected to a particular page topic.

Here’s an example of how the CMS configuration and the Tera templating code could be set up:

- name: extra
          label: Related Articles
          widget: object
          i18n: true
          fields:
                - name: related
                  label: Related
                  widget: relation
                  collection: posts
                  value_field: '{{slug}}'
                  display_fields: [title]
                  search_fields: [title]
                  multiple: true
                  max: 4
                  required: false
                  i18n: true  

{% if page.extra.related %}
{% set related_articles = page.extra.related %}
    
            <section class="gh-container is-grid gh-outer">
                <div class="gh-container-inner gh-inner">
                    <h2 class="gh-container-title">Read more</h2>
                    <div class="gh-feed">
                        {% for next in related_articles[:5] %}
                        {% set post = get_page(path="posts/" ~ next ~ "/index.md", lang=lang) %}
                            {{<post_card post lazyLoad={true}/>}}
                            {% if loop.index is divisible_by(divisor=1) and not loop.last %}
                            {% include "partials/ads-feed-post.html" %}
                            {% endif %}
                        {% endfor %}
                    </div>
                </div>
            </section>
        
{% endif %}

For the Markdown content, it looks like this:

+++
title = "tes"

[extra]
related = ["post-1-tes", "post-2-tes"]
+++

I’m using Zola with the unreleased Tera 2 version.

[husenunicorn]

I’m not entirely sure about your specific use case, but it seems like a Relation Field might be what you’re looking for. In my case, I use it to handle “Related Articles,” allowing me to link or reference specific pieces of content that are connected to a particular page topic.

Here’s an example of how the CMS configuration and the Tera templating code could be set up:

- name: extra
          label: Related Articles
          widget: object
          i18n: true
          fields:
                - name: related
                  label: Related
                  widget: relation
                  collection: posts
                  value_field: '{{slug}}'
                  display_fields: [title]
                  search_fields: [title]
                  multiple: true
                  max: 4
                  required: false
                  i18n: true  

{% if page.extra.related %}
{% set related_articles = page.extra.related %}
    
            <section class="gh-container is-grid gh-outer">
                <div class="gh-container-inner gh-inner">
                    <h2 class="gh-container-title">Read more</h2>
                    <div class="gh-feed">
                        {% for next in related_articles[:5] %}
                        {% set post = get_page(path="posts/" ~ next ~ "/index.md", lang=lang) %}
                            {{<post_card post lazyLoad={true}/>}}
                            {% if loop.index is divisible_by(divisor=1) and not loop.last %}
                            {% include "partials/ads-feed-post.html" %}
                            {% endif %}
                        {% endfor %}
                    </div>
                </div>
            </section>
        
{% endif %}

For the Markdown content, it looks like this:

+++
title = "tes"

[extra]
related = ["post-1-tes", "post-2-tes"]
+++

I’m using Zola with the unreleased Tera 2 version.

However, you need to be careful when using a Relation Field, because if a referenced page is deleted, it can cause the build to fail.

[Akselmo]

Thanks, I'll look into it. However, those pages do not actually exist, the alias hint is just a redirection link.

It's not that big of a deal if I can't set it up, but there is software archival group following my blog that uses these aliases to archive it.

[kyoshino]

Aliases mean redirects, right? From the doc:

# Use aliases if you are moving content but want to redirect previous URLs to the
# current one. This takes an array of paths, not URLs.
aliases = []

I don’t think it’s supposed to be generated automatically for every single entry. It’s not a feature for creating short URLs.

[kyoshino]

Aliases were implemented in getzola/zola#86, which mentions Hugo’s aliases. I have never used Zola but I had a Hugo site and sometimes used aliases. So I know the purpose 😉

[Akselmo]

Yes, that's what I'm after. :) Though I understand this can be hassle to implement for pretty niche need.

[kyoshino]

There might be a practical/reasonable use case for aliases support. When an entry slug is edited, the CMS could add the old path to the aliases array. This would automatically set a redirect, avoiding broken links.

[Akselmo]

For that it could be good indeed. Though I am after manually creating my own alias string for them, so I can preserve the old way of file structuring for the archival teams.

But if that's not possible, I'll either enter it manually each time or just.. Stop doing it. 😛