Category talk:Templates that should have been local
From WoWWiki
Contents |
Characteristics of a "local" template?
Mikk, I'm wondering what your thoughts are on what characteristics a template should have for it to not be "local". I'm also wondering why you chose the term local of all things. * [[CCCC ZoneIDs]] is listed here, but for what reason? It's not even in the template namespace, and isn't called as a template on the one page that links to it. * [[template:cloths]] and [[template:gems]] are legitimate, called by each of the cloths and gems * [[template:battlegrounds]] for a similar reason * [[template:bfd]] and such. Now, '''bfd''' and such aren't called more than one time, and on my page, so it's fine if that's in this category, but it could be useful (although I don't know what plan would be best to use it). If it remains unused, it could go "local" as far as I care.
I'm not familiar with all the others, so I have no opinion right now. Schmidt 14:49, 30 May 2006 (EDT)
- Ooo, input! Thanks :-)
- Why "Local"? Erhm. Lack of imagination I suppose. Something in "Template:" is "Global". Something somewhere else would then be "local". If you can think of a better name....?
- On cloths/gems/battlegrounds/bfd.... My thinking is that a template that is used only used a very few times, and in a very narrow context, makes more sense to move somewhere other than "Template:". Like "Template:Cloths" would make sense to move to "Cloth/Cloths". It'd still be listed as a template (via these categories!).
- "CCCC ZoneIDs"? Err. I meant to categorize Template:CCCC, not that one. Thanks for catching my snafu.
- And yeah the page text could have been a lot better. I already had it up for edit but had to go get some sleep. I've expanded LOTS on it now so give it a read. It explains the concept a lot better than I cba to do here right now :-)
- --Mikk 00:24, 31 May 2006 (EDT)
- (As with everything else I'm doing, if you think this is a horrible idea, please say so and I'll back the changes straight out. Well, ok, I might argue a little bit first ;) --Mikk 00:47, 31 May 2006 (EDT))
- Let me direct you to the illustrious Wikipedia, and their Allpages list (Template namespace). Right at the beginning you see all kinds of templates, such as 100th Senate, 1984, 1984 Atlantic hurricane season buttons (only up to L!, only 4 legit hurricanes); on the second page, Admirable class minesweeper (a real ship class, I reckon, with tons of red links – we should do likewise, for standardization of names), Aircraft by nationality, and see all the Buffy templates.
- So I'm going to have to firmly say that at least the ones as I mentioned them above should not be "localized", or at least in this manner. I haven't gone through the list of templates that might be good candidates or bad candidates for this, so I'm afraid I can't give you a whole lot more to go with. I'm guessing, though, that there are better candidates for the list.
- As I see it, in this case, if there is a potential that a template can be used in more areas, given more information (bfd, for one), it should be used wherever it is relevant, and should be given whatever information others think is relevant to where it will be inserted. Stuff like instancing guide – stuff like that.
- As for a better term than local, marginalized would fit better somewhat, but even that isn't really good. Basically, the best use for a project like that is just to say that if someone has a template that is specifically to be used by them, having a message specific to them and in that case will probably be substed (not including the welcome template that Fandyllic uses although he might already be doing this), they should just put templates like that in their own space, like user:D._F._Schmidt/signature. I'm not sure what term you would use in this case. All told, I don't think it's a good idea to take something that anyone globally could feasibly use and marginalize (for lack of better term) it.
- In any case, it does seem like an idea I would come up with. That doesn't necessarily make it a good idea, but I also have a mind to prune things down a bit here. What you're doing helps. Thanks. If you come up with any other thoughts to retool this idea, definitely state them. Schmidt 06:47, 31 May 2006 (EDT)
- Sure, I have no problem with looking at things that way. It's the same basic idea but with a narrower scope. I'll go through the list and move things off to suitable categories. Examples of things that should be local would then still include e.g. the subpages of the Community Portal and WoWWiki:Policy/Deletion_categories. (But those are already "local", so they obviously won't end up on the list :-)) There'll probably just be a handful left in the end.
- My motivation was to make the Template namespace a bit more navigable while still telling people to go ahead and use (local) templates to their hearts' content. And also make them somewhat easier to find - you'd find ingredient templates next to the ingredients, instance templates next to the instances, etc, and reserve the Template namespace for things that are useful outside of a single category. But then again, the template categorization system itself does make it more navigable. Assuming people actually keep using it, that is.
- (On a sidenote though, I think "wikipedia does it" has no merit in and of itself. L2argue plx :-))
- --Mikk 08:33, 31 May 2006 (EDT)
- I get you there, that just because Wikipedia does it doesn't make it so we should. But see, if templates will be called frequently, they should be easy to call, and therefore should be easy to spell and to remember. Whatever method is best should be used. Keep in mind that some of them have been used for quite a while, but unlike old dogs, old people can learn new tricks. And then there's the template categories that you've made, which are good.
- There is one template I just came across that I want deprecated, and didn't know what category to use: [[template:money]].
- L2argue? I assume that means "love to argue." I'm the same way, to an extent, and I appreciate it when someone will give some resistance when they feel as strongly as I do. Schmidt 08:51, 31 May 2006 (EDT)
- Aye, but if a template is used often, it's 99.9% likely to be because it's globally useful, and hence a "Template:" namespace candidate according to my way of seeing it. Heck, that's what judgement calls are for :-) Anyway, I'm cleaning up this category in a little.
- Re: "money". Hmm.. "Deprecated Templates" sounds good to me. Makes them easy to skim through once in a while and see if they can be deleted.
- And, yeah, I've also done way too much arguing on various newgroups, mailing lists and IRC channels over the years; if I know that the guy I'm arguing with will take it the right way, I'm likely to keep going just for the joy of wringing the last scraps of debatability out of a good argument ;) --Mikk 11:50, 31 May 2006 (EDT)
- Damnit, now you made me go fix all pages that used money, money1, money2 and money3. Now you owe me a new brain. I think I've mine's got RSI now. --Mikk 15:16, 31 May 2006 (EDT)
Arf, ok, I've moved out the templates Schmidt mentioned and some similar in intent. But even in a more lenient view, the (fairly numerous) templates that remain do deserve to be made local, according to my reasoning.
- One other thing about the template namespace, and having "local" templates on another namespace such as the main namespace: If you click Random page in the navbar, I'm pretty sure it uses only those articles in the main namespace. This means that it might pull up one of these "local" templates. I don't like the sound of that. Personally, I think the fact that they're named as they are, a great many on this list, I mean like creaturetype-dragonkin and so on, and the fact that they group together on an alpha-sorted list makes it so you can pretty well imagine what they are and what they're for. To be more clear, I don't know why those exist. But if they stick around, due to the naming of them, I'd say keep them in the template namespace. Do you have anything else for me to refute? lol Schmidt 16:46, 31 May 2006 (EDT)
- Ok, you and I aren't gonna solve this unless you simply trump me with the Admin Card. I'll just start a vote on it and see what people seem to think. I meant to do this right off, but then I got annoyed by the voting templates and had to fix them first ;) Oh, and the "random page" argument doesn't work on me. There's just too many other "crap" pages that people could land on for this to have any real impact. Random is random, and I think people know that :-) --Mikk 15:23, 2 June 2006 (EDT)
- I won't pull that card on this case yet, and probably not at all. Whatever results from voting is fair. Schmidt 16:19, 2 June 2006 (EDT)
Education
This vote seems to have stalled. Myself, I am in favor of using 'local pages' for things that would ordinarily be made a template solely to clean another (single, or very few) page(s) up. However, as inclusions are not as common as templates, we should make an effort to point out the methods involved:
| to invoke a template at "Template:Tables:ReputationMobs:Timbermaw Furbolgs | {{Tables:ReputationMobs:Timbermaw Furbolgs}} |
| to include a page (not in the template namespace) at Timbermaw_Furbolg_reputation_guide/ReputationMobs | {{:Timbermaw_Furbolg_reputation_guide/ReputationMobs}} |
--Eirik Ratcatcher 14:27, 22 March 2007 (EDT)
Should the majority of the templates in this category be moved to local subpages?
- Voting "Yes", means that you mostly agree with Mikk in the discussion above, and that templates that really only have a local use should be moved off to local sub pages. (You can disagree with the classification of a few of them, obviously... this is just a general poll)
- Voting "No", means that you mostly agree with Schmidt in the discussion above.
I'm not going to require that the vote follow the voting policy and "win" by a certain number of votes before any action is taken, because I have a feeling it'd mean we'd sit here locked for two months. I'll just let this run for a couple of days and see what happens.
Just use #~~~~ - your notes in the Yes/No subsections below:
Yes, they should be moved
- Mikk 15:23, 2 June 2006 (EDT) - my idea, so...
- Ted 03:09, 27 August 2006 (EDT) - Templates are confusing to casual editors, some wont know how to change them, some wont know that they've changed more than one page. I realise that the obvious retort is just learn, but I think that pages should be as transparent as possible. Certainly we should not have templates on the off chance that they might become useful in the future. Templates should be used sparingly imo.
- - CJ talk / cont 05:33, 8 November 2006 (EST) -
- Eirik Ratcatcher 14:27, 22 March 2007 (EDT) - see my comments above
- // DarkRyder /
/
// 16:57, 25 June 2007 (UTC) - There's simply no reason for most of these to be "global" templates; {{Blood elf traits}} should be Blood elf/Traits, {{Cosmos}} should be Cosmos/Menu or some such, etc.
- --Pcj (T•C) 20:25, 29 June 2007 (UTC) - Templates should be anything with parameters or used in...I'd say at least 3 articles. Otherwise, not much reason for them to be templates.
No, they stay in the "Template:" namespace
- Schmidt 16:23, 2 June 2006 (EDT)
- Bevans (FeldmanSkitzoid) 12:18, 15 August 2006 (EDT) - Um...I'm a bit confused. Here's my thought on Templates: anything that will be used on more than one page should be able to be a template. It makes it a lot easier to keep these pages up to date if we don't have to go and edit several pages when Blizz changes something. For example, the Racial Traits page. Each entry is also used on the corresponding race's info page. It may only be 2 pages accessing each template, but it allows for greater consistency and decreases the chances that mistakes/errors will be made.
- Rahskala 12:32, 15 August 2006 (EDT) - IMO, even templates of marginal/infrequent use should be placed in the Template: namespace just for the sake of consistency. There's always the possibility that a local template might suddenly become 'globally' useful in the future when somebody decides to expand a particular area of WoWWiki that is lacking information today.
- Cynric 11:40, 11 October 2006 (EDT) - I'm new here and just trying to catch up on things (thanks Mikk for the links). As, Bevans stated, if it is redundant content, templates help out a lot with keeping pages small[er] and facilitates updates. I also agree with Rahskala about consistency.
- Tusva 15:15, 25 October 2006 (EDT) - There should be a reliable way to both identify templates as well as browse through them. This would allow future editors to perhaps find and use an existing template rather than try to create his/her own. It also keeps things organized and allows us identify where to make broad changes to articles (that have Templates used) when and if needed.
- Rukkyg 20:44, 28 November 2006 (EST) - Templates should be easily accessible and that means in a template namespace. Templates should be used as often as possible. Ever try to code in HTML with navigation before php's include() and require() functions? However, making random tables in to "templates" just because is not good practice. In my experience, templates are best used as a navigation tool, not a content tool.
- Zeal 00:58, 26 December 2006 (EST) - Template namespace is helpful for quick use, but they should not be in the template namespace unless they are templates helpful to all users. I think they need to be looked at again in terms of if other users could use the templates. If the answer is no, then remove them from the categories, and then move them back to user pages of the author. I'm too tired to offer any further input.. I keep my templates in userspace if they're just for me, and don't add them to a template category.
Comments
I think it might be important to note the discussion above, for the scope of "majority". In any case, I feel that some – maybe most – of these (as of writing) should remain in the template: namespace. Mikk disagrees. Maybe more others agree one way or another. That's pretty much the sum of it. Schmidt 16:23, 2 June 2006 (EDT)
- Roflcopter. I need to have my head checked. "I want this to go somewhere, I'll start a vote on it." <-- st00pid. --Mikk 07:20, 13 June 2006 (EDT)
- lol. C'est la vie. Too bad no one else has anything to say on it. Schmidt 07:56, 13 June 2006 (EDT)
Wow, this one was at a standstill for a while, wasn't it? :) --Rahskala 12:32, 15 August 2006 (EDT)
Most tables that are in: Category:Templates_that_should_have_been_local, can probably be moved here Category:Tables CJ 08:12, 30 October 2006 (EST)
- Not sure. See Category talk:Tables. --Mikk (T) 08:39, 30 October 2006 (EST)
- Ok, we ended up making Category:WoW table templates the place to put listings of stuff, and Category:WoW table helper templates the place to put snippety things (table headings, rows, etc... without actual content)
I still don't get it
Have you people even looked at the list? I was asking for the opinion of "most" templates in the category.
Something like 80-90% of them are pulled in in one single place:
- Template:Tables:ReputationMobs:Argent Dawn and all the other reputation templates
- Template:Tables:Talents:WarriorProtection and all the other talent templates
- ... and many like them
I'm not even sure that these should be templates to begin with. Looks like regular page content to me? o.O
--Mikk (T) 03:40, 31 October 2006 (EST)
- Split off content Keeps the original page smaller and easier to edit, reputationmobs page needs to be split off to pages accordingn to each faction however, or moved to their faction page (the page is too big to edit normally). Makes sense to have the tables on a seperate page which can be called locally, less scrolling, faster loading, smaller history page. CJ 04:41, 31 October 2006 (EST)
- Yeah, but there's lots of pages that are split up that way. And the vast majority just use subpages, not stuff in the template namespace. Examples include WoWWiki:Community portal, Help:Contents, Help:Editing... --Mikk (T) 06:27, 31 October 2006 (EST)
- Hmm. got a point though. Enchantment , just made Enchantment/Tables/Armor/Head, as it's full page content, only used on that page. probably fits best locally there, but with a special "local templates" category ( Category:Misc local templates ) attached to the "noinclude". some things such as those reputation mobs, would likely only be used on that page.. could perhaps be moved to act locally. CJ 03:10, 3 November 2006 (EST)
Fixed
I fixed most of them; I really don't think the Cosmos templates should be local, however. --Pcj (T•C) 15:13, 11 July 2007 (UTC)