Template:Main talk other/doc

This is the main talk other meta-template.

This template is used inside other templates that need to behave differently (usually look differently) depending on what type of page they are on. It detects and groups all the different namespaces used on TechInfoDepot into three types:


 * main = Main/article space, as in normal TechInfoDepot articles.
 * talk = Any talk space, such as page names that start with "Talk:", "User talk:", "File talk:" and so on.
 * other = All other spaces, such as page names that start with "User:", "File:", "TechInfoDepot:" and so on.

This page is also the documentation for some other templates:


 * main talk other flex – It works exactly the same, but it has some minor internal differences. Read more about that below.


 * main talk category other – It works exactly the same, apart from that it uses the type category for pages that start with "Category:", but it still uses the type talk for "Category talk:" pages.


 * main other, talk other, file other and category other – Simpler versions that only differentiate between one type of page and all other.

Basic usage
This template usually takes three parameters, and returns one of them depending on which type a page belongs to. Like this:



If the template is on a main space (article) page, it will return this:



If the template is on any talk page, it will return this:



If the template is on any other page (such as this template page and its doc page), it will return this:



If you only feed a parameter for one or two of the types then this template returns an empty string for the rest of the types. That is, if it for instance is used in one of these ways:



Then it doesn't render anything in mainspace and other space.



If this template is used without any parameters or only fed empty parameters (empty strings), then it returns an empty string. That is, then it renders nothing.



The extended main talk category other template instead takes four parameters, also in the same order as the words in its name. Like this:



which renders like this:



For testing and demonstration purposes these templates can take a parameter named demospace: if it has any of the values main, talk or other it makes the template behave as if it is on a page of that type; if the parameter is empty or undefined, the actual page type determines the result.

Usage example
This example creates a message box, but these templates can of course be used for many other things than message boxes. This example uses numbered parameters and HTML tables, for the reasons why see the technical details section below.

Which renders like this:

Let's see how it looks on talk pages. So we change the first line in the code to this:

{{main talk other|demospace=talk

This is how it will render on any talk page:

{{main talk other|demospace=talk }}
 * 1 = This messagebox should not be used in articles.
 * 2 = {{tmbox|text=Talk page notice}}
 * 3 = {{ombox|text=Other pages notice}}

And now let's test it for article pages:

{{main talk other|demospace=main

This is how it will render in an article:

{{main talk other|demospace=main }}
 * 1 = This messagebox should not be used in articles.
 * 2 = {{tmbox|text=Talk page notice}}
 * 3 = {{ombox|text=Other pages notice}}

Additional code
Too make this example complete, here is the rest of the code that is needed to make it a fully equipped template:

The line " " means that your template also will understand the demospace parameter. That means you can demonstrate the different appearances of your template in the documentation for your template.

The " " template creates a green documentation box, like the one you are reading in right now.

Numbered parameters and HTML tables
Templates have a problem to handle parameter data that contains equal signs " ". But that is easily solved by using numbered parameters, such as " " and " ".

Templates also do have a problem to handle parameter data that contains pipes " ", unless the pipe is inside another template  or inside a piped link. Thus templates can not handle wikitables as input unless you escape them by using the template. This makes it hard to use wikitables as parameters to templates. Instead the usual solution is to use "HTML wikimarkup" for the table code, which is more robust.

The simplest way to include tables that use wikimarkup is to transclude them as a subtemplate.

Comparison
main talk other and main talk other flex behaves exactly the same but internally uses different code:


 * will still correctly detect all talk pages even if new namespaces are added to TechInfoDepot. The talk page and main space detection functions are also shorter and thus nicer if you want to copy them to use them elsewhere:


 * is more flexible in that its code is much easier to modify to detect any combination of namespaces as one wishes. But please copy the code to a new template before you do such modifications.


 * If a new namespace is added to TechInfoDepot then needs to be manually updated, otherwise it will detect the new talk space as type "other". Fortunately new namespaces is a very rare event.

So if you just need to detect main, talk and other then use. But if you want to detect other combinations then copy the code from.

main talk category other also will correctly detect all talk pages even if new namespaces are added to TechInfoDepot.

Copying to other projects?
If you copy these templates to another language TechInfoDepot or other Wikimedia project, then should work as is, but you probably want to update the template's name and its parameter names to your local namespace naming. But you must update the code of and  to your local naming and add any extra namespaces that are local to your wiki, otherwise they will malfunction.

CSS namespace detection
CSS code can be used instead of these templates to detect namespaces. This can be used for those things that can be coded as CSS, such as colours and borders. See example on the talk page.