a better permalink/route system for products

[usta]

When i was checking mint linux's PR i have seen that it wants linuxmint as permalink
[btw extra question which one is better linuxmint or mintlinux ]
then i have checked ubuntu and seen it didnt use linux suffix or prefix

so My suggestion is to collect some products under a parent product or producer
that will help us something like this :
https://endoflife.date/linux/ubuntu
https://endoflife.date/linux/openSuse
https://endoflife.date/linux/fedora
...
or
https://endoflife.date/microsoft/windows
https://endoflife.date/microsoft/office

With this system it also solve our JAVA problem with their vendors/distributors
https://endoflife.date/java/oracle
https://endoflife.date/java/eclipse

[captn3m0]

linuxmint- follow official project names wherever possible.

I really like the memorable URLs approach we've followed so far, and switching to nested links breaks that.

Instead, let's get categories correctly (#23 was an older attempt, the theme supports it better now I think).

There's some cases where we'll need to take judgement calls (such as probably redirecting /java to /java-openjdk) but sticking to a single level path everywhere keeps it consistent and simple.

I'd appreciate if someone can create a Product,Category table in the interim though.

[captn3m0]

If someone would like to help with this, please help me fill up this sheet with potential nav categories for all products here. Once we have some idea of the kind of categories we'd like to use for navigation (and how many), we can move further perhaps.

As an example, the nav category for microsoft stuff could be microsoft. Maybe there should be multiple nav categories as well (such as productivity to contain (libreoffice, office)?

I don't really have much idea, but hopefully we'll know better with a somewhat filled version of the sheet.

cc @ravage84 (ref: #23)

[ravage84]

Just some (random)) thoughts & opinions:

It might be sensible and useful to have a two tier-ed navigation but it might not be necessary or even value adding in all cases.

https://endoflife.date/microsoft/windows
https://endoflife.date/microsoft/office

For example, while it makes sense to list all products from "Microsoft", such as "Office" (soon to be rebranded as "Microsoft 365", btw) under a parent microsoft, it wouldn't add much value to list CakePHP under anything.

One could place CakePHP under either framework, php or php-framework for that matter but I don't think it improves anything.

so My suggestion is to collect some products under a parent product or producer
that will help us something like this :
https://endoflife.date/linux/ubuntu
https://endoflife.date/linux/openSuse
https://endoflife.date/linux/fedora

All of them are linux distributions but that does not make them children of the Linux kernel.

Additionally, they could (also) be categorised under their vendor (instead):

https://endoflife.date/canonical/ubuntu
https://endoflife.date/suse/openSuse
https://endoflife.date/redhat/fedora or https://endoflife.date/fedora/fedora

As an example, the nav category for microsoft stuff could be microsoft. Maybe there should be multiple nav categories as well (such as productivity to contain (libreoffice, office)?

What would be the concrete value for an end user of having multiple categories, thus multiple URLs to access the same product?
I think there is not much, except if one could access a list of all products under a given parent URL base.
E.g. one could find "Microsoft Ofifce" listed under either https://endoflife.date/productivity/ or https://endoflife.date/microsoft/.

And because of that I think it would be sensible to differentiate between "categories" and "tags" .
May be a product could have only one category, but it could have more than one tag.

Both meta data values could be used differently in many ways.

Still, neither would have an influence under what canonical URL it would be available.

For example CakePHP:

Canonical URL = https://endoflife.date/cakephp
Alternative URLs = https://endoflife.date/cake & https://endoflife.date/cake-php
Category = "Framework" or "PHP framework"
Tags = "MVC", "Framework", "PHP" etc.

These meta data could make CakePHP listed under:

https://endoflife.date/php-framework

https://endoflife.date/mvc
https://endoflife.date/framework
https://endoflife.date/php

In some cases categories or tags could use plurals, such as frameworks, or more specific names, such as mvc-framework.

[captn3m0]

More than URLs, we really need a "grouping" for our navigation.