Difference between revisions of "Template talk:Outdated"

From DoomWiki.org

m (woops)
(Problems)
Line 3: Line 3:
  
 
Also, do not ever subst any BaseInfoBox template into an article. The entire point of the system is that descendent templates respond to design changes in their parents, so that the generated HTML can be changed if necessary, and styling is kept consistent across related notice types. I would like to have that suggestion removed from the template documentation. --[[User:Quasar|Quasar]] ([[User talk:Quasar|talk]]) 15:35, 10 August 2014 (UTC)
 
Also, do not ever subst any BaseInfoBox template into an article. The entire point of the system is that descendent templates respond to design changes in their parents, so that the generated HTML can be changed if necessary, and styling is kept consistent across related notice types. I would like to have that suggestion removed from the template documentation. --[[User:Quasar|Quasar]] ([[User talk:Quasar|talk]]) 15:35, 10 August 2014 (UTC)
 +
 +
: I took out the substing part — testing showed it was a bad idea anyway because not recursive, so any extra categories still would need manual removal.  (Though if someone seriously attempted to recreate such a guideline, old template formatting would be the least of their adversity.)  I see you've added a maintenance subcategory, which makes sense; thanks.  Still thinking about your other paragraph.    [[User:Ryan W|Ryan W]] ([[User talk:Ryan W|talk]]) 23:06, 11 August 2014 (UTC)

Revision as of 18:06, 11 August 2014

Problems

I feel the suggestion made by this template is less than helpful. If an editor cannot get clear word on our policies by reading the articles that supposedly expound them, then editing this wiki is a useless proposal to anybody without the guts to be bold. This is a situation we need to have some balls to get out of, either by laying down policy, or by not having a policy at all. I'm not opposed to use of the template to point out these kinds of situations (which it does not do effectively currently, vis-a-vis lack of an auto-category to collect such problems for future review), but use of it as a permanent white flag of surrender is not positive either.

Also, do not ever subst any BaseInfoBox template into an article. The entire point of the system is that descendent templates respond to design changes in their parents, so that the generated HTML can be changed if necessary, and styling is kept consistent across related notice types. I would like to have that suggestion removed from the template documentation. --Quasar (talk) 15:35, 10 August 2014 (UTC)

I took out the substing part — testing showed it was a bad idea anyway because not recursive, so any extra categories still would need manual removal.  (Though if someone seriously attempted to recreate such a guideline, old template formatting would be the least of their adversity.)  I see you've added a maintenance subcategory, which makes sense; thanks.  Still thinking about your other paragraph.    Ryan W (talk) 23:06, 11 August 2014 (UTC)