You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Precursor: I am not an engineer/coder, but work more in design and UX. I understand my suggestions may pull the data architecture in different directions ("Hey but that's not a tagging system anymore!") but I approach these things from the user down rather than than architecture-up. Apologies in advance if this seems frustrating.
Is your feature request related to a problem? Please describe.
The problem: not all tags are created equal. Tagging systems when properly used can be incredibly useful in returning information in searches, etc. but it requires all content creators to have the discipline to apply tags in the same way.
Example: client / server tags versus content type tags may both be tags a user sees in search returns, but in traditional tagging interfaces, the project creator needs to apply these tags in a single step.
Per Darkhax: We can't enforce/autodetect that so it would be 100% opt-in by the authors. Would likely be part of our tag system as well which would allow search filtering.
Describe the solution you'd like
On a per game basis, understand the types of tags you'd like to apply and break these apart into steps that are gated - i.e. project creation requires a choice before the Creator can proceed or finalize the project.
In the Minecraft Mod example this might look like:
Is this a Forge or Fabric mod?
What is the content type of the mod?
Selection choice examples: worldgen, mobs, structures, power, API, other (user entered)
Please choose applicable tags for client / server functionality.
Selection: client only, server only, both client and server side required to function, partial functionality etc.
etc, etc.
Requiring these steps to continue will help to ensure proper attention to all required tag types.
(Again, from a data perspective may pull this away technically from a traditional tagging system, but i'll let you BigBrain guys figure out that part or not).
Describe alternatives you've considered
There are a bunch of different UIs that could be applied to this system. Chinese menu system (choose one from column A, one from column B, etc)
Additional context
If you'd like me to wireframe something, please LMK.
The text was updated successfully, but these errors were encountered:
Precursor: I am not an engineer/coder, but work more in design and UX. I understand my suggestions may pull the data architecture in different directions ("Hey but that's not a tagging system anymore!") but I approach these things from the user down rather than than architecture-up. Apologies in advance if this seems frustrating.
Is your feature request related to a problem? Please describe.
The problem: not all tags are created equal. Tagging systems when properly used can be incredibly useful in returning information in searches, etc. but it requires all content creators to have the discipline to apply tags in the same way.
Example: client / server tags versus content type tags may both be tags a user sees in search returns, but in traditional tagging interfaces, the project creator needs to apply these tags in a single step.
Per Darkhax:
We can't enforce/autodetect that so it would be 100% opt-in by the authors. Would likely be part of our tag system as well which would allow search filtering.
Describe the solution you'd like
On a per game basis, understand the types of tags you'd like to apply and break these apart into steps that are gated - i.e. project creation requires a choice before the Creator can proceed or finalize the project.
In the Minecraft Mod example this might look like:
Selection choice examples: worldgen, mobs, structures, power, API, other (user entered)
Selection: client only, server only, both client and server side required to function, partial functionality etc.
Requiring these steps to continue will help to ensure proper attention to all required tag types.
(Again, from a data perspective may pull this away technically from a traditional tagging system, but i'll let you BigBrain guys figure out that part or not).
Describe alternatives you've considered
There are a bunch of different UIs that could be applied to this system. Chinese menu system (choose one from column A, one from column B, etc)
Additional context
If you'd like me to wireframe something, please LMK.
The text was updated successfully, but these errors were encountered: