Improve `tags` collection

[4www]

Right now we use tags:

• on company.tags, to describe companies, it is a list of "free text field"
• as tags collection, but not currently used anywhere except the /tags/:tag page if it exist, to add data to a tag

But the tags are overall not so great, as a user experience.

• their semantic is unclear
• it is not really grouping companies together
• hard to figure what tag to add / remove, or what is available

We could improve tags:

• enforce companies.tags to pick from the tags collection, (create a relation between the two models, in the cms)
• clearly define the source of the tags collection list. Why does a tag exist, what value does it bring to the user

The tags need to evolve to be able to well describe a company.

Maybe it should be additional categories on the company model.

Examples:

• https://www.linkedin.com/pulse/complete-list-linkedins-service-categories-brynne-tillman
• https://en.wikipedia.org/wiki/Category:Types_of_business_entity

All in all this seems like a complex project, that needs to bring clear and accessible semantics, to add value for the end user when exploring companies and looking for jobs.

(related cms issue https://gitlab.com/joblist/cms/-/issues/4)

[4www]

Notes about tagging systems: https://twitter.com/hillelogram/status/1534301374166474752