# Would it make sense to have tags for every module?

**URL:** <https://forum.ansible.com/t/would-it-make-sense-to-have-tags-for-every-module/514>\
**Category:** Forum Guide & Feedback\
**Tags:** community\
**Created:** [September 12, 2023, 9:21am UTC](https://forum.ansible.com/t/would-it-make-sense-to-have-tags-for-every-module/514 "2023-09-12T09:21:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\
**Post date:** [September 12, 2023, 2:04pm UTC](https://forum.ansible.com/t/would-it-make-sense-to-have-tags-for-every-module/514/3 "2023-09-12T14:04:36Z")

</div>

Hey there @dulhaver , we have been creating quite a few tags to keep things as consistent as possible (check [Ansible](http://forum.ansible.com/tags) for the full list), but having all the modules would be a huge amount of tags if we consider every collection (and that the [2.9 list is end of life](https://docs.ansible.com/ansible/2.9/modules/list_of_all_modules.html)).

What we have been thinking on is using the collection “namespace” (which sometimes matches the Working Group as well) in tandem with the #collections tag where possible.

For example we could have posts tagged:

1. #collection #vmware
2. #collection #windows
3. #collection #kubernetes

_Collections_ and _collection_ are an alias, so you can use any of those.

You can search for the combination by using the intersection search:  
`http://forum.ansible.com/tags/intersection/TAG1/TAG2`

For ex:  
[http://forum.ansible.com/tags/intersection/collections/awx](http://forum.ansible.com/tags/intersection/collections/awx)

Did you had any module in mind?

---

_[View the full topic](https://forum.ansible.com/t/would-it-make-sense-to-have-tags-for-every-module/514)._
