Missing documentation, explanation of idea.

I think I'm getting general idea of "maps" correctly here and trying to use for myself bit more than just finding out where I made this picture and display track I recorded.
I'm trying to get the idea of "favourites". And probably all would be clear if any documentation describing usage and features would exist.
To the point. I'd expect that "favourites" is something where I can pinpoint/select picture and/or range/area on map and group those pictures/tracks under one name/category. I think this is not possible yet or I don't know how to achieve that.
Only possible for me so far was to create a point on the map and save it in favourites with its name and, in some, created category. After that I can create another pin and have it in same category but... what for? Such feature is nice to have as "note" maybe additionally to main "favourites" feature which I would see as ability to group elements and such thing make a "favourite" element.
Otherwise I have a map with bunch of pictures, bunch of tracks and.... bunch of pins with some of them being in same category. But nothing links that to "real" data which actually actually are tracks and pictures (and maybe other elements - like contacts).
Therefore is above something what exists and I don't know how to achieve - missing documentation.
OR, that's just a possible future feature and that's why "favourites" ever exist here.
OR, I'm missing point of "favourites" feature and totally don;t get the point of it.
I understand creating this as issue is not best way of reporting this problem but can't find an other way to share thoughts and might be other people agree with my point and/or like the my view of "favourites" idea in case I'm missing its current purpose.

No files, tests, or entry points are identified in the issue. Review the current favourites behavior and any existing user-facing documentation, then clarify whether favourites cover only saved map points or also photos and tracks; document the supported usage and purpose, or separate unsupported behavior into a feature request.