Task List

Style

Somehow the style of the page has been changed, although I don't see any entries in the log. There is a large grey background on the page which is ugly and needs to be removed. --Etaew 15:02, July 27, 2011 (UTC)

The gray is from the ".WikiaPage .WikiaPageBackground {background: #474646;}" from the oasis.scss. Looks like Mythic changed something in some settings within the wiki? Vanesyra 23:12, July 27, 2011 (UTC)

Do you know how to access the css or style for the wiki? I should in theory have permission for that. Researching it at the moment. --Etaew 11:13, July 28, 2011 (UTC)

We need to add a min-height value to the portal content page, when you switch between pages the length of the page changes which is pretty bad. --Etaew 19:18, July 28, 2011 (UTC)

Navigation

Any changes to the top navigation bar?

Also I've started to add other text links on the home page, any comments on this? --Etaew 19:18, July 28, 2011 (UTC)

Templates

Class Box

Information currently displayed:

• Type
• Profession
• Races
• Stats

Are we happy with this information displayed? I would like to change the Type from Melee/Support/Caster etc to something more easily identifiable.

• Ranged DPS
• Melee DPS
• Tank
• Healer
• Buffer

It could be worth noting the spec of each line, for example cleric.

• Ranged DPS (Smite)
• Healer (Rejuvenation)
• Buffer (Enhancement)

--Etaew 10:02, July 26, 2011 (UTC)

---

None of the information included into the class box is useful. If you ask me... using it as a picture box is the best that we could do. Why?

• A huge "Class Box" (Armsman for example) breaks down the design of the page. The box push the attribute box down leaving a big empty space between box and headline
• "Class Stats" is miss leading. It sounds like "get this attributes for this class" (already saw someone editing this because "hey this class does not need quickness, its a caster"...). Also it's something that you can not alter at all, so how cares about it? The information within the attribute box is enough for this topic and it's displayed on the same screen.
• The "Profession" is also complete useless information. No one ever will open a class page because he want's to look up the profession of a class.
• "Races" this would be a bit useful but we have the attribute box just below. Showing a information twice on one screen is bad.
• "Type" is a heretic a melee? a ranged? a supporter? a ranged dps? a buffer? a healer? You can not answer that question for many classes, it depends on how you spec and how you play. Also a big question is what you are doing? 1on1, small man, 8vs8, zerg battle? And if we can't answer that then we should not display this anyway.

So in the end so only thing that is still there is the picture. And that picture is useful because it's showing you the class your searching information for.

Vanesyra 13:21, July 26, 2011 (UTC)

---

In relation to the Armsman page and the attributes box, yes I can agree the length of the box impacts the style of the page.

I do think it's important to have some standard information separated from the main content of the page taking World of Warcraft's Paladin page it has the bare minimum of useful information which I admire:

• Important Features
• Class Type
• Armor
• Weapons
• Available Races

These are all split into separate boxes, which may be a way forward for us.

Regarding the class stats I do agree with you the attributes box below covers that well enough. Also yes, Profession does not need to be there, a simple text link in the initial description is good enough.

We could do the following:

• Wrap the main content and class box in 2 separate divs and float them, to enable a 2 columed view. The question is what other information goes on the right, images?
• Have a standardised class page header with 2 divs, floating side by side, this allows us to have a class overview and class picture the way we want them, and leave the rest of the page as normal text.
• Have various boxes covering various information around the page, the way we have it now is a bit disorganised.
• Leave the class box as an image and have the rest of the information in-line, but personally I find long wiki pages a chore to read which is why I like to separate vital content out of it.

Type is pretty important in my opinion, lets take your Heretic for example:

• Melee DPS (Flexible/Crush/Shield)
• Ranged DPS (Rejuvenation)
• Healer (Rejuvenation)
• Buffer (Enhancement)

And yes, this does have lots of combinations and options, and we can address this in different ways:

• Display type only e.g. Melee DPS / Ranged DPS
• Display type with spec e.g. Melee DPS (Flexible/Crush/Shield)
• Display as it is now: Melee

For placement in the Classbox, I would then use the 2 cells for this instead of the one currently.

To summarise, if we think in terms of visitors to the page important class related information would be:

• Image
• Type
• Races
• Specs
• Key Features (unique class abilities) - something would be quite interesting

It's good having someone to sanity check my ideas and designs and I value your opinion. --Etaew 13:48, July 26, 2011 (UTC)

---

I really hate pages like that "WoW Paladin" one. It has nearly no information but lots of pictures and bla bla text all over the page.

I did a preview on the Paladin page. You have the information you need on the TOC as a overview and none unneeded or double information on the front page of the class.

Vanesyra 15:33, July 26, 2011 (UTC)

---

It's a matter of taste really, I agree your recent change of the Paladin page is a lot better, having the TOC in a separate section with text in the middle and picture on the right is quite nice, followed by the tables of information. I would move the tactics sections down down down out of sight as they can get very wordy, and then move the realm abilities table up a bit.

For a compromise we could have a summary list as the opening paragraph of the class description, the layout of the page shouldn't be affected. Something like this:

Paladins can fill the role of a Tank when Specializing in Shield and Parry or Melee DPS when training in Slash, Crush, Thrust or Two Handed, they are also a valueable Support class when using their group Chants.

The main section of the paladin text does go into more detail, but I think summary at the top of a page is quite useful. --Etaew 15:44, July 26, 2011 (UTC)

---

I agree that the "Tactics" should be placed on the bot. So that RA selection is more on top. Just didn't changed that yet because it's done that way on all pages at the moment.

Yes we could use such a sentence as first sentence of the page to give a useful overview. For that few people how will read that. Think really most people just use the TOC to jump to whatever they are looking for.

Vanesyra 17:19, July 26, 2011 (UTC)

---

Just created the Template:Box/Class Page Header template to replace the Template:classbox on all class pages. Just needs two options: realm = Albion / Hibernia / Midgard and text = class info text. If we realy want we could later easly add again some more to the picture box at the right. Ah and well we need to make all pictures 200x300 with the name of the class (should be that way already but isn't). The Character on the picture should use the epic or epic dungeon torso (the one with the class unique skin and not colored black) and in most cases the champion level five weapon (look at Wizard for an example). May delete the [File:Highlander Armsman.jpg] as it's no longer needed (use [File:Armsman.jpg] instead). Vanesyra 16:08, August 1, 2011 (UTC)

Class Icons

Template:Portal/Albion Template:Portal/Hibernia to be changed to the Template:Portal/Midgard style, which involves listing the classes in alphabetical order. --Etaew 10:31, July 26, 2011 (UTC)

Content

NPC Lists

City of Camelot NPCs I'm not sure how to present such a large amount of information, or even if we should. I was hoping to field something like http://www.wowwiki.com/Elwynn_Forest_NPCs where eventually each NPC can have it's own page, indicating what Quests they offer, what they sell etc. Any thoughts would be welcome. --Etaew 10:02, July 26, 2011 (UTC)

Quests

Plan out the quests section

• Epic
• Per Zone

--Etaew 10:31, July 26, 2011 (UTC)

Items

Plan out the items section

• Epic
• Artifacts
• Other sets

--Etaew 10:31, July 26, 2011 (UTC)

Just some Idea for this

You can output the pages form a given category by using

<categorytree mode=pages>Paladin</categorytree>

Paladin

Block

Chants

Crush

Paladin

Parry

Plate

Shield

Slash

Thrust

Two Handed

Look at http://www.mediawiki.org/wiki/Extension:CategoryTree for more information.

We can use http://help.wikia.com/wiki/Help%3AImageMap for displaying maps with quest waypoints on it, npc locations, mob spots and so on. Going to look into that when I got the time for it. Building a sweet template for it should be possible :D

And we should be able to use http://help.wikia.com/wiki/Help%3ADynamicPageList for displaying lists of npcs within a zone, list of artefacts, list of quests within a realm, list of quests in a zone and so on. Again this should be able to be done with sweet templates.

All we have to do is creating a solid category tree and add each npc, quest, mob, item and so on to the categories they fit in. To do so we need again some templates for quests, npcs, mobs, items and so on which automatically add a page to the categories if you use the template. Also we need a template for "/loc" to later add the loc to the map of the zone.

All this is a huge work of templates and dynamic lists / maps. Have never done that before on a wiki but it should work and if it work its very sweet :D Just let me know what you think about this.

Also stuff like "show me all items with +hit points on it" or "show me quests for level 25 on albion" should be possible then. The question is if the performance of the page can handle that, but think there is only one way to get an answer to this :p

Vanesyra 14:28, July 26, 2011 (UTC)