60:
31:
406:. However, Milotic and Gyarados have no explicit connection and so would be violating the previous guideline. Instances where the different connections are believed to be equal in explictness and notability will be handled on a case by case basis as per discussion and consensus on that instance.
358:. There happens to exist Pokédex info that directly mentions these species' animosity. Additionally there has even been an episode devoted to the topic. This relation can even include the fact that they are version specific Pokémon. A bad example would be an article entitled
306:
A group article is to be created whenever any Pokémon has an explicit, noteworthy connection to another Pokémon. The most common of these would be evolutionary connections. When these group articles are created, the Pokémon's entry in the list should be summarized as per
538:
because it's the earliest evolution. Besides the similar reasons listed above at Naming conventions, this also aids readers in understanding the "evolution" of the species as a whole, seeing how it was transformed over time by new releases.
275:
All Pokémon, by default, are at least deserving of a few detailed paragraphs discussing their video game/anime/manga/TCG/other appearances, and the Pokémon in general. The template for inserting information relevant to all Pokémon is
139:
134:
568:
All sections that are grouped like this should be able to have a lead. If you are having trouble coming up with a good lead, the perceived connection between the Pokémon may not be satisfying the criteria.
604:
example of Pinsir. It adequately discusses the subject without disrupting the rest of the article. It still fits nicely as a section and should not be split out. However, a section that looked like
443:
for a condensed listing in that order), or if
National number ever becomes defunct, FOO is the first Pokémon ever introduced in that evolutionary line. This means that the article which talks about
230:
225:
220:
264:
215:
196:
451:. It is done this way because it prevents page moves that would potentially occur whenever Nintendo introduced a new Pokémon to that evolutionary line. Also, for the sake of explanation,
483:) because they do not belong to any other explicit group. Rather than leave a substandard article on its own it is preferred to primarily group all legendaries by region into a
113:
378:
An unusual case may occur where a Pokémon has an explicit connection to more than one other Pokémon. Ideally they would be all grouped together under a defining title like
240:
235:
129:
85:
180:
99:
402:
connection to their evolutions is preferred. The simple reason is that it is nearly impossible to create an article that defines the subjects properly short of
554:. In many cases it would be appropriate to create parent sections for smaller, relevant groups. The smaller sections should still follow the guidelines for
160:
565:== Raikou, Entei, and Suicune == LEAD === Raikou === === Entei === === Suicune === == Lugia and Ho-Oh == LEAD === Lugia === === Ho-OH === == Celebi ==
45:
Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as the
90:
46:
507:. Ampersands (&) are to be avoided. In the case that more than two Pokémon need to be listed in the title the preferred convention is
80:
64:
17:
403:
298:
to the greatest number of people. If it is later discovered that the list pages regularly exceed 32K, different numbers may be used.
499:
Similar to the conventions for evolutionary lines, naming is determined by
National number. For example, the article would be named
354:. The most common reliable sources for Pokémon articles are the games/anime/manga themselves. A non-evolution example would be
628:
526:
Like naming conventions, sections should be ordered by
National Pokédex number. This means that after the lead, the section on
155:
254:
259:
204:
For information regarding the discussions that took place to implement this proposal please review the following links.
287:
531:
448:
325:
484:
165:
543:
379:
383:
436:
500:
355:
515:
594:
359:
231:
WT:Pokémon
Collaborative Project/Archive 14#Is there any reason why all Pokemon are necessarily notable?
508:
427:. It also helps people understand why a change that they thought was helpful ended up being reverted.
38:
30:
315:
280:
608:
version of
Bulbasaur would be cumbersome to read through in an article that still needs to discuss
295:
546:), National number already groups them appropriately so there is no need to worry about keeping
440:
226:
WT:Pokémon
Collaborative Project/Archive 11#General issue with many of the Pokemon articles...
582:
420:
291:
504:
586:
578:
562:
and be named following the naming conventions for "Pokémon grouped by other connections."
590:
488:
487:
article. The minor groups can then be worked on until they are ready to be split off per
424:
416:
363:
351:
308:
589:
information contained in a section that it can be broken out into its own article per
336:
622:
175:
170:
597:}} tag so that other editors can be aware and voice any comments or suggestions.
491:. The new articles would follow the conventions outlined in "other connections".
59:
332:
613:
472:
391:
609:
551:
527:
468:
479:), if they are only grouped in this way some Pokémon become stranded (
350:
An explicit connection is one that has been directly referred to in a
480:
476:
439:. Where FOO is the name of the first Pokémon by National number (see
387:
415:
It is important to agree upon naming conventions in addition to the
286:. The current arrangement is to list Pokémon in groups of 20, e.g.
216:
WT:Pokémon
Collaborative Project/Archive 8#Being serious about this
547:
535:
444:
467:
While many legendary Pokémon are related in smaller groups (e.g.
600:
An example of an article that should remain a section would be
25:
459:
because it is grammatically better to use an adjective form.
290:. This is admittedly an arbitrary number. It is thought that
265:
Knowledge (XXG):Articles for deletion/List of Pokémon (1-20)
221:
255:
Talk:List of Pokémon (1-20)#Merged
Proposal by Zappernapper
241:
WT:WikiProject Pokémon/Archive 15#A combination proposal
605:
601:
577:
Ideally, the situation will arise when there is enough
435:
The titles for these types of group articles should be
236:
WT:WikiProject Pokémon/Archive 15#Huntail looks awful.
366:
by fans, that they exist as male/female counterparts.
37:
This page is currently inactive and is retained for
362:. There exists no concrete discussion, outside of
404:Magikarp & Gyarados and Feebas & Milotic
386:. However in cases like connections between
331:. It is important to define what is meant by
8:
593:. Before doing so, it is best to add a {{
542:In the case of larger group articles (
7:
495:Pokémon grouped by other connections
463:Pokémon grouped by legendary status
18:Knowledge (XXG):WikiProject Pokémon
24:
58:
29:
1:
260:Talk:Pidgey evolutionary line
431:Pokémon grouped by evolution
573:Individual species articles
645:
417:Knowledge (XXG) guidelines
532:Pikachu evolutionary line
449:Pikachu evolutionary line
419:. This reduces needless
294:is likely to be the most
485:Legendary REGION Pokémon
321:should be replaced with
544:Legendary Johto Pokémon
384:Eevee evolutionary line
380:Legendary Hoenn Pokémon
629:Inactive project pages
373:Noteworthy connections
288:List of Pokémon (1-20)
530:should come first in
437:FOO evolutionary line
197:Video game characters
501:Zangoose and Seviper
356:Zangoose and Seviper
345:Explicit connections
516:Foo and bar and baz
247:Related discussions
208:Project discussions
135:Articles by quality
73:General information
65:WikiProject Pokémon
411:Naming conventions
360:Tauros and Miltank
509:Foo, bar, and baz
148:Project templates
114:Reception archive
81:Main project page
54:
53:
636:
522:Section ordering
505:Plusle and Minun
455:is preferred to
330:
326:pokeinfoboxsmall
324:
320:
314:
285:
279:
271:Lists of Pokémon
156:Talk page banner
62:
50:
33:
26:
644:
643:
639:
638:
637:
635:
634:
633:
619:
618:
575:
566:
524:
497:
465:
441:List of Pokémon
433:
413:
352:reliable source
328:
322:
318:
312:
304:
283:
277:
273:
202:
201:
192:
185:
151:
144:
125:
118:
76:
69:
44:
22:
21:
20:
12:
11:
5:
642:
640:
632:
631:
621:
620:
574:
571:
564:
523:
520:
496:
493:
464:
461:
432:
429:
412:
409:
408:
407:
376:
375:
374:
368:
367:
348:
347:
346:
303:
302:Group articles
300:
272:
269:
268:
267:
262:
257:
251:
250:
248:
244:
243:
238:
233:
228:
223:
218:
212:
211:
209:
200:
199:
193:
186:
184:
183:
178:
173:
168:
163:
158:
152:
145:
143:
142:
140:Assessment log
137:
132:
130:Article alerts
126:
119:
117:
116:
111:
105:
104:
103:
102:
94:
93:
88:
83:
77:
70:
56:
55:
52:
51:
43:
34:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
641:
630:
627:
626:
624:
617:
615:
611:
607:
603:
598:
596:
592:
588:
584:
580:
572:
570:
563:
561:
557:
553:
549:
545:
540:
537:
533:
529:
521:
519:
517:
514:
510:
506:
502:
494:
492:
490:
486:
482:
478:
474:
470:
462:
460:
458:
454:
450:
446:
442:
438:
430:
428:
426:
422:
418:
410:
405:
401:
400:more explicit
397:
393:
389:
385:
381:
377:
372:
371:
370:
369:
365:
361:
357:
353:
349:
344:
343:
342:
341:
340:
338:
334:
327:
317:
310:
301:
299:
297:
293:
289:
282:
270:
266:
263:
261:
258:
256:
253:
252:
249:
246:
245:
242:
239:
237:
234:
232:
229:
227:
224:
222:
219:
217:
214:
213:
210:
207:
206:
205:
198:
195:
194:
191:
190:
182:
179:
177:
174:
172:
169:
167:
164:
162:
159:
157:
154:
153:
150:
149:
141:
138:
136:
133:
131:
128:
127:
124:
123:
115:
112:
110:
107:
106:
101:
98:
97:
96:
95:
92:
89:
87:
84:
82:
79:
78:
75:
74:
68:
67:
66:
61:
48:
42:
40:
35:
32:
28:
27:
19:
599:
595:splitsection
587:well-written
576:
567:
559:
556:explicitness
555:
541:
525:
512:
498:
466:
456:
453:evolutionary
452:
447:is found at
434:
414:
399:
396:more notable
395:
305:
274:
203:
188:
187:
147:
146:
121:
120:
108:
72:
71:
63:
57:
47:village pump
36:
364:speculation
316:pokeinfobox
281:Pokeinfobox
189:Task forces
86:Noticeboard
579:verifiable
560:notability
337:noteworthy
296:accessible
181:Navigation
176:Invitation
41:reference.
39:historical
457:evolution
425:edit wars
292:this size
623:Category
614:Venusaur
473:Articuno
392:Magikarp
333:explicit
122:Articles
610:Ivysaur
583:neutral
552:Suicune
528:Pikachu
469:Moltres
171:Welcome
161:Userbox
585:, and
534:, not
481:Deoxys
477:Zapdos
475:, and
394:, the
388:Feebas
109:Layout
591:WP:SS
550:near
548:Entei
536:Pichu
489:WP:SS
445:Pichu
421:moves
309:WP:SS
100:Lists
91:Style
16:<
612:and
606:this
602:this
558:and
423:and
398:and
390:and
335:and
311:and
166:Stub
513:not
503:or
382:or
625::
616:.
581:,
518:.
511:,
471:,
339:.
329:}}
323:{{
319:}}
313:{{
284:}}
278:{{
49:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
