Building Tag Links for `getResourcesTag` in Evolution CMS

A tag archive only feels complete when editors can enter tags once and the frontend automatically turns them into working navigation. In Evolution CMS, one practical approach is to store the tags in a TV, convert them into links, and let getResourcesTag read the selected value from the request.

The original setup used a helper snippet like this inside the listing template:

[[!tolinks? &items=`[[+tag]]` &keyTag=`news` &target=`18`]]

And then rendered the tag results page with:

[[!getResourcesTag?
  &grSnippet=`getResources`
  &toPlaceholder=`results`
  &parents=`8`
  &tpl=`tagResult`
  &keyTag=`tag`
  &showHidden=`1`
  &includeTVs=`1`
  &processTVs=`1`
  &tvPrefix=``
]]

The important part is consistency: the outgoing links, the request key, and the field used for filtering all have to line up. If one piece uses tag and another uses news or a different TV name, the archive will look fine while silently returning wrong or empty results.

This pattern is still worth keeping because it gives Evolution projects a simple tag system without requiring a separate content type or a heavier search layer.