FANDOM


Forums: Index Watercooler Pokemon & Move Pages


Sup fellow Poké-fans!. My name is Rachin123 or you can call me Rai. I have created this forum as I have some ideas for updating/adding templates to Pokémon and move pages. I have previously worked on some of the current templates used now but I was still a beginner and much more knowledgeable now. Templates include the following:

  • Move Infoboxes: This is something that is definitely in need of some updating. While the current infobox includes everything it needs to in terms of information. However, it fails a bit in terms visuals and construction. Plus the Contest Data section sub-templates are messed up as in its coding context causes some infoboxes to differ from each other and not for the better. My new move infobox will include the same info out side of "secondary effect", as it can be written in the Effect section of the respective move page, and "affects" as the target box will make up for that. An example can be found here.
  • Target Box: This is something we needed for a while to properly see what Pokemon are targeted. The effect section should include a brief sentence about who is affected in battle. An example can be found here.
  • Stats: There is currently a stat infobox, but it needs work in construction as the stats bars do aline properly. There's also the typing colorization. It seems that a Pokémon's secondary type takes part of inner and border coloring while the primary type gets the middle. This is something that should be opposite. My idea is to give the outer border a more bold lining so the dark coloring of the secondary type can be more defined with the primary type's normal and light coloring takes the inner part of the box. I also changed the highlighted coloring for the stats within the box, as certain types coloring clash with the coloring of the bars, making it difficult to see. I've tested all types with the colors and it seems to work much better. If the Pokémon is a single type, the outer and inner part of the box will be different shades of the same typing color. An example can be found here for a single type and here for a dual type.
  • Type Effectiveness Chart: This version is pretty much a mini version of the type effectiveness chart that is included on every type page. This allows one to see what the weakness and resistants a specific Pokémon has, which can be used to determine your decision with picking the Pokémon. The type's coloring will follow the same coloring function as the above. An example can be found here.
  • Move Tables: These include list of Pokémon on a move page and in the moves learnt section on a Pokémon's respective page. These needed some updates as its small sizing caused most rows lining to be compressed, especially because of the adding specific games the Pokémon's learns the move. My new template enlarges things a bit and helps give enough equal space to each row even when adding specific games. However, this caused it be impossible for every generation to fit with the table. But, I came up with a plan to split the templates into two parts that makes sense and is beneficial. The first template will include information that is more current and includes the addition of the Fairy type, which expands from generation 6 to 8. For the second template, it will include info from generation 1-5, and thus will not include the fairy type, however, this type of templates will be included in a subpage of the respective move page and should be named by the starting generation the move was introduced and up to 5, for example, Flamethrower: (Flamethrower/Generation I-V Learnset). An example of the learnset for Flamethrower can be found here.
  • Gallery Tables: These are expandable tables including info of every Pokémon that have used it in anime and manga media, as well as a expandable gallery table for previous generation move images. The table includes the Pokémon species that have used it in order of debut, an image of the Pokémon using the move, and the list of Pokémon users in a series that have used it. If multiple of the same Pokémon species appear in the media, a poll can be made to see which image you'd prefer used, otherwise the debut Pokémon should be used. This is so reverting for a picture you prefer doesn't arise. The coloring will be of single type with the same coloring pattern as the stat box because a move can be only one type primarily. An example can be found here.
  • Ability Tables: This table takes the stress of creating two different template boxes for a normal section and hidden ability section on an ability page. The coloring type option will only come into hand based on circumstances of the move and if it is exclusive to a certain type. An example can be found here.
  • If there enough support, I will also like to transfer the template's new styling to both Pokémon Location templates, the Pokédex Entries template, and Sprite template.

If you can give your vote down below if you support, oppose, or is neutral for the change, I'd appreciate it. You can explain your reasoning in the comment section, or if you have more questions I'll reply in the comment section.

Wiki Changes
 
13
 
1
 
4
 

The poll was created at 20:14 on June 27, 2019, and so far 18 people voted.

Comments

Comment Comment: I'm voting support, I can understand and agree with the layout reform mentioned above. PokémonGamer* 16:48, July 11, 2019 (UTC)
Comment Comment: Also voting support, seem like good points, and I am interested to see how it will work out. Misch60 (talk) 17:48, July 11, 2019 (UTC)

Comment Comment:
Move Infoboxes: It looks fine to me. I'd personally turn off the color coding and have a unified style, rather than having 18 themes. Same goes for every other color-coded template. Also, it should use the portable infobox coding, to standardize in line with the other ones.
Target Box: Good, just move it to the bottom of the "In battle" section.
Stats: Besides color coding, I'd prefer if the highest stat in the table was widened to 100%, and the others are proportionally aligned to match its size. It it is not too much trouble to code it like that, at least.
There is also an idea to actually make it like a hexagon, similar to this. Again, it might be too much trouble to code it, but if it is possible, it might be worth the trouble.
Type effectiveness chart: is this something we really need? The thing about such things is that we already have such content in type pages. I don't know about that one.
Move tables: again, I'd remove the color coding. And I am not really comfortable to leave out move information on separate pages. Especially if that style is followed on Bulbapedia. That move would spark some criticism. And from what I hear, it's better for site rankings to keep info together than to separate it.
Galleries: I admit the current style we have is not quite good. But remember, galleries aren't meant to be units to store images; if we had a ton of images, it'd slow the page down and hurt the rankings. As for the template itself, I'd prefer to make as little difference to the pages where the templates are used. Being said, is there a reason to have "Pokémon - move image - actual Pokémon" table? It might be better to sum them all up into one dropdown table, and separate them into sections (anime/manga/games/other).
Ability: I'd remove the None parameter and combine the two cells with colspan="2". However, the image and the name of the Pokémon appear to be redundant; just remove the images and it's all fine.
Design is somewhat good, judging from my experience, and I am pleased these things are being tackled. However, before making these changes, we should also ask ourselves: How will this have an impact? Will our pages be slower? Will this increase our rankings? Is this the best user experience we can offer?
And for that, I will call a pro to review these, if he isn't busy. Energy X 18:38, July 11, 2019 (UTC)

Comment Comment:
  • Move infoboxes: The new template looks good but I was wondering why the contest data has its own template and isn't in the main template, is it because of the coding?
  • Target box/Stats: Looks good to me.
  • Type effectiveness chart: Hmm, I'm not sure if it's that needed since it is on the type pages as well but I'm not really against it if it's going to be used.
  • Move tables: While the template looks nice, I prefer as well if all the tables are on the same page instead of creating a seperate page just for that. The system with the tabbers we are using right now is working just fine to me.
  • Gallery tables: I'm not sure about this one. While it does like better than the galleries we are using right now, it can fill up quite a bit with moves that are used quite a lot in the anime/manga etc. I don't mind the gallery system who are using atm. The dropdown table that Energy suggests sounds quite nice yeah.
  • Ability tables: Looks good but personally, I would remove either the Pokémon image or the names since it's kinda the same thing almost. Since it seems that many Pokémon have None as their second ability, it might be an idea to make just two rows, one with the main abilities using <br/> if there's a second one and the second row being the hidden ability one.--Lordranged7 (talk) 20:01, July 11, 2019 (UTC)

Comment Comment:

@Lord

Move Tables: I am only doing the coloring system as the infobox does and it honestly gives some appeal to it other than using the plain orange and blue "standard colors".

Gallery Table: The point of this gallery table is to not repeat images of the same Pokemon species, thus allowing for additions to users of the Pokemon species. With just using this for Water Pulse, I was able to remove 4 images of a repeated Pokemon species using it and this would be more if the move was used by more Pokemon. I think it's important to list users and not just have a gallery of certain Pokemon using it.

Ability Table: I will test out your idea to see how it changes the template.

@X

Move Tables: See my reply to @Lord above.

Stats: Ok so widening the stat box to 100% will make it too long. I did add it to 50% which coordinates well with the stats which go up to max 255 with Blissey's base HP. Um I don't know how to shape it like that. You can see how it look here now for a bot more widened stat box.

Move Tables: Ok I here you and trust me if there was some other way to fit all the information in the page for the table I would but by increasing the size allowed for less distortion in row linings. Like the table on Ember's page. However, I did not exclude the information on previous Pokemon learnset, just added links to the desired generation you are looking for. The problem with tabs is they have the tendency to slow down pages when there is large amount of info including repeated use of move tables. --Rai 水 (talk) 22:53, July 11, 2019 (UTC)


Comment Comment:
  • Move tables: I think you confused my comments with Energy since I don't have any issues with the colors but I did with having a seperate page, no worries though, haha. Ah, that's unfortunate to hear with size problem. If tabbers do really slow down the page, I don't really see another option than seperating it. Is it possible to include a link in the template itself that links to the page that has the previous gen learnsets? (I'm also still wondering about the move infobox, so I hope you can help me with that one.)
  • Gallery tables: Hmm yeah, you do have a point with that. Hopefully it will turn out good as well with the other moves.
  • Ability table: Ah nice! I hope it will turn out great.--Lordranged7 (talk) 23:21, July 11, 2019 (UTC)

@Lord

Sorry about that. Didn't mean to mix you up with @X. But yea I've tried to find a proprtional way to include all generations but it doesn't work out in the end so this is best solution we have instead of tabbing that slows the page especially if it was a move page introduced in earlier generations. That's about 20 different tabs on a single page. Too many for large tables like breeding sections especially.

I was actually thinking about linking the previous generations to the move table. Let me test something and get back to you. --Rai 水 (talk) 05:47, July 12, 2019 (UTC)

No worries. Ah okay, too bad there isn't another option for it. Alright!--Lordranged7 (talk) 11:01, July 12, 2019 (UTC)
Comment Comment:

@Lord and @X

I've re-edited the ability template. See how you like it now here. --Rai 水 (talk) 21:06, July 12, 2019 (UTC)

@Lord

So I've tried adding the links to previous generation in mobe tables for Pokemon pages but it's seems to be more difficult than I thought.

@AllUsers

I personally would like to get a good enough consensus by a week to get started in on this updating and editing jow that I'm out school until late August. --Rai 水 (talk) 21:09, July 12, 2019 (UTC)

Ah okay, looks better to me with the first and second ability now combined. Oh hmmm, that's unfortunate. Are you able to figure it out or nah? Also, to whoever voted for oppose, it would be appreciated if you explain your reasoning.--Lordranged7 (talk) 20:35, July 13, 2019 (UTC)

So it's officially been a week since I suggested this change and the majority voted support. I'm willing to start the changes on Monday unless there is a good reason not to. If you want to take a look back at my sandboxes, you can as I've done some remodeling a bit which include gallery section where on 6 images max will installed while we also continue to list the users. Unless all attacks look pretty much the same, try to add different ways its used as well. --Rai 水 (talk) 16:30, July 18, 2019 (UTC)

So how will you edit hundreds of pages to include users? That sounds a bit too much work, and I am not sure if that's a good idea. Besides, as said before, galleries aren't meant to be storing images, and having too many can slow the page down. I'm for one per generation. Energy X 20:42, July 18, 2019 (UTC)

I fundamentally oppose the new infoboxes, as they use the older non-portable syntax, and will inevitably create large problems on mobile, search ranking, and systemic issues throughout the community. — FishTank @fandom (wall) 20:05, July 18, 2019 (UTC)


@FishTank

Care to elaborate? --Rai 水 (talk) 20:23, July 18, 2019 (UTC)

It means using old infoboxes, consisted of table element, aren't suitable for mobile view. The newer syntax is much more fluid, and is better for rankings, too. Energy X 20:42, July 18, 2019 (UTC)

And one more thing, this is a bit too many proposals to approve at once, should've been each vote per each new template, something like this. Energy X 20:53, July 18, 2019 (UTC)


@X

Okay so is there a way to update it to fit the new syntax? Because as far as desktop or tablet viewing goes, it's pretty solid. The current templates need work done too. --Rai 水 (talk) 23:39, July 18, 2019 (UTC)

I'd also like to point out thateven a phone, you can view pages on desktop view. --Rai 水 (talk) 14:51, July 19, 2019 (UTC)
It can be done, and it's somewhat easy for portable infobox. While it is true that you can do the desktop view, is it something what we should be going after? The UX is slightly damaged with that. Energy X 12:26, July 21, 2019 (UTC)
@X Ok so can you show me how I should deal with converting the templates to include the new syntax style. --Rai 水 (talk) 16:41, July 21, 2019 (UTC)
Ok. I did some revisiting and noticed that it does show the mobile version of information. So.they may not be up to date with the new syntax but it is seeable and suitable enough. Either way the deskop or tablet version view is what actually depicts the styling and coloring of the templates. --Rai 水 (talk) 17:53, July 21, 2019 (UTC)

I don't have much time at the moment, but you can parse the standard infobox, which is a bit better, to line up with the rest of the infoboxes we have currently. Energy X 21:46, July 21, 2019 (UTC)
Ok but my versions were highly voted and it still works for mobile version so with that being said, I will start making the changes soon. --Rai 水 (talk) 13:42, July 22, 2019 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.