Are there any workarounds to support alternate tag structures? For example, we want to introduce tags for each of our SDKs that is a reflection of the SDK name. Our SDKs are structured as @namespace/name - ideally this is what each of the tags would be, but doesn’t seem possible. Ideas?

I thought I had updated :face_with_peeking_eye: - we did find a solution that works for us :slight_smile: We removed the @namespace/ and simply used the name, alongside an SDK tag icon to denote it being one of our SDKs [Screenshot 2025-09-18 at 9.52.04]

[image] Noah Lovell: @namespace/name Aside from the issue of presentation, hierarchy does exist, you can have Tag Groups.

For sure - we’ll be putting all the SDK tags under an SDK tag group. It’s just the actual tag themselves that’s the problem. It’s made worse by the fact the name could be hyphenated as such @namespace/name-name. The perfect solution would be for that to be the tag in it’s entirety, as changing it to namespace_namename or any variation would defeat the purpose

hyphens are legal in tag names, not so sure about slashes they are illegal because they are used in the routing.

Ahhhh yes - just need to figure out / and @ I appreciate the insights!

slashes are illegal because they would break the routing.

Not sure I fully follow, but we have 70+ SDKs we want to support via tags. They all follow the structure outlined, and looking for a viable solution to showing these SDKs as tags (either out of the box, custom etc) My current thinking is to drop the namespace, and have just the name. Then use the Tag Icons to better indicate that these are the SDK versions, rather than generic tags

An alternative would be using a supported homoglyph that looks like a slash. Example ／. [The image shows a tagging interface where an unrestricted tag labeled "test / test" is created, indicating it's not limited to any categories and has no synonyms. (Captioned by AI)]

Workarounds to support alternate tag structures

Product Support

Canapin (Coin-coin le Canapin) March 7, 2025, 7:56pm 10

An alternative would be using a supported homoglyph that looks like a slash.

Example ／.

Topic		Replies	Views
"." (dot) in tag Feature tags	7	2033	February 10, 2020
Is anyone else using tags on a Discourse forum in a big way? Community Building	11	4071	January 16, 2020
Support for tag aliases? Feature	4	2884	June 11, 2024
Magic Markdown tag for links to tags Feature completed	3	1415	January 12, 2016
Better navigation for (structured) tags UX	11	2330	October 27, 2021

Workarounds to support alternate tag structures

Related topics