From StrategyWiki, the video game walkthrough and strategy guide wiki
Jump to navigation Jump to search
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current staff lounge page.

September 2013 | October 2013 | November 2013




MapleStory skill template overhaul vote

Hi all, we need your input. After the long discussion and sandboxing, as seen here and here, we need to vote on the features that we are proposing. Please see MapleStory/Warrior/Skills for implemented templates at the top. --Notmyhandle (talk contribs) 16:18, 24 October 2013 (UTC)

There are two main sections we are discussing here:

1) Table of contents

The thing to vote on here is how the table of contents will be laid out. On MapleStory/Warrior/Skills we currently have two table of contents. The first is a simplified table with links to each section. The second table is a highly detailed skill matrix. It looks cool, but takes up a lot of space. It also allows people to skip directly to what skill they want by hovering their mouse over an icon and looking at the skill name in the form of "MapleStory/Warrior/Skills#Shout" where #Shout is the name of the skill that popped up when I put my mouse over a particular icon.

Let's keep this vote simple. If you vote for the simple table of contents, sign here:

  • Prod (talk) 16:42, 24 October 2013 (UTC)

If you vote for the detailed skill matrix, sign here:

2) Skill tables

Under MapleStory/Warrior/Skills#First_Job we have four versions of the layout. RAP's, NMH's (2 and 3 column versions), and the Old template. There are four elements to vote on here.

a) Icon placement

We differ on our preference of where to put the skill icon. RAP wants it above the skill name, so it is centered along with the rest of the text in a triangle-like shape. I prefer that it be in-line with the text, like we do with items and other features in guides like Dragon Warrior III and Castlevania: Circle of the Moon. It also saves a line of white space.

If you vote on icon above text, vote here:

  • RAP (talk) 06:27, 25 October 2013 (UTC)

If you vote on icon in-line with text, vote here:

b) Collapsible tables

This is what we used on the old template. I propose that we do not use collapsible lists, as it adds additional clicks for readers to find the info they want. This is even more unnecessary if we make the icon matrix table of contents the permanent one (which takes you right to where you want to be). The collapsible table also requires javascript to display.

If you prefer collapsible tables, vote here:

If you prefer non-collapsible tables, vote here:

c) Columns

The template Notmyhandle proposed can be shortened so that two or more columns can be used. This saves vertical space considerably (50% or more).

If you vote for single column template, vote here:

  • -

If you vote for multi-column template, vote here:

d) Table content/colors

The data in our existing skill templates exist in one big block of text. This is handy because a lot of the data we get comes from other people posting around the internet, so a quick copy/paste of a list of text can be formatted easily with a few preceding asterisks to turn it into a bulleted list. Both of the proposed templates here suggest forcing additional formatting.

Notmyhande's table is simpler, and more like the existing template. Instead of using a bulleted list, each row would be preceded with a template parameter like row1= and everything after that would be in that row. Also, the rows only appear if the row parameters are used, so the table can be up to the maximum a skill can have (I think 20 is the maximum).

RAP's table is more complicated, has to be created after the ID/collapsible template, but allows for more customizations - more columns and colored cells.

If you vote for Notmyhandle's template (under "New template"; multi column), vote here:

If you vote for RAP's template (colored tables), vote here:

Abstain (or, the collaborative editors have to come to some consensus)

  • Procyon 02:29, 25 October 2013 (UTC)


Thank you all for your input. We have clear decisions on all but the most important part: the tables. Proc, if you see this, your thoughts would be much appreciated - the table that I suggested has two things that are very important. 1) It is simple. This makes it easy to update and, more important, makes it easy for temporary viewers to correct small mistakes (very little formatting in comparison to the elaborate table). 2) We have never supported colored tables except for where {{yes}} and {{no}} are used. I feel like this would set a precedent that all future tables could be expanded to more complex, colored versions. Neither option is bad. The more complex, colored ones, however, do require tweaking for color blind support - possibly making the colored areas optional rather than part of how you read the table. They also require more work. I think we can make the complex ones into a template, but figuring out how to do that will be painful. --Notmyhandle (talk contribs) 16:24, 25 October 2013 (UTC)

I think it would be best if I just vote for the colored table and help RAP to optimize it and then template it. We allow colors elsewhere (e.g. Chrono Trigger's boss template, Knights of the Old Republic party page, MapleStory feature tables utilizing yes/no template,s etc.). It's not about color, it's about making things simple. Color just helps cells stick out. As long as we keep simplicity in mind I think it will be ok. --Notmyhandle (talk contribs) 18:17, 25 October 2013 (UTC)