Board Thread:Wiki discussions and announcements/@comment-3308937-20140428221750/@comment-3308937-20140506175721

Deshiba wrote: This was supposed to be about Item Data Templates

I agree, as with the item list template this discussion is just to get the big ball ball moving, finer details like how we use the data templates (outside of, obviously, the stat pages) can be discussed in another topic, especially something like tooltips which is big enough to warrant its own thread.

Unfortunately, we're relying a lot on Bryght's same-page data template thing that I, for one, have no idea on how or if it works and whether or not it could be used for items.

One thing though, if we're going to use them for the item pages themselves (one page of editing instead of two), we're going to need to tweak the item infobox template quite a bit and figure out/plan things like what stats should be listed in what order and like how we're going to do named passives links.

My thoughts on some things:
 * Main stat listings: The obvious choice is alphabetical but, as always, could be a point of discussion, but I don't really see anything else taking priority over this.
 * Actives/passives: Actives first, Named passives second, unnamed passives third, fairly obvious.
 * Named passives: Probably going to have to be its own grouping or potentially two (name and effect) for the linking to work, open to thoughts on a more elegant solution
 * Availability: we could probably just use the already known map abbreviations like sr, cs, tt and ha for easy of use in the data templates
 * Tiers: Something that was being touched on in the item list discussion. Could either remove it from the item infobox entirely and not track it or just keep using it until we have a full blown discussion on the matter.  Currently I say we should track it in the data templates and, if need be, we can switch it off in the infobox template
 * Recipes: I feel this could be tied to a data template, we may not be able to track the actual recipe components but we could just use the data templates to call the info so that when something like ruby crystal is changed we won't have to update all the pages that it builds into. The recipe template would just call the icon, name and cost from the data template

I might come back with more but this is just what's off the top of my head atm.