This module relates to the WikiProject Council, a collaborative effort regarding
WikiProjects in general. If you would like to participate, please visit the
project discussion page.CouncilWikipedia:WikiProject CouncilTemplate:WikiProject CouncilCouncil articles
If you wish to discuss the behaviour of the project banner inside the banner shell, then you may wish to post at
Template talk:WikiProject banner shell instead.
Can |DOC=auto also add the template to the project category? Either Category:WikiProject project or Category:WikiProject project templates category.
Gonnym (
talk)
11:27, 28 May 2024 (UTC)reply
Do you want it to check to see if Category:WikiProject project templates exists first. If so use it, otherwise use Category:WikiProject project? — Martin (
MSGJ ·
talk)
08:24, 4 June 2024 (UTC)reply
That sounds good (and uncontroversial) to me, but after some searching, I have been unable to figure out where the relevant code is. Sdkbtalk18:31, 30 May 2024 (UTC)reply
Compare this: {{WikiProject AfroCreatives|category=|listas=|class=|importance=|auto=|attention=|needs-image=|type=|details=|location=|topic=}} which uses inline, with this:
I would like to add some prominent warnings when people try to use the |class= parameter in a project banner instead of in the banner shell template
If {{WikiProject banner shell}} is already on the page (but without a |class= parameter), then the message will say something like Please add the quality rating to the WikiProject banner shell instead of this project banner
If {{WikiProject banner shell}} is not on the page yet, then the message will say something like Please add the WikiProject banner shell template to this page and then add the quality rating to that template
This should be expended to any parameter we migrate to the shell, like |listas= do deal with redundant, duplicate or conflicting data.
Gonnym (
talk)
16:20, 11 June 2024 (UTC)reply
Please add {{
WikiProject banner shell}} to this page and add the quality rating to that template instead of this project banner. See
WP:PIQA for details.
This article is within the scope of WikiProject Cycling, a collaborative effort to improve the coverage of
cycling on Wikipedia. If you would like to participate, please visit the project page, where you can join
the discussion and see a list of open tasks.CyclingWikipedia:WikiProject CyclingTemplate:WikiProject Cyclingcycling articles
I am happy to walk you through it; this task is a bit easier than poofing CSS out of thin air. The basic gist of what needs to be done here is:
See if there's a class some CSS can be attached to. The presence of addClass will usually make that obvious.
If no, add a class (addClass).
If yes, check to see if the uses in the generating module all need that particular CSS. If yes, proceed to 2. If no, add a specific class to that specific element to support the new CSS.
There is a proposal to track uses of WikiProject banners which are placed outside the banner shell. The coding might be complex but I think this would be really useful — Martin (
MSGJ ·
talk)
17:38, 29 June 2024 (UTC)reply
It is not in that category because it is a redirect and doesn't need a quality rating. The |class=stub is just ignored on such pages. What needs to be corrected? — Martin (
MSGJ ·
talk)
14:15, 1 July 2024 (UTC)reply
Since
Talk:Mount Gorton refers to a redirect, |class=Stub should be removed from the 3 WikiProjects.
They are the same in that the class parameter may safely be removed without having any effect. Do we need two separate categories? — Martin (
MSGJ ·
talk)
15:42, 1 July 2024 (UTC)reply
The way that the pages in these 2 would-be categories are fixed is different. In 1, WPBS's |class= is kept. In the other, WPBS's |class=, if found, is removed. Someone working on these categories in the future might not know to check the redirect-status of the page before proceeding, and perform the wrong operation.
The interesting thing is, that in preview mode it is properly generating the notice with the diamond caution sign and "immediate attention needed", as well as displaying the name of the hidden attention-needed category in the footer that would be populated if I hit Publish, but all of that with the Preview error at the same time.
Not sure if it's relevant, but the PROJECT param is Intertranswiki/OKA task force, and a couple of redirects are involved:
Further data: I went ahead and saved the page with the Preview error anyway, at
Draft talk:Contravention in French criminal law with the intention of pointing to the error here, but after publication the error was gone, and the banner message and hidden category look good. So far, so good; but |attention= is a valid parameter, so why does it say that it isn't in Preview? Preview mode still displays the error message now, if you edit it.
Mathglot (
talk)
07:36, 2 July 2024 (UTC)reply
MSGJ, Yes, it has! Thank you. Given the complexity of this Module, and the type of situations that might arise, I am considering adding a Troubleshooting section to the doc page, and this would be a good entry there. Or at least, where to look if you get that error message, would be a good start. Such a section might expand to cover other situations, as well. Thanks for your fixes to that template.
Mathglot (
talk)
10:35, 2 July 2024 (UTC)reply
In general though, this error should be a very rare edge case, as task forces should not have standalone banners as they should use the one of the project they belong to. In this situation, there isn't a project one at this moment.
Gonnym (
talk)
10:57, 2 July 2024 (UTC)reply
Gonnym, thank you for your comment I did notice that the module had params like |tfN= for handling task forces, and I wondered how to proceed with that, given that the parent WikiProject didn't have its own banner, so I did the best I could. What I'm hearing, is, maybe this is too rare a case to be worth writing up as a troubleshooting case, and I accept that. But, what is the right path forward, here? Should Intertranswiki have its own banner, and then */OKA would use the |tfN= params? Or, is it good enough, the way things are, now?
Mathglot (
talk)
11:06, 2 July 2024 (UTC)reply
I think that if there are not going to be any other task forces needing one, then don't bother changing it as it's already working. If another task force will need one then yes, they should be combined into one template.
Gonnym (
talk)
11:09, 2 July 2024 (UTC)reply
Dark mode support
I implemented dark mode support for the banners in
these sandbox edits, without those on dark mode the banners are showing white text on light yellow background which is not great. The
test cases seem good to me, but I would still appreciate a second set of eyes on the change before deploying it.
Taavi (
talk!)
22:20, 4 July 2024 (UTC)reply