# Educating users about tags

**URL:** <https://meta.discourse.org/t/educating-users-about-tags/82386>\
**Category:** Community Building\
**Created:** [06.Март.2018 09:04:57 UTC](https://meta.discourse.org/t/educating-users-about-tags/82386 "2018-03-06T09:04:57Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![n-b-sonar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/n-b-sonar/32/119822_2.png) [@n-b-sonar](https://meta.discourse.org/u/n-b-sonar)\
**Post date:** [06.Март.2018 09:04:57 UTC](https://meta.discourse.org/t/educating-users-about-tags/82386/1 "2018-03-06T09:04:57Z")

</div>

Continuing the discussion from [Tags: category restrictions, tag groups, relationships](https://meta.discourse.org/t/tags-category-restrictions-tag-groups-relationships/48260/18):

Thanks Neil.

While we’re at it: do you (or other active members here) have any best-practice to share about educating members with respect to existing tags ? It’s in everybody’s best interest for topics to be accurately tagged, but I find there are a few grey zones (these are _concerns_ for now, granted I’ve not experienced it yet). Here’s a use-case:

- I’ve defined tags _feature1_ , _feature2_, _feature3_ under group _product1_, all requiring parent tag _product1_
- members of my forum might naturally tend to tag _featureX_, which won’t be autocompleted because _productX_ should actually be tagged
- I’d like my members to know that, would they tag _product2_, then all these tags would be available to them

The `instance_url/tags` is quite nice in that respect, but I was (and am still) very surprised to see that it’s not linked anywhere in the UI. ☹ Apart from pinning a post where I send users to this _tags_ page and/or share best-practice, I don’t see how I can pass the message (nor which Discourse UI/UX features can help me on that).

Happy to get input from other forum mods/admins on this.

Nicolas

P.S.: I guess one might argue that _products_ are less tag-like , and could rather be mapped with _categories_. But I don’t see this working best for us: our products work together (no strict silo), and we’re more leaning towards categories like ‘Get help’/‘Report bug’/‘Discuss best practices’  
P.S.2: the above context got me thinking that a ‘Discover tags’ link somewhere close to the tag input field could be a nice UX improvement

---

_[View the full topic](https://meta.discourse.org/t/educating-users-about-tags/82386)._
