Forums › English Language Forums › General › Wiki Editors

Search

Fusing the "weathery" costume pages and others

5 replies [Last post]
Fri, 04/10/2015 - 04:44
Dracora-Speaking's picture
Dracora-Speaking

There is some desire to fuse pages like "storm avenger helm," "raging avenger helm," and "frenzy avenger helm" into a single page called "Avenger Helm" and so on. We had this before, but it was both confusing and some information was not displayed due to limiting template parameters (I have added parameters to these templates since then, so we can manage). I think one of the few reasons they are not fused is simply because they were released at different points in time.

Advantages:
Reduces editor workload significantly. We would no longer do overworld/tooltip animations for each item (only doing so if it's especially special), nor would we do an inspect window preview of each item. We would no longer have to add them to the main costume list, they would be rooted with "storm." EDIT: this point for editors

As more items are released that are "weathery," fusing the pages will seem more consistent with the rest of the wiki, like the recolor pages, and so on. EDIT: this point for users

Disadvantages:
Puts another "exception" into the already confusing sorting method we have for costumes. As a microbiologist, such exceptions to "taxonomy" are the norm, so it doesn't bother me. EDIT: this point for users

I already went through a deletion process with an Admin with fused weatherpages, so reforming the pages would make us seem inconsistent as editors, but in our defense, the game is very dynamic, so we should all expect this sort of thing now and again. EDIT: this point for editors

I am neutral on this - there's a lot of information per item. I will make changes if there is more desire to do so, but only if I get help. I will defer to the opinions of those who are willing to help with the grit editing. I propose a format similar to the one we use on the Obsidian Costume pages, without the set column of course.

===============================================================================================
Here is a list of entities we have merged, to keep track of what we should do in the future, or if we want to revert back to previous formats consistently:

- Anti-Personnel Spikes and Anti-Hazard Spikes have been merged into an article called "Anti-Spikes"
- Crown of Summer and Crown of Winter into "Solstice Crown"
- Apocrean Crown and Arctic Crown into "Crown (accessory)"
- Apocrean Disciple Wings and Arctic Disciple Wings into "Disciple Wings"
- Cosmic, Solar, and Voltaic Plasma Wings into "Plasma Wings"
- Wings of Fury, Rage, Frenzy into "Wings (special)"

- Dragon (Iron, Gold)
- weather costumes (avenger, champion, crusader, dragon, warrior, rider, plate)
- NPC uniforms (the armor items are not as intuitive due to naming issues. Those have been merged into "Coat (uniform)."

===============================================================================================
To Do (considering appearance and name, not just appearances):

wolf costumes
serene costumes
think of any more?

Also, will be working on making the format of certain "only released in one style" accessories more uniform. It's a little weird, but it's one of those formats that makes more sense with more examples. I just pretend everything is a bolted vee unless it has a unique name and it works out. EDIT: Bleh no, then it would be inconsistent with costumes.

On a side note, it's nice to be able to compare that gold dragon helm to the storm on the same page. I imagine people will want to do that, especially now.

Fri, 04/10/2015 - 05:36
#1
Thepc
I prefer it merged

thats not an easy decision.
Personally I would prefer if they were merged together, but I'll help with making more animations in case the pages stay separated.

Fri, 04/10/2015 - 06:59
#2
Bopp's picture
Bopp
some vague comments

I don't pay much attention to promotions and their accessories/costumes, but here are some vague comments that you might or might not find useful.

Our focus should always be on readers, whereas your advantages and disadvantages seem to be entirely about editors. But maybe I'm reading too much into that.

From a reader perspective, how is Storm vs. Raging Avenger Helm different from Devotion vs. Influence Obsidian Helm? Aren't they all just recolors? If so, then they should be treated similarly.

In general, the wiki is better when each page presents a substantial, but not overwhelming, amount of information. Therefore merging these tiny pages into one coherent page is good. It reveals similarities that readers might not notice otherwise.

On the other hand, one of our principles has been "one wiki page per game entity". This is very elegant and easily understood by readers. But it leads to many small pages disconnected from each other. And we already violate it all over the wiki.

Fri, 04/10/2015 - 07:44
#3
Dracora-Speaking's picture
Dracora-Speaking
*ahem*

Put annotations in original post to clarify pros and cons. I actually did try to balance it between users and editors...two for each :/ (I am a user too, and I often compare what I expect, pattern wise, from other wikis to our own)

As far as "one page per entity" goes, I've tried to rectify this somewhat with redirects so they at least register for categories. There's still...almost every accessory left to go. I'm fairly certain that the only reason we have this...issue...is because SK controls the color palette. Like you wouldn't post pictures of every possible color of a thing if the player can change it with a palette. Blegh.

I wonder what we'll do when the naming convention isn't easy. Like what do we do with Wings of Fury, Rage, and Frenzy? "Wings of X"? "Weather Wings?" Blargh.

Fri, 04/10/2015 - 11:12
#4
Bopp's picture
Bopp
I see

I now see which comments you intended to be about users. Thanks. I have nothing more to add though.

Fri, 05/08/2015 - 17:18
#5
Dracora-Speaking's picture
Dracora-Speaking
Workin on this

I will be working on this for a little while. This type of work requires special attention to the way involved templates function. If you want to help, carefully pick examples you feel are best. If an image doesn't show up, do not upload anything - these items have definitely been uploaded. Adjust some capital letters, spacing, and hyphens for a while. If that doesn't work, come back here and talk about it. These are my template coding for the most part, so I'd like to know if they can be simplified too, and I should be able to fix/clarify things if there are issues.

Check out the page code of this merged example that uses weird naming convention to see the flexibility of the gallery template in action. Here is the documentation for the galleries used on these pages. The rest of the templates should be pretty intuitive.

I will be updating the OP with a list of merged entities as this goes on.

Powered by Drupal, an open source content management system