You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use taxonomy only for the blog section of my zola-generated website, which is found under /blog.
Currently I started to use taxonomis but sadly the generated output paths are generated as /<taxonomy> rather than /blog/<taxonomy>.
I don't think this is currently possible. It's not really a blocker or harmfull, but at the same time it doesn't really make sense to have these taxonomies as a root page if they only are used for one section of my website (the blog).
I do not mind to contribute in code, but I would require a bit of help and introduction to the codebase.
The text was updated successfully, but these errors were encountered:
After a night of sleep I decided for an intermediate solution I now declare these taxonomies as blog_authors instead of authors (as an example). This way I get a slug of /blog-authors, so at least the connection with /blog is already more clear :)
I could find this useful for organising collections of articles in a site that has a blog as well, where the articles might be linked together in collection after the fact rather than being a planned series in its own section which is I belive the currently recommended way of doing it.
Version:
zola 0.15.3
I use taxonomy only for the blog section of my zola-generated website, which is found under
/blog
.Currently I started to use taxonomis but sadly the generated output paths are generated as
/<taxonomy>
rather than/blog/<taxonomy>
.I don't think this is currently possible. It's not really a blocker or harmfull, but at the same time it doesn't really make sense to have these taxonomies as a root page if they only are used for one section of my website (the blog).
I do not mind to contribute in code, but I would require a bit of help and introduction to the codebase.
The text was updated successfully, but these errors were encountered: