Template talk:Infobox company: Difference between revisions
→Align the infobox?: Reply |
→Align the infobox?: Reply |
||
Line 53: | Line 53: | ||
* This is somewhat [[wp:lame|lame]]. My personal preference is without all the extra spaces, but I wouldn't get upset about it! — Martin <small>([[User:MSGJ|MSGJ]] · [[User talk:MSGJ|talk]])</small> 14:31, 19 July 2023 (UTC) |
* This is somewhat [[wp:lame|lame]]. My personal preference is without all the extra spaces, but I wouldn't get upset about it! — Martin <small>([[User:MSGJ|MSGJ]] · [[User talk:MSGJ|talk]])</small> 14:31, 19 July 2023 (UTC) |
||
*I don't have a strong preference either way. On one hand, we'd add unnecessary space if we align everything, and we should generally try to avoid creating overly long wikitexts when smaller wikitexts would work fine. On the other hand, the infobox template is marginally more readable when aligned, and the change is less than a kilobyte in length, so I'm not sure if the length drawback is or is not outweighed by the readability benefit. {{summoned by bot}} — [[User:Red-tailed hawk|<span style="color: #660000">Red-tailed hawk</span>]] <sub>[[User talk:Red-tailed hawk|<span style="color: #660000">(nest)</span>]]</sub> 15:37, 19 July 2023 (UTC) |
*I don't have a strong preference either way. On one hand, we'd add unnecessary space if we align everything, and we should generally try to avoid creating overly long wikitexts when smaller wikitexts would work fine. On the other hand, the infobox template is marginally more readable when aligned, and the change is less than a kilobyte in length, so I'm not sure if the length drawback is or is not outweighed by the readability benefit. {{summoned by bot}} — [[User:Red-tailed hawk|<span style="color: #660000">Red-tailed hawk</span>]] <sub>[[User talk:Red-tailed hawk|<span style="color: #660000">(nest)</span>]]</sub> 15:37, 19 July 2023 (UTC) |
||
*:The amount of bytes added by the spaces is negligible, only about the same data as one or two long references, and it immeasurably helps with readability and organization. [[User:Ɱ|<span style="text-shadow:#bbb 0.1em 0.1em 0.1em;" class="texhtml">'''ɱ'''</span>]] [[User talk:Ɱ|(talk)]] 18:31, 19 July 2023 (UTC) |
|||
* Is this visible only to editors who happen to view the source code at that place? If yes, I recommend that you [[Wikipedia:Assume good faith]], thank the other person for their attempts to contribute to the [[Wikipedia:Prime objective]] enunciated by Jimmy Wales, trying to provide freer access to the sum of all human knowledge, and focus on things that seem more important in the long term. (I keep a diary with "to do" lists. This helps me distinguish between things that upset me but don't matter much to others from things that can really help others. Let others do whatever they want as long their actions do not substantively degrade the quality of information provided to the general public.) [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|talk]]) 16:15, 19 July 2023 (UTC) |
* Is this visible only to editors who happen to view the source code at that place? If yes, I recommend that you [[Wikipedia:Assume good faith]], thank the other person for their attempts to contribute to the [[Wikipedia:Prime objective]] enunciated by Jimmy Wales, trying to provide freer access to the sum of all human knowledge, and focus on things that seem more important in the long term. (I keep a diary with "to do" lists. This helps me distinguish between things that upset me but don't matter much to others from things that can really help others. Let others do whatever they want as long their actions do not substantively degrade the quality of information provided to the general public.) [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|talk]]) 16:15, 19 July 2023 (UTC) |
||
*:Yes it is only visible as source code, but when it allows for new articles to align, and then editors can easily see what's missing in infoboxes, it's a subtle change that really benefits everyone. I've never encountered opposition to such a beneficial change, but I suppose someone has to somewhere. And thus the RfC. [[User:Ɱ|<span style="text-shadow:#bbb 0.1em 0.1em 0.1em;" class="texhtml">'''ɱ'''</span>]] [[User talk:Ɱ|(talk)]] 18:29, 19 July 2023 (UTC) |
*:Yes it is only visible as source code, but when it allows for new articles to align, and then editors can easily see what's missing in infoboxes, it's a subtle change that really benefits everyone. I've never encountered opposition to such a beneficial change, but I suppose someone has to somewhere. And thus the RfC. [[User:Ɱ|<span style="text-shadow:#bbb 0.1em 0.1em 0.1em;" class="texhtml">'''ɱ'''</span>]] [[User talk:Ɱ|(talk)]] 18:29, 19 July 2023 (UTC) |
Revision as of 18:31, 19 July 2023
This is the talk page for discussing improvements to the Infobox company template. |
|
Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12Auto-archiving period: 45 days |
Template:Infobox company is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
Infoboxes | ||||
|
Companies Template‑class | ||||||||||||||
|
This template was considered for merging with Template:Infobox U.S. national banks on 2020 March 24. The result of the discussion was "no consensus". |
Addition of "child" parameter
Couldn't there be a "child" parameter so this template can be embedded inside another infobox template? For example, at the TBS Television (Japan) article, I tried to embed this template inside Template:Infobox television station, but the result looks weird because this template doesn't have a "child" parameter, so I had to do it the other way round. JSH-alive/talk/cont/mail 14:36, 27 April 2023 (UTC)
- JSH-alive, it does, it's just called
|embed=
. Primefac (talk) 13:05, 28 April 2023 (UTC)- @Primefac: Well, it's missing in the main documentation. Anyway, thanks for your tip. JSH-alive/talk/cont/mail 14:43, 28 April 2023 (UTC)
- Always happy to help. Feel free to update the /doc. Primefac (talk) 17:16, 28 April 2023 (UTC)
- @Primefac: Well, it's missing in the main documentation. Anyway, thanks for your tip. JSH-alive/talk/cont/mail 14:43, 28 April 2023 (UTC)
Citation in Infobox
This discussion on citation inside of infobox may be of interest to editors here. Ckfasdf (talk) 00:07, 22 April 2023 (UTC)
Founders
With this edit I intended to remove the "Founders" line from the infobox for the article. Unfortunately, The line displays from Wikidata when the field is empty. There are multiple founders in Wikidata, but the label display "Founder". That need to be fixed so it says "Founders" when there are multiple founders. Can we also add an option to suppress the line as well? Richard-of-Earth (talk) 21:38, 28 May 2023 (UTC)
- The
|fetchwikidata=
parameter can be set to "no" to disable calling WD, which I have done on the article. For the record though it is an all-or-nothing parameter, so turning it off removes all WD calls in the infobox. Primefac (talk) 17:37, 29 May 2023 (UTC)- Thank you. Richard-of-Earth (talk) 02:56, 30 May 2023 (UTC)
Template-protected edit request on 4 July 2023
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Add a | headqaurters =
parameter. 90.255.6.219 (talk) 11:52, 4 July 2023 (UTC)
Not done: We already have
|hq_location=
and similar parameters. Primefac (talk) 13:27, 4 July 2023 (UTC)
Introduces more issues than it solves
@IceWelder: We really should make this template have its parameters aligned, so that when editors copy it, they copy it aligned, and so it will be aligned in more articles. This makes editing and reading the code much, much easier. I haven't met any editor who disagrees. What "issues" do you claim it causes, and why are you edit-warring your preference as well, while trying to accuse me of the same? ɱ (talk) 13:56, 19 July 2023 (UTC)
- Please see User talk:IceWelder/Archive 9#"Block spacing"? and Template talk:Infobox character/Archive 5#TemplateData format type for reference. Regarding your latter question, see WP:STATUSQUO. IceWelder [✉] 14:00, 19 July 2023 (UTC)
- Sounds like you're a singular adamant person acting against the will of other editors in those conversations, and arguing your way into succeeding. How does the spacing make it harder for mobile editors? No space makes everything intensely cluttered and jumbled, for mobile and desktop editors. Yet I can tell I won't persuade you. ɱ (talk) 14:04, 19 July 2023 (UTC)
Align the infobox?
|
Hello all, I aligned the infobox parameters on this infobox's documentation, meaning editors using this template will start with an aligned infobox, where all the parameters and their data line up. Another user in the conversation above reverted me, and has seemed to have a long-time preference against this. What should we do for Template:Infobox company/doc? -- ɱ (talk) 14:07, 19 July 2023 (UTC)
- Support alignment. This makes it easier to read the values instead of just a wall of text-code. This is also pretty standard in a lot of infoboxes so nothing new is suggested here. Gonnym (talk) 14:17, 19 July 2023 (UTC)
- This is somewhat lame. My personal preference is without all the extra spaces, but I wouldn't get upset about it! — Martin (MSGJ · talk) 14:31, 19 July 2023 (UTC)
- I don't have a strong preference either way. On one hand, we'd add unnecessary space if we align everything, and we should generally try to avoid creating overly long wikitexts when smaller wikitexts would work fine. On the other hand, the infobox template is marginally more readable when aligned, and the change is less than a kilobyte in length, so I'm not sure if the length drawback is or is not outweighed by the readability benefit. (Summoned by bot) — Red-tailed hawk (nest) 15:37, 19 July 2023 (UTC)
- The amount of bytes added by the spaces is negligible, only about the same data as one or two long references, and it immeasurably helps with readability and organization. ɱ (talk) 18:31, 19 July 2023 (UTC)
- Is this visible only to editors who happen to view the source code at that place? If yes, I recommend that you Wikipedia:Assume good faith, thank the other person for their attempts to contribute to the Wikipedia:Prime objective enunciated by Jimmy Wales, trying to provide freer access to the sum of all human knowledge, and focus on things that seem more important in the long term. (I keep a diary with "to do" lists. This helps me distinguish between things that upset me but don't matter much to others from things that can really help others. Let others do whatever they want as long their actions do not substantively degrade the quality of information provided to the general public.) DavidMCEddy (talk) 16:15, 19 July 2023 (UTC)
- Yes it is only visible as source code, but when it allows for new articles to align, and then editors can easily see what's missing in infoboxes, it's a subtle change that really benefits everyone. I've never encountered opposition to such a beneficial change, but I suppose someone has to somewhere. And thus the RfC. ɱ (talk) 18:29, 19 July 2023 (UTC)
- I'd like to voice a procedural oppose as this kind of discussion should be held in a forum that would affect all infobox-style templates. Furthermore, the discussion should focus more on accessibility than personal preferences on particular styles. Doing so for one template and one template only would not aim for wider improvement or even consistency, rather reinforce one style preference in one instance. Additionally, I would oppose the change (both for this case and for any large-scale discussion) as it makes infobox code difficult to read and edit on small screens, especially mobile devices, while having little no advantage in other cases apart from that some believe it to look nicer. IceWelder [✉] 17:58, 19 July 2023 (UTC)
- Every infobox can have its own formatting, this should not be a global change. And I'm sick and tired of people weaponizing "accessibility" as an issue. You aren't a medical professional, simply because you think it looks cluttered to you in one viewscreen doesn't make you an expert at helping format to advantage differently-abled people. It'd still look cluttered your way in mobile, too. ɱ (talk) 18:08, 19 July 2023 (UTC)
- And you still have the right to format articles you edit however you wish. This simply just guides more new articles towards a more orderly format. Especially as most longtime editors do most of their work on desktops/laptops. ɱ (talk) 18:10, 19 July 2023 (UTC)