Product Harmonization

[adriens]

👉 See #2016 for more details

[captn3m0]

Maybe we can also add tags to each product to help with such usecases?

Since tags are cheap, we can tag projects with vendors, and other distinctions. Some example tags that wouldn't fit elsewhere:

• cloud
• infrastructure
• amazon
• microsoft
• nosql
• rdbms

And similar.

[captn3m0]

Suggest undoing some confusing changes. Simple ones (Microsoft, Hashicorp) should be good.

Let's look at tags instead for such usecases.

[usta]

I'm not sure about just 2 parts in this harmonization , Mysql and rabbitmq
other than those 2 looks good to me. Yes i know oracle bought mysql and yes i know vmware bought rabbitmq
but in general those two never known with the name of these companies and adding name of these companies
infront of their title just will cause more confusion for users and make it harder for humans to find in list in left side of endoflife webpage [ as a user i never search mysql under oracle , or same i never search rabbitmq under vmware ] and i think this site doesnt have it and just ignore it [ if i was not using search bar or search function of browser ]

what do you think @captn3m0 @BiNZGi @marcwrobel ?

[BiNZGi]

Like @usta I would also leave mysql and rabbitmq without the company. The products are not strongly tied to the company brand.

[marcwrobel]

I am OK for most Microsoft and Hashicorp changes: names like "Microsoft Windows" or "Hashicorp Consul" are commonly used. But I have never or rarely seen those :

• Microsoft Azure DevOps
• Apple iPhone
• Apple macOS
• Red Hat Ansible
• VMware RabbitMQ

Like @captn3m0 I think using tags would be much better / flexible to resolve the initial issue (which was perform some reporting on vendors). We could create a page and/or a JSON for each tag listing all the products with that tag (note: looks like https://just-the-docs.github.io does not have a "tag" feature).

[captn3m0]

• Tag pages are cheap and easy to setup, even if a theme doesn't support them.
• I'm okay with the Apple prefix, since Apple iPhone is common enough phrasing, and grouping these products(so they're next to each other) makes sense.
• Azure Devops does sound more accurate than Microsoft Azure Devops. Azure is already the parent brand here.

[adriens]

Sure 👍

[adriens]

Sure 👍

[adriens]

Hi @captn3m0 @marcwrobel @usta , I've applied patches, please let me know if I sould apply some more changes, like for "Oracle MySQL" 😸

[adriens]

Maybe we can also add tags to each product to help with such usecases?

Since tags are cheap, we can tag projects with vendors, and other distinctions. Some example tags that wouldn't fit elsewhere:

* cloud

* infrastructure

* amazon

* microsoft

* nosql

* rdbms

And similar.

How willl I be able to get them from API side ?

[marcwrobel]

How willl I be able to get them from API side ?

I imagine a new path, '/api/tags/<tag_name>` that returns a response with a list of products (similar to the "All Products" endpoint).

[captn3m0]

 I imagine a new path, '/api/tags/<tag_name>` that returns a response with a list of products (similar to the "All Products" endpoint).

The product endpoint (#2062) should include tags as a list - don't think tags deserve an endpoint on their own. Till we have API up, you can easily generate these files locally by just reading the raw metadata from YAML files and dumping it as-is instead.

[captn3m0]

LGTM. Squash Merging.

[adriens]

I imagine a new path, '/api/tags/<tag_name>` that returns a response with a list of products (similar to the "All Products" endpoint).

Awesome 👏

[adriens]

🚀 👏 🙏