Forum:Regarding the length of infoboxes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 8: | Line 8: | ||
[[User:Pikmin1254|<b><span style="color:blue;">Pikmin</span></b>]][[User talk:Pikmin1254|<b><span style="color:#800080;">1254]]</span></b> 20:53, 8 June 2015 (EDT) | [[User:Pikmin1254|<b><span style="color:blue;">Pikmin</span></b>]][[User talk:Pikmin1254|<b><span style="color:#800080;">1254]]</span></b> 20:53, 8 June 2015 (EDT) | ||
:::I see what you mean. I never really noticed it before, but it does stand out. I'm afraid there's not much we can do to fix it, though. I can try making it so seeds and Pokos for enemy infoboxes are all in the same line, but other than that, this happens mostly because of the huge number of areas the enemies appear in. In the future, we'll likely have a section or subpage on all enemy articles that lists all the detailed locations of that enemy, and it'd make sense to link to that section/page on the infobox, instead of having a huge list. That will probably help too. Finally, I'll get around to standardizing the width of infoboxes one of these days. — '''{''[[User:Espyo|Espyo]]''<sup>[[User talk:Espyo|T]]</sup>}''' 11:41, 13 June 2015 (EDT) | :::I see what you mean. I never really noticed it before, but it does stand out. I'm afraid there's not much we can do to fix it, though. I can try making it so seeds and Pokos for enemy infoboxes are all in the same line, but other than that, this happens mostly because of the huge number of areas the enemies appear in. In the future, we'll likely have a section or subpage on all enemy articles that lists all the detailed locations of that enemy, and it'd make sense to link to that section/page on the infobox, instead of having a huge list. That will probably help too. Finally, I'll get around to standardizing the width of infoboxes one of these days. — '''{''[[User:Espyo|Espyo]]''<sup>[[User talk:Espyo|T]]</sup>}''' 11:41, 13 June 2015 (EDT) | ||
::::It's unfortunate that there isn't a whole lot that would change it. A project could be started to work on the detailed locations sections/pages. <span style="border:2px solid #001;background-color:#00BFFF;font-timesnewroman;"> | |||
[[User:Pikmin1254|<b><span style="color:blue;">Pikmin</span></b>]][[User talk:Pikmin1254|<b><span style="color:#800080;">1254]]</span></b> 23:36, 16 June 2015 (EDT) | |||
:::::The project won't be forgotten, as it's still in our (slightly more private and disorganized) TODO list. Also, I tried editing the infobox, but the way I set it up takes a huge loop around the way "per-game" fields are organized, so it'd be more important to rethink the whole thing instead of trying to make those fields less tall, but in the process, breaking other things. — '''{''[[User:Espyo|Espyo]]''<sup>[[User talk:Espyo|T]]</sup>}''' 03:59, 17 June 2015 (EDT) | |||
Latest revision as of 02:59, June 17, 2015
Forums: Index > Watercooler > Regarding the length of infoboxes
When persuing a few articles I can't help but feel that the infoboxes on enemy pages are obnoxiously long. Does anyone think it would be a good idea to include information that is essential, like maybe carry weight or Poko value and a few other bits of info, and have the rest be hidden by a dropdown menu? I feel that it would help the wiki maintain a more clean and organized look since there won't be an infobox stretching halfway down an article. Pikmin1254 23:56, 7 June 2015 (EDT)
- Do you mean long as in width or as in height? The width problem is probably because every call of an infobox specifies its width, which I find ridiculous. As for the height, it sort of the depends on the infobox. Most of them have information that wouldn't make much sense to include in the article, and unfortunately, it does make them end up a bit tall. Can you also specify which infoboxes you find huge, then? — {EspyoT} 07:17, 8 June 2015 (EDT)
- I was referring to height when I made that post. Though now that I look at it the width does seem a bit wide. Most of the issues with this are more apparent with shorter articles or enemies appearing in either the first Pikmin game or in Pikmin 2 and then again in Pikmin 3 such as Antenna Beetle, Dwarf Orange Bulborb, and Watery Blowhog.
Pikmin1254 20:53, 8 June 2015 (EDT)
- I see what you mean. I never really noticed it before, but it does stand out. I'm afraid there's not much we can do to fix it, though. I can try making it so seeds and Pokos for enemy infoboxes are all in the same line, but other than that, this happens mostly because of the huge number of areas the enemies appear in. In the future, we'll likely have a section or subpage on all enemy articles that lists all the detailed locations of that enemy, and it'd make sense to link to that section/page on the infobox, instead of having a huge list. That will probably help too. Finally, I'll get around to standardizing the width of infoboxes one of these days. — {EspyoT} 11:41, 13 June 2015 (EDT)
- It's unfortunate that there isn't a whole lot that would change it. A project could be started to work on the detailed locations sections/pages.
- I see what you mean. I never really noticed it before, but it does stand out. I'm afraid there's not much we can do to fix it, though. I can try making it so seeds and Pokos for enemy infoboxes are all in the same line, but other than that, this happens mostly because of the huge number of areas the enemies appear in. In the future, we'll likely have a section or subpage on all enemy articles that lists all the detailed locations of that enemy, and it'd make sense to link to that section/page on the infobox, instead of having a huge list. That will probably help too. Finally, I'll get around to standardizing the width of infoboxes one of these days. — {EspyoT} 11:41, 13 June 2015 (EDT)
Pikmin1254 23:36, 16 June 2015 (EDT)
- The project won't be forgotten, as it's still in our (slightly more private and disorganized) TODO list. Also, I tried editing the infobox, but the way I set it up takes a huge loop around the way "per-game" fields are organized, so it'd be more important to rethink the whole thing instead of trying to make those fields less tall, but in the process, breaking other things. — {EspyoT} 03:59, 17 June 2015 (EDT)