Identify applications with unique tag(s) (to support e.g. application homepages in Together)

@jjaone Sorry... what was your question again? (or what are you looking for with your question?) Is it that should Q/A team do this, in our opinion, or what? I might be stupid here, but please specify a bit more. I've removed my answer, as it obviously wasn't related to your question.

@simo by removing your answer you also removed my explanation to that. Now you want me to write that explanation, again. Unique tag to identify each app accepted/submitted to Harbour. E.g. harbour-tidings, harbour-tweetian, and native system apps with jolla prefix (jolla-email, jolla-settings) just like they are named in Harbour already. Additionlly,Android apps can be differentiated here by using android prefix e.g. android-firefox, etc.. This tags cam be assigned by Harbour team when app is accepted or used here in Together everytime a question or wiki abt spesific app is posted. Tags for apps would name them explicitly and the prefix would tell the orgin/platform of the app. Also, my suggestion talks abt posting an initial page here with all app info imcluded when it is released. Thid page can be made by Q/A team or Together forum mods. This way each app would have a unique tag and page here to expand the commenting only feature in.Store currently. This would benefit users and devs and make Together a step.closer to serve as a web version of Store for or each app in Harbour. Also apps from external repos could be tagged with the same naming convention (if they are seen fit to be visible in this forum). [I'll convert this to an answer so that it is easier to see what this suggestion is all about]. Thanks for asking for details ;)

@simo and your answer was related but you were suggesting one tag for all apps, which is IMO redundant to unique-tag-per-app suggestion, where the prefix would tell whether it is system, native, external or android app. (jolla-, harbour-, external-, android-- respectively)

[see also my.comment on the answer below]

@jjaone Sorry - that was a good comment by you which got removed in my reduntant answer, however that comment didn't bring me closer to undestanding your suggestion. The one above did :) Now who would benefit of an unique tag? In general, tags are used to bring several questions under the same categories to enable better search results. Or do you mean that it would enable several questions conserning that app (which is already used, simply by adding the name of the app as a tag)?

@simo This shouldn't be very difficult to understand; tags are meta-data of content, right? A way to categorize questions here, to build typologies, to organize content, right? Basically tags are free for anyone to write any tag to any question and even retag them at will. And that freedom is the problem when you wamt to identify something uniquely (to give a name that refers to one thing only), right? But we have one example of a tag that is restricted and monitored (a first word of controlled vocabulary if you wil): everytime I use 'roadmap' I know that every instance document (question) I get as result really is roadmap'ed (and only those, not rmapped or roadmap-please, but just 'roadmap' a unique identifier for one type of content.

Same with this proposal to make apps (of different origin) to first class citiizens here, anh organize other content around them, a unique indentifier is needed, and tag is good way to start: If I want to refer the email app natively in device released by jolla. I use the tagjolla-email, and only that. not email nor jollaemail, nor jollasemail, nor email-app, nor jollas-email, so only that and always that tag in quesion means it is about jolla email app. Unique way to seartch and give metadata to the content (without any external metadata toolset) etc.

So, yes if I search with harbour-tidings tag, I get all quesions, wikis (+ any other content that can be tagged) that concern the app in harbour named "tidings" or actually harbour-tidings as it is named there already. And, the additional benefit is to have the source/platform/vendor/developer/repo-data encoded in the tag as a prefixe: "jolla-", "harbour-" (native sailfish 3rd-party apps), "android-" for dalvik-stuff, "openrepos-" for those etc. (or just "external-" for all external repos").

If you have ever used any CMS systems or tried to organize and build knowledge from e.g. free form texts that community is contributing, this is how you take the first steps towards shared knowledge building by agreeing on common vocabularies and terminologies for content (and metatdata describing it).