please improve the UI of the tags page

Description

The release workflow allows us to attach files to a tag, to turn them into releases.

However, the rendered releases page is just horrific.

Browsing the "tags" (aka "releases") page of a project, will give me a long and convoluted list of text of varying sizes, that makes it really hard to distinguish between the releases themselves, and the various items (headings) within a release.

This is the screenshot used in the official(!) release-workflow documentation:

gitlab releases

Just imagine what the average consumer of that page (not the developers, who are familiar with git) have to suffer, if they want to get the latest binary for the "FooBar download manager":

What they (at least: I) see, is a list of alternating "Changes" and "Downloads" headings, intercepted with the occasional comment (some small and greyed out text, e.g. "v2.6.5"; it's most likely unimportant, and it doesn't make much sense anyhow ... "ebb9da80 anybody?").

There seems to be something important on the right-hand side, where there is big fat button, that includes a download-icon (right, we want to download the latest release, remember), but unfortunately that seems to be "SOURCE CODE" only. heck, do they want me to earn a CS degree, when all I want to do is just use their bleeding DownloadManager.

Proposal

I'd suggest you review the "tags" page to make it actually usable.

E.g. the github releases page looks like this:

the left side contains a bit of technical info (9432598??) and can safely be ignored, though the green button "latest release" is clear enough.

it's pretty easy to distinguish between the various releases (the version number as title is obviously more important than the sections within a given release).

the downloads for each release can easily spotted, there is no distinction between generated downloads (source-code) and binary artifacts (uploaded manually, or by some CI)

final thoughts

maybe you were just unlucky and the github team were simply better in making up their release-workflow documentation. however, in practice i do find it impossible to create an appealing release-page from the gitlab "tags" page, one that i am not afraid to hand out to non-CS-literate people.

gitlab is great, but please make it even better :-)