Forum:Card article redesign

Following Forum:Set page redesign, I think card articles need reworking too. They've been following the same format for years and just got added to rather than redesigned as new stuff was documented on them. There are a number of problems with the current format:
 * The first thing you see when you open a page, is the image and the card's name in many languages. The image is fine, but most readers aren't going to be interested in more than the English name, which is already in the page title, the top of the table and in a lot of pages, the image. So most people are going to be scrolling through a lot of information before getting to what they're looking for.
 * Once you scroll past the image, which probably happens at the end of the names section, the left column of the article is blank. The default skin has a small enough content area as it is, so it's not desirable to waste another 300px. A lot of stuff on the right gets crammed as a result.
 * The card's stats, English lore and sets are probably the content the reader is most interested in. Sets is kind of lost in the middle of a sea of collapsibles.
 * The pages look terrible on mobile devices.
 * The "other card information" links are near the bottom. I don't have any evidence to back this up, but I think a lot of readers aren't noticing them. I think they should be somewhere more obvious.
 * The black box at the bottom is a bit of an eyesore. The cards limitation status(es) are also something the reader is probably most interested in and I think they're easy to miss in that box.
 * Long outstanding problem: We can't search by sets using SMW.
 * A lot of the properties for "card search categories", which are not applicable to the card have "No Entry" as their property. I'm sure there's a much better way of handling this.

I've taken a stab at designing a new layout trying to address as much of these as possible and make the pages a bit more visually appealing.

-- Deltaneos (talk) 02:13, August 21, 2012 (UTC)
 * At the top of the page, you have the image at 200px, with some of the more important information next to it. You don't need to scroll much to find it and it's not crammed. There's no wide empty column below the image after this section. It's a bit more colourful and somewhat matches the design of the cards and yes, it is slightly influenced by Konami's database. Statuses (Forbidden, Limited etc.) would be displayed in this section too if the card is anything other than Limited.
 * The aforementioned section has a set of tabs, split by language. Click a different tab, you get mostly the same information, but with the name, lore and image in the chosen language. I'm a bit unsure about how I've handled the extra Japanese name stuff. I don't think we'll go beyond English, French, German, Italian, Spanish, Japanese, Korean and maybe Chinese for this. Although I think we'll add a section for other names and make some distinction between official and unofficial names.
 * In the mobile skin, you'll only see the English version of the above section. Tabber does not work so well on mobiles.
 * I think the "other card information" links are much more obvious.
 * Sets (and everything below them) have the full width of the content area to play with. English and Japanese are set to show by default, while the other languages are set to hide by default. (They're all hidden in the current setup.) Set number, set name and rarity are nicely tabbed. The rarities full names are used now that we have space. The abbreviations we were using were unofficial and I think we should use the abbreviations from Konami's DB if we are to continue to abbreviate. I haven't actually wrote the code to add the set searchablity, but it should be doable.
 * Anime/manga appearances have room for both the episode name and number.
 * The "other versions" section for cards which are quite different in the anime, manga, video games etc... I've thought it was out-of-place to put another card table in the appearances page and that it would be too much to make separate pages for them. I thought it would be nice to give them some decent recognition. Anything in this section probably won't be given SMW properties, so that they don't mess-up search results.
 * A lot of the parameter names and input is the same. Some stuff has been changed for simplicity or having some standardisation across all templates. One of the things I like is for the Japanese name, you'll just use  There's no need for any separate parameters to split up the kanji and furigana.