Help talk:Wiki Templates

Categorization

Currently all wiki templates are categorized as Category:Wiki Template. Since there are less than 100 templates this is probably best, however as more get added some consideration should be made for subcategories. However because these are highly arbitrary (lots of possible names for the same thing, see Wikipedia for examples both bad and good of template category names). Therefore I wanted to start making suggestions now and allow others to do so as well so that when the time comes to make them we have good selections that can withstand a cold eye. Navigation Template - to include any template that is primarily composed of links to other pages, including Table of Contents templates. Article Archive Template - to include internet archive templates and any utility templates that aid in archiving content. Table Template - table and row templates. Stats Box Template - to include all templates that mimic an in game stats ID panel. (this one is highly arbitrary name, not sure if I like this name best) Code Element Template - very nuts and bolts template that's used all over the place (again very arbitrary name, not sure) Whatlinkshere Template - templates that present a variation of a Special:Whatlinkshere/Wiki Templates link. Message Template - warning and informational messages. Summary Template - templates that present basic important information in a summary box. Please feel free to suggest other subcategories or alternate names for those I or others suggest. --Tlosk 11:56, 23 June 2009 (UTC)

"Stats Box Template" - Assessment Template or Assessment Panel Template? --An Adventurer 16:58, 23 June 2009 (UTC)

Usage Scope

These template fragments are really great. Do you have an end goal on how much you'd like to use them for? I could imagine that we could use them for just about everything in the wiki. --Atarax 10:24, 6 January 2009 (CST)

Late response but an important question. I think it's important to have a balanced approach because I believe utility is a function of template quantity/complexity and the function is an inverted U (upside down). Too few templates and things are harder than they need to be. Too many and things get too complicated and fragile (especially when templates begin nesting many layers deep like on Wikipedia). It can also hide how to do things which makes it harder for new people to learn the wiki markup. These aren't hard and fast rules but things worth considering making a template for are: Widely used - any code or text that is identical and used on many pages, especially when it might change in the future. Complicated or verbose formatting that is used on many pages, this makes it easier to use. Efficiency - if it will make the contribution process faster and less prone to errors. New functionality - some things would be too complicated to do with wiki code on each page would be hard for most users to edit it. Considerations against: Content is highly variable and would require lots of special rules and exceptions for a template to work for all of them. Content that would only be used in a handful of pages, and especially when only used in one place. Content that will often need customized wiki code to change the layout/format/appearance. Small payoff for the time investment, some templates can take a long time to code and debug, compare with what the benefit of the template will be. --Tlosk 11:56, 23 June 2009 (UTC)