Module talk:Sidebar

From WikiProjectMed
(Redirected from Template talk:Sidebar)
Jump to navigation Jump to search

Should the sidebar image ever be overridden at article level?

Child sidebar templates allow editors to override the "image=" field at the article level, which is sometimes used in place of a lead image (such as The consequence is that such an article displays with no lead image on mobile, since the mobile view doesn't attempt to display sidebar templates.

Are there cases where it's useful for individual articles to override the sidebar image, or is this an outdated pre-mobile approach which should now be deprecated and removed? --Lord Belbury (talk) 12:18, 26 January 2022 (UTC)Reply[reply]

I think it doesn't make sense to rely on sidebars to generate page images, regardless of whether Module:Sidebar should allow children to change images.
That said, there's not a lot we can do here to prevent children from changing their images. So long as the direct use of sidebar can change images as on the template's definition page, so too can someone change the direct use to allow passing an image from the indirect use. Izno (talk) 17:54, 26 January 2022 (UTC)Reply[reply]
True. Would it be worth updating WP:SIDEBAR documentation to explicitly say that sidebars should never have article-level images, and that these should always be split out into regular thumbnails above the sidebar, when encountered? (Another problem I encountered today was that not all sidebars support captions below the image, making it impossible to explain what an image is illustrating, while it remains in the sidebar.) --Lord Belbury (talk) 13:59, 17 February 2022 (UTC)Reply[reply]
Never is probably strong, but I have no particular qualms with a similar change. Izno (talk) 18:26, 17 February 2022 (UTC)Reply[reply]

I've added a milder do not ... override the "image=" field to illustrate something from the article to the paragraph about mobile display. --Lord Belbury (talk) 19:32, 17 May 2022 (UTC)Reply[reply]

Paramter "state=expanded"

Hi again, in the template {{Sidebar with collapsible lists}} which uses Template {{Sidebar}} there is (or was?) a parameter named state – for example see Archive 1 or the use {{Peerage|state=expanded}} in the article Peerages in the United Kingdom. I cannot find information about this on the help page, also not on Template:Sidebar with collapsible lists/doc. There it is writen | expanded = {{{expanded|}}}. But if there is Parameter "state", shouldn't it be | expanded = {{{state|}}}? OR: in the first use {{Peerage|expanded=yes(?)}} or sthg. similar? Sorry for my poor English, it's not my mother tongue. Thx, --W like wiki good to know 14:27, 12 April 2022 (UTC)Reply[reply]

|state= has never been an argument supported by {{sidebar with collapsible lists}}. You may be confusing it for {{navbox}}, which does accept that parameter. Here |expanded= is the correct argument as you have identified. Izno (talk) 17:25, 12 April 2022 (UTC)Reply[reply]
Fixed. Altanner1991 (talk) 16:24, 28 May 2022 (UTC)Reply[reply]

Missing navbar in {{Neolithic}}?

For some reason the v/t/e links are not appearing in {{Neolithic}}. My cursory skim of the source doesn't seem to indicate an obvious reason. Can someone help please? --Joy [shallot] (talk) 08:13, 6 June 2022 (UTC)Reply[reply]

Never mind, I found the reason in another talk page archive - the "name" parameter was missing. Can we document this better? --Joy [shallot] (talk) 08:15, 6 June 2022 (UTC)Reply[reply]
The convoluted "if ... and ( or ...) ~= cfg.i18n.title_not_to_add_navbar) then" block should have an "else" sibling that prints some sort of a warning message, whether in the live output or that new box above the edit preview. --Joy [shallot] (talk) 08:19, 6 June 2022 (UTC)Reply[reply]
Why should we warn people about this? Sidebars are not like navboxes which are basically guaranteed to have the relevant parameter. Izno (talk) 15:13, 6 June 2022 (UTC)Reply[reply]
It all comes down to the same thing - no |name=, no navbar. In that respect, sidebars are no different from navboxes. --Redrose64 🌹 (talk) 19:52, 6 June 2022 (UTC)Reply[reply]
We should warn them because it's obfuscated otherwise, it's not intuitive at all, you have to delve into the documentation to understand this quirk. It's bad design. --Joy [shallot] (talk) 08:23, 11 June 2022 (UTC)Reply[reply]

Left justified text?

Is there a simple way to use normal left-justified text for the content section? Maury Markowitz (talk) 14:14, 18 July 2022 (UTC)Reply[reply]