Resources: Is the resource frontpage supposed to show file paths and not titles?

[junlarsen]

Right now the /resources page shows us something like this

Some of these are kind of "crypting", for example java/generics and java/class. These items don't really describe the content but they're like this because that's the file names.

Would it be better to show the article titles instead?

[veksen]

Possibly, but that would also mean showing the titles in the sidebar as well

[AstronautEVA]

I think it would also help to structure it like a file directory. Seeing things like

promises/async await
promises/intro
promises/simplifying promises

is redundant. It could instead be

promises
   async await
   intro
   simplifying promises

and that would also give more room to supply the article names without having a massively long line.

[hbjydev]

Wouldn't it be better to do it with titles everywhere anyway? That's what it showed on the Figma sheet iirc

[veksen]

according to this

promises
   async await
   intro
   simplifying promises

I tried it, it seems good before you try it. Most subcategories have 1 or 2 articles, it becomes really really hard to scan, this is why I did it the way it currently is.

So no, I don't think we should do this.

About titles over filenames, yes, I think titles is a better approach than using the file name, and being consistent on usage (sidebar, list of resources, related resources).

PR appreciated.