Hi guys, I added a comment on bug 40810 but I also want to send it here to reach more people. We still need to discuss how the badges should work in general. At the development plan [1] it says "Each sitelink can have zero or one badge attached to it." This does not match the current implementation which allows multiple badges. So the implementation needs to be changed to only supporting one badge. However, if we decide to keep the option of multiple badges we face some other problems. First, the ui gets harder to be implemented on Wikidata. This is not a real problem though. But a real problem is that we cannot determine which badge we want to display on the client. The only option I see to solve this issue is either to create another config variable (very ugly) or to only allow one badge as stated in the development plan anyway. Best regards, Bene* [1] https://www.wikidata.org/wiki/Wikidata:Development_plan _______________________________________________ Wikidata-tech mailing list Wikidata-tech(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech

On Sat, Feb 1, 2014 at 1:44 PM, Bene* <benestar.wikimedia(a)gmail.com> wrote: That was an oversight in the development plan document. I corrected it. Several badges per sitelink need to be supported at least in the future. We can start with one. Cheers Lydia

On Mon, Feb 3, 2014 at 8:37 PM, Bene* <benestar.wikimedia(a)gmail.com> wrote: We could always show the first or last in the config.

I would be glad if you explained a bit further how this feature will work on client. There needs to be a mechanism to select which items are visible in the interwiki links section and which are not. This will perhaps be a setting on the client. However, even if we say, only FA and GA badges should be shown in the article, it can still come to collisions when a sitelink has two badges which are both specified in the client's config. How should this cases be handled?

Am 03.02.2014 20:37, schrieb Bene*: In that case, both badges would be shown. The idea is: "if it IS wrong, it should LOOK wrong". Having both badges on the same page violates a convention. The convention should not be enforced by the software but by the community (possibly with the help of bots, common.js, etc). I would propose to add a css class for each badge that applies to a given language link. Per default, these classes would do nothing. Each client wiki can then define site CSS (or JS) to make some badges visible.

Am 05.02.2014 18:00, schrieb Bene*: > Interesting, so in your opinion the actual display of items should happen via > the common.css? I think this can work though I don't know if we should leave > this implementation detail to the local wikis. At least, it would prevent > another config to be added to the client which is very recommened from my > side. Also the wiki could rank the badges easier. (New css properties override > old ones.) Thus I support your idea leaving this to the client wikis.

In addition to the previous message, we still have to decide on one badge if we want to add a tooltip title. However, I don't think it makes sense to add a config variable only for the tooltip. Do you have any idea how to fix this?