Decoupling Component Elements

Generally speaking, a component that lists items/models or something of the sort, should have a separate method for building the item/model 's JSX or a separate component like we sometimes do, whichever is appropriate. That allows themes or event extensions to override the minimum, which is more flexible and easier to maintain.

This will contain a list of relevant components:
* [ ] TagsPage: https://github.com/flarum/tags/blob/ea98a6cd9c96bc7f4518b6226374895001deadb8/js/src/forum/components/TagsPage.js

Start with js/src/forum/components/TagsPage.js at the referenced commit and trace how the component builds its listed tag items. Identify the item/model JSX that should be independently overridable, then compare the resulting structure with the issue’s separate-method or separate-component goal. Done means the relevant listed components have decoupled item rendering without changing their intended output.

Written by the indexing model from the issue text.