Difference between revisions of "Bulbapedia:Project Shipping"

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to: navigation, search
Line 86: Line 86:
*{{u|Grass lover since day one}}
*{{u|Grass lover since day one}}
* {{u|Hikari Haruka luver}}
* {{u|Hikari Haruka luver}}
===Page Creation===
===Page Creation===

Revision as of 20:48, 11 October 2009

FireRed LeafGreen Giovanni.png ArcToraphim is the leader of this project. Please direct any questions about Project Shipping or its actions to this user.
Project Shipping logo.png

Some Bulbapedia members have formed a project to better organize efforts to write and improve articles about Shipping. If you would like to help, please inquire on the talk page or the Bulbapedia forum and see the Bulbapedia:Project Shipping/To-do list.

Project Shipping

Scope and aims

Project Shipping covers all articles about Shipping. When developing new pages or adding to old ones, adhere to this: Bulbapedia:Shipping for guidance on content.


PLEASE READ: "All" is a misnomer; it is impossible to actively construct articles for all the known Ships. Bulbapedia is also an encyclopedia, and encyclopedias are professional tools. All information is relevant if it relates directly to the medium it spawns from, and is FACT. It is fact Ash is oblivious to the many crushes he's gotten; it is not fact he might currently reciprocate on any of them.

Shipping articles do offer bias, as Shipping itself is as bias as it is factual. It's fact Shipping is a major part of the fandom; it's not fact everyone agrees with everything that will be represented as evidence. Therefore, if you are going to participate in cleaning up the articles or creating them, please be aware of what is acceptable within the article. You might insert information another does not believe belongs, even though it fits possible "evidence"; unlike the main space, information here is not judged the same, only because everything on the main space is generally ironclad and there is no room for fanon, weak evidence, or lazy information. In that frame of mind, even bias information is subject to disbelief, and can be deleted if the evidence is not sustainable.

tl;dr - Crap is still crap. You can grasp at straws, but you're better off not, for the sake of an article's integrity. Know your information, and if you have to, explain it coherently (just not over-glossed and embellished).


To join the project, simply add your name to the bottom of this list:

Page Creation

If you want to create an article that is not listed on the to-do list, it would be wise to ask the current project leader if it's actually okay, with a valid argument for it. There are over 6,000 Ships in the Pokémon fandom alone; not all of them deserve articles on the merit of existence alone.

AUGUST 21, 2009: There will be no more pages for nevermets without prior consultation with the Project Leader. Any future articles will need to have a founding basis for the article, and will be given a week-long trial on its worth. Meaning, unless it's an article on a somewhat canon interrelation, such as ChikoShipping, AdvanceShipping, or CollideShipping, it will be rightly judged if it's worth notability. So before publishing the page, please construct it to an adequate size. If there is little to be said for the couple past popularity and straw-clutching (IkariShipping), then chances are it's not worth it. However, we will be the judge of that, if it's worth its weight or not.



All articles should be known as 'Shipping:{name}Shipping' and a page, '{name}Shipping' should be created with only the template {{Shipping redirect}}. There is no need to put {{Shipping redirect|PAGENAME}} because the template has that covered.

Also, at the start of each article in the Shipping namespace you should add a {{ship}} template so as to warn people.

If the article is a stub, use the template mentioned below.

Evidence Content

The manual of style for all Shipping pages are going to follow a set structure, henceforth. All Shipping pages are, from here on in, either going to go through a major overhaul, or will be using this style from the get-go. Style should be:

 * ''[[DP001|TITLE]]''
 : Hint that such-and-such may overgrossly perhaps CARE for the cretin.
 * ''[[DP038|TITLE]]''
 : Hint that such-and-such may want to have the cretin's children.
 : Oh wait, new paragraph if the above one hint carries on for too long! Possibly still talking about them having children!
 * ''[[DP099|TITLE]]''
 : Hint that such-and-such may like a second honeymoon with the cretin. Oh look, another hint that shouldn't begin a new paragraph because both are only a sentence long.

However best this information is cataloged is at your own discretion (in individual person's sections, or if their interactions are heavily interlaced, go simply for one list that contains them both), but please remain concise and neat.

It is recognized, however, not all articles will allow for adequate usage of the above template to get maximum evidence integration, and if that is the case, please utilize a style that will properly capture the evidence (but only as an alternative). Examples include AkebiShipping, FireShipping, and HoennShipping.


All articles are to be properly categorized according to character involvement and in this order of descending, applicable labels:

 [[Game (whichever one they come from OR if they are a cross-gen 'ship)|PAGENAME]]
 [[OLDER male character]]
 [[YOUNGER male character]]
 [[OLDER female character]]
 [[YOUNGER female character]]
 [[Gym Leaders]]
 [[Orange Crew]]
 [[E4 members]]
 [[Frontier Brain]]
 [[Team Rocket/Magma/Aqua/Galactic]] (in that order)
 [[Movie character]]

  • If you cannot tell who is older when dealing with homosexual Ships, then likely no one else can and it doesn't matter the order.
  • No individual Pokémon is to have their own category, not even Pikachu.
  • If the character is not important (a movie character of any level, a COTD), they should not have their own category. If you think they should, ask the project leader first and state why you think they should have a category.
  • The conditions for a recurring, secondary character to have their own category is to have at least three Shipping articles they are involved in.
  • "Recurring" in this case means they have showed up on two separate occasions (not how many episodes they've appeared in), are confirmed battle rivals, or briefly joined the group, a la Barry and Todd. Brief cameos do not count.
  • If a character falls under any the categories between the Gym Leaders and Pokémon ones in the above list, they do not get their own category without a convincing argument or enough Ships to require one (six or more).
  • If one character is from the game and another is from the anime, we'll cross that bridge later (though you shouldn't be crossing canons so blatantly and expect a legit article). If they can cover two mediums legitimately, please list them in corresponding order.
  • If Brock or Misty are involved and the other involved isn't one, it is not necessary to add the Gym Leader category. If Jessie or James are involved, it is not necessary to add the Team Rocket category (Meowth and Giovanni do, as they do not—and will not—have their own categories), unless the other character involved is a Rocket member. Treat Wallace as a Gym Leader, not an Elite Four member.
  • If the media (the side-game, the specific manga) the characters are from don't even have twelve articles under them, they do not warrant character categories at all.

Further Notes

Nevermetshippings should be labeled accordingly, such as OysterShipping, RubyShipping, OutcryShipping, et cetra. Until they do meet, there will be no "hints", but "similarity" sections are allowed, as are reasons why people Ship them in the first place. However, please do not add bias information; no nevermet Ship has risen to the popularity of the others, so they do not rival anything within the fandom's top tier.

Nonrecurring Ships, such as LuckShipping, DanceShipping, AbilityShipping, FireShipping, where the person does not, or has not, thusly returned after the heroes move on (regardless how many episodes that character was around for), should be analyzed to the nth degree (but not written be-all-end-all). Please use GaiaShipping as an example of how to handle those sorts of circumstances.

Please also do not assume that a standard for one carries over as a standard for another. This concerns the "Alternate name" business. If you've seen it with your own eyes, you may document it, UNLESS it's another Ship name that isn't on the list (the only current exception to this is "FarawayShipping" to OutcryShipping).


  1. Write comprehensive and upstanding articles on Ships.
    1. This means they are to be substantial, well written (even if they are short articles), and with substance.
  2. Ensure that all hints/evidence/facts are in the originating media and not from fanfiction. All fanon information is to be eliminated.
    1. All given hints/evidence/facts should also be meaningful and not tossed in there because it made the Shipper in you go squee.


The article you are attempting to reach contains theories of a romantic relationship between {{{1}}} and {{{2}}}. If you are offended by such material, please turn away now.

To proceed to the article, click here: Project Shipping

370Luvdisc.png This article is about shipping.
As hints and evidence for ships are mostly speculation, this page may contain personal points of view.
370Luvdisc.png This shipping-related article is a stub. You can help Bulbapedia by expanding it.

Other templates

Project Shipping logo.png This article is part of Project Shipping, a Bulbapedia project that aims to write comprehensive articles on each couple in Pokémon.
Project Shipping logo.png This user is a member of Project Shipping.

Other projects

Parent project

This project has no parent project.


No subprojects have been defined.

Related projects

No related projects have been named.