I've been looking through the forum, it seems there's a few methods to retrieve a tags page but I'm looking for the most efficient method (both speed- and template-wise).
- Using
tag.name
with tag token (routes), which utilises the original article template for rendering. - Using
tag.slug
- Using
tag.title
andsearch()
I think #2 is the simplest and prettiest solution, but it's relatively undocumented as far as I can tell. Also, I'm using two tag groups and, although I've mentioned to my client to not add duplicate tags (e.g. { 'group 1': 'stress' }
{ 'group 2': 'Stress' }
I'm interested to know the following:
- Is #2 the most optimised solution?
- Can it be used with a
tag token
route? - Will duplicate tags accross tag groups cause conflicts?
In my tests using #1 (the urls are ugly in my opinion), Depression
seems to return no results, perhaps because there is already a depression
tag in another tag group.
Ideally, I want one place for all tags, without having to create two different routes for both tag groups.