1

The system I'm building requires a flexible taxonomy, where users should be able to add new taxonomy stuff to entries really easy and freely as soon as the need arises. So tags seem to work best for this situation.

However, there's a usability issue I'm concerned about. And that's a lot of typing, potential typos, and general "closeness" of what's already available to users (existing tags already added by users)

What I would ideally like is a tag field, which would still allow standard entry, but which also has a checkbox list of all existing tags as well - so users could just quick check tags they want to add to an entry - without typing anything - and add any extra tags manually only when these are needed.

Would something like that be possible to implement in Craft?

(The system will be an internal one, so there's no worry about too many users adding too many tags. Eventually, every single required tag will be created at some point, and users will be able to just choose from checkboxes - that's the ideal vision of how things would work on the data entry side)

thanks!

1

Any reason why you'd choose tags over categories?

Categories seem to be more of what you're describing:

Eventually, every single required tag will be created at some point.

And since Craft 2.5, authors can easily create categories right in the Entry screen as well as pick the category they want if it's already created. No manual typing required if it already exists.

Tags are usually looser approximations of the content and are considered by content strategists to be more of a "folksonomy".

If you wanted to push forward with checkboxes as tags, you could probably create a custom field that spits out all the tags as checkboxes, along with a way to add new ones.

| improve this answer | |
  • Thanks for the comment! The reason I want to have tags is mainly to make the flow of "folksonomy" more frictionless, so less typing and more of the visual hints (existing tags' checkboxes) would do the best job for this kind of stuff. Categories are also used, but in more strict format. The idea behind tax to give an little extra (I'm creating a system with the main functionality being searching "items" based on various factors). That said… you mentioned custom field… It might work! That sounds like some custom plugin to me. Is that correct? Or is it somehow built into Craft? – Mikhail Kornienko May 2 '17 at 11:52
  • Yeh the custom field would be plugin development territory. If your concern is purely UX, one other thing you might want to consider is just another category field. Unlike something like WordPress, Craft lets you have as many fields and field types as you want. You can even have multiple category groups... one strict as you want and one "looser" that resemble tags. You could then name the "looser" category field something like "Tags" or whatever and ignore Craft's built-in tags. Then let the user pick and choose from that category group. – RitterKnight May 4 '17 at 18:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.