Template talk:Ptag

Initial discussion
Would appreciate your thoughts on this template. I noticed Librarization had a handcoded indicator and figured if we're going to do that, wrapping it in a template made more sense to me. However, we could just stick to having it in the little infoboxes like Template:Extension, Template:Wikimedia engineering project information, etc. The advantage of page status indicators is that they're a little bit more prominent and if one knows to always look for them in the top right corner, it could be a nice way to make projects consistently discoverable. Thoughts?--Erik Moeller (WMF) (talk) 07:39, 25 November 2014 (UTC)


 * Seems like a great idea. We might want to add the Phabricator tag as one of the infoboxes' parameters, and have the infoboxes emit ptag, but it's nice to have a separate template for pages that don't have an infobox, like team pages, since Phabricator tags can be used for both products and teams. Guillaume (WMF) (talk) 16:48, 25 November 2014 (UTC)


 * I like it too. Doing it in the infobox (and letting non-infobox'ed pages do it with the template) seems a good plan. Jdforrester (WMF) (talk) 17:35, 25 November 2014 (UTC)


 * Done for the Extension and WMF project infoboxes (examples: extension, project). Guillaume (WMF) (talk) 23:58, 25 November 2014 (UTC)

Overlap error - dropdown More actions menu is inaccessible
If the project tag is long, then it overlaps the dropdown p-cactions "More" menu, making it hard to access anything under the first item. See Extension:PronunciationRecording for example.

I'm not sure how to fix this. Quiddity (WMF) (talk) 20:10, 4 February 2015 (UTC)

Translation note
The colon must be preceded by a space in French, and the translator should never have to write such a hack: the colon should have been included in the translatable part of the template.

Does someone know why Template:Ptag/de says the translation is 0% complete ?

— Ltrlg (talk), 22:16, 5 July 2015 (UTC)