Making tags easier to use by adding a multi select drop down

[paaljoachim]

Various categories are listed with checkboxes beside them and one can easily select which category a post should belong to.
Tags shows a field box and the user is expected to know which tags are available or create new ones.

It would be better to have a multi select to where one can see a list of tags and choose the ones one want to use and if needed create additional tags.

For instance here is an issue I made in regards to WP Job Manager.
​https://github.com/Automattic/WP-Job-Manager/issues/1935

Adding multi select to WordPress will likely also benefit other areas as well.
Tags will very much benefit from it. Multi author posts can also benefit from it as well. We might perhaps also change categories to also use multi select.

[joyously]

Showing all the existing tags could be a UI overload, similar to listing all the authors in a dropdown on a forum site with 10,000 users.
If any are to be listed, perhaps extracting the ones that a similar to the content or title would be a way to limit the list. But then this could be for a plugin to do, instead.

[paaljoachim]

As you mention Joy perhaps extracting certain tags would be a way to limit the list.
Perhaps the 10-15 most popular tags will be seen and the rest will not.

I added this trac ticket because tags are difficult to discover.

[noisysocks]

@paaljoachim: Are you referring to the tag select component in the block editor? Or something else?

[paaljoachim]

Hey @noisysocks Thanks for checking in!

I am thinking about the tag select component in the block editor.
Here is the PR which has taken a few rounds. I believe the original contributor kinda gave up because we design folks went a bit forth and back on how to handle it, and new arguments also came up on why to continue using the tag cloud. I'll link to the last comment which in a sense creates a summary: ​https://github.com/WordPress/gutenberg/issues/8867#issuecomment-715231526

I assume this ticket can be closed as this is being handled through Github instead.

[noisysocks]

Yes, let's track this in the Gutenberg GitHub repository since it relates to the block editor. Thanks!