See something you'd like to change or add, but you've never edited an open encyclopædia before? This overview was written to help absolute beginners get started.

aSK talk:Template list

From A Storehouse of Knowledge
Jump to: navigation, search


Missing welcome template

why no welcome template? Taj 08:16, 26 March 2009 (UTC)

Because "somebody" hasn't added it to the list. Philip J. Raymentdiscuss 10:50, 26 March 2009 (UTC)
Wow, the list has grown really fast! So many more templates than just 2 days ago! I wish I knew how to make templates, but luckily you have plenty of technical people here. :-) Taj 08:09, 29 March 2009 (UTC)

Bible verses on templates

I suggest adding suitable Bible verses to aSK's maintenance templates. This would have the following benefits:

  1. It would help embed A Storehouse of Knowledge's identity as an encyclopædia grounded in the Bible.
  2. It would make these templates more interesting, and different from those on other Wikis, again helping aSK to develop a distinctive identity.
  3. It would refer readers to Bible passages that they might not be aware of.
  4. It would help people keep the religious purpose of this enterprise in mind while undertaking routine maintenance activities.

As a couple of initial suggestions, I propose the parable of the mustard seed for the Stub template, and Psalms 58:7 "Let them vanish as water that flows away" for speedy deletion.--CPalmer 13:45, 7 April 2009 (UTC)

I like the sound of that, but for a newcomer to the site it may be confusing as to why those verses are on a page about, say, Kenya. Perhaps we could add a guide or a key to the style manual or some other likely-read introductory page? --שεṣĿεўŚЅρƏäќëŕfáčΣ 20:28, 7 April 2009 (UTC)
The average visitor will not read any intro page. The average editor maybe, but seriously, did you read any of Wikipedia's About and Help pages the first time you looked something up? This is also one of the reasons why I opposed cutting "According to The Biblical Worldview..." from the intro sentences before I changed my mind. --Sid 20:35, 7 April 2009 (UTC)
It would have to be clear from the template design that the verse is part of the template. I'd envisaged, for example, the speedy deletion one being a box with a standard message about speedy deletion in normal-sized writing, and the Bible verse in smaller italics in the bottom right.--CPalmer 08:15, 8 April 2009 (UTC)
OK, that makes sense then. --שεṣĿεўŚЅρƏäќëŕfáčΣ 15:11, 8 April 2009 (UTC)
If you're gonna have a bible quote, why not put (a random?) one on every (mainspace?) page - in either the footer or the left column? I'm sure it could be managed as part of the skin or as a "toolbox" addition. User 11speak to me 12:51, 11 April 2009 (UTC)

Copyright template

We need an image copyright template for images that are copyright but used with permission. Philip J. Raymentdiscuss 12:19, 11 April 2009 (UTC)

Can you copy : over? (assuming you haven't got it already) User 11speak to me 13:08, 11 April 2009 (UTC)

We also need several other image copyright templates - for example, works that are public domain because they're by the US government, works that are public domain because they're 70 but not 100 years old (and therefore PD under US copyright law, let alone Australian which has a 50-year term), et cetera. Also, what's your take on recent photographs of ancient paintings/sculptures/documents? Wikipedia considers them public domain, but do we? --EvanW 02:54, 18 February 2010 (UTC)

Conservapedia's long had an interesting link on its main page: It explains the (U.S.) situation on the copyrightability of photographs of paintings, and I guess it would apply to photographs of documents also, although not to sculptures. Philip J. Rayment 10:56, 18 February 2010 (UTC)


I'd recommend that templates be protected. Things can be snuck in (remember CP's "Atheism" [or was it liberal?] template?) which might be missed by the casual observer but get plastered all over the wiki. ;-) User 11speak to me 13:24, 11 April 2009 (UTC)

BUT WAIT UNTIL I'VE CATTED THEM! ;-) User 11speak to me 13:53, 11 April 2009 (UTC)
Too late! Seriously, this is a reason to not protect them. On Conservapedia, I argued that a blanket locking of templates was not warranted, and only templates used on the main page plus high-use ones should be locked. We now have cascading protection, so any used on the main page are automatically locked. I've just locked four of the top five templates. I left {{elements}} unlocked as there could well be changes required. Apart from the {{welcome}} template, the rest are very basic ones that will not likely need changing. And the ones further down the list are not really high-enough use to warrant protection, I believe. Nos. 6, 7, and 10 are only used in template documentation. No. 9 is cascade locked. Philip J. Raymentdiscuss 14:06, 11 April 2009 (UTC)


The number of userboxen will probably grow out of proportion to the rest of the templates: might be better on a sub-page? User 11speak to me 13:28, 11 April 2009 (UTC)

Bump. They clutter up the page & render others less easy to find. 11:06, 18 May 2009 (UTC)User 11speak to me
I've commented on this somewhere else some time back. I agree that they should be moved to their own page once there gets to be too many for this page. How many is too many? I don't know. If someone wanted to move them now, I've no objection. Philip J. Raymentdiscuss 13:02, 18 May 2009 (UTC)


NB: The first three posts were moved here from user talk:Philip J. Rayment

I reorganised the template list slightly. It should make it much easier to find something you're looking for, as you can scan the list for the template you remember rather than having to guess at the name or skim through the notes section. The "appearance" tab is disabled by default, because it wreaked havok with the page formatting, but it can be switched on for individual templates. Just FYI, feel free to revert if you don't approve. New3.pngPink(Inertia presides over burnt modernist strides) 13:43, 11 May 2009 (UTC)

I'm not going to approve or disapprove, but I will comment that I'd wondered myself about putting the listing(s) into a table, but hadn't come up with a satisfactory way to do it. The tables with varying-width columns looks a bit ugly, in my opinion. As for the appearance column, you've really only used that for user boxes and boilerplate text, and if the userboxes are moved to a separate page (there's close to enough now to warrant it), then it's left with the appearance column being used in one section only, which seems rather a waste of space. Philip J. Raymentdiscuss 15:22, 11 May 2009 (UTC)
The columns should indeed be a consistent width. They aren't at the moment, but only because I'm not sure how to do that.
The appearance column is disabled for most templates at the moment, but it can be used for almost all of them -- it works for any template that has an appearance. I am about to enable the ones that work, so you can see what it should look like in a second... New3.pngPink(Inertia presides over burnt modernist strides) 15:41, 11 May 2009 (UTC)
The only way to make the columns the same width is to specify their width. This can be done by specifying pixels, ems, or percentage, although pixels are never a good idea (account different screen resolutions). Whether to use ems or a percentage depends on whether you want to allow the column width to vary according to the user's screen resolution. Ems for the first column, for example, would be a good idea, but not for the others. Of course the problem is that you need to allow for the widest item to go in the column, thereby potentially wasting space on many others.
Although there is some merit in showing what the template looks like, I'm inclined to think that it creates more problems than it solves. I can see the following problems:
  • A number of the templates have a heading "Template list". This is understandable, as they are designed to default to the page name, but it still doesn't look the best.
  • A number of the templates add a category to the page, so the template list now has nine categories, none of which are applicable to the template list. Each individual template can be edited to solve this (I've made one or two templates that only add a category if they are used in a given namespace), but that seems like a bit of overkill just so that we can show the templates here.
  • The default for many templates looks rather a mess, as those ones are designed to be used with parameters that are not here supplied.
  • The page is much bigger as a result.
Keep in mind also that this page is intended to be a ready reckoner only, and that users really should go to the template page itself to find out more about a template, including what it looks like, how to use it, and what parameters are required. Given that, and the problems I've listed, I don't think we should be showing their appearance.
Philip J. Raymentdiscuss 02:47, 12 May 2009 (UTC)
I think you're right. I'll remove the appearance option from the template. New3.pngPink(Inertia presides over burnt modernist strides) 14:07, 13 May 2009 (UTC)


I wonder if somebody who is good at templates would consider something like CP's {{Reflist}}, which replaces the rather cumbersome <small><References/></small> (especially for those of us who can never remember which way the "/" goes). -- KotomiTOhayou! 07:42, 18 May 2009 (UTC)

I think "CP's" reflist was copied from WP, but regardless, {{reflist}} already exists. The 'navigation' box in the left column has a direct link to a list of all (? hopefully) templates. Philip J. Raymentdiscuss 09:54, 18 May 2009 (UTC)
Ah, thank you Philip! I think I need new glasses! -- KotomiTOhayou! 10:37, 18 May 2009 (UTC)
You're not the only one. I didn't realise that I was posting this on the template list talk page! Philip J. Raymentdiscuss 13:01, 18 May 2009 (UTC)


Would it be possible for somebody, better at coding than me, to create an infobox for the countries? I do not think it needs to be as detailed as say WP's, but should have place for basic info, such as:

  • Flag
  • Map
  • National anthem
  • Pres/PM
  • Area
  • Population

and anything else that might be relevant. -- KotomiTOhayou! 08:01, 20 May 2009 (UTC)

With my limited knowledge of coding I can make one, but it will pretty much look the same as Template:Band. I only know enough to change out all the info categories. FernoKlumpDrugged-up Communist! 15:37, 20 May 2009 (UTC)
Nevermind, I see that Pink already made one. FernoKlumpDrugged-up Communist! 15:39, 20 May 2009 (UTC)
She (He? oh dear, I do not know) did, and they are a star for helping. I am busy in my sandbox at the moment playing around with it and figuring out what goes where so I can tweak it a bit. -- KotomiTOhayou! 15:45, 20 May 2009 (UTC)
"She (He? oh dear, I do not know)" -- Hee hee hee hee. ^_^ New3.pngPink(Inertia presides over burnt modernist strides) 03:48, 21 May 2009 (UTC)

Automatic list?

I believe that it would be possible to generate the template list automatically, by using SMW properties in the template documentation, then converting the template list page to be a series of SMW inline queries. However, there is a catch, and I'm not sure that it's worth doing. To achieve this automation, we would have to:

  • I would have to alter the SMW configuration to scan template namespace for SMW properties. This is off by default. This is a once-off, so is no problem.
  • Modify the {{template doc}} template to facilitate this. This is a once-off change, so is no problem. This is to provide for the next point.
  • People creating templates would need to add a brief description to the documentation of each template, in an additional parameter to the {{template doc}} template. We already do this, except that we do it on the template list page, so it's no extra effort. Rather, it can be done with the other documentation, so is actually a bit easier.
  • The automatic list would group templates according to the category (or categories) they have, so each template would need a suitable category, but this is something that we would be doing anyway.
  • We would need to add <includeonly></includeonly> tags around every occurrence of a property declaration in a template, both existing and new. This is likely to mainly effect info boxes, as they would be the main ones which declare properties for some of their fields. This is to avoid these properties being treated as properties of the template.

The last point is the main problem, although not a big problem by any means, but it's an extra burden which may not outweigh the single advantage of making the template list automatic.

Any opinions?

Philip J. Raymentdiscuss 08:00, 6 October 2009 (UTC)


The xkcd cartoon is actually under a Creative Commons Attribution-NonCommercial 2.5 License, and we need a template for that. Steriletalk 13:23, 9 July 2014 (UTC)

Personal tools

visitor navigation
contributor navigation