వికీపీడియా:Requested templates

"WP:RT" redirects here. You may be looking for Redirect templates or Requests for translation.

For users unable to create new pages (new users, or anonymous users), who wish to code a template themselves, see Wikipedia:Articles for creation

వికీపీడియా:Requested templates/Interwiki Add new requests for a new template or updates to existing templates to the bottom of this page. Please be clear about what the template is used for, roughly what it should look like, and which articles it should link to, if any.

For requests regarding stub templates, go to Wikipedia:WikiProject Stub sorting/Proposals.

A general description and guideline for userboxes can be found at Wikipedia:Userboxes. A detailed instruction to use the userbox template can be found at Template:Userbox. For requests regarding userboxes, go to Wikipedia talk:Userboxes/Ideas.

Add wikisource support to poem infobox

It seems there is no support for a wikisource link in a poem infobox as there is in a book infobox. Can this functionality be added? ie:

{{Infobox poem
...
...
| wikisource = The Raven
}} — ఇక్కడి సంతకం లేని వ్యాఖ్య రాసినవారు: Aschuess (చర్చ • రచనలు) 03:26, 14 March 2013‎

 చేసాను --207.62.160.91 (talk) 06:15, 20 March 2013 (UTC)

want cross-references when an article is moved but the talk is not

I request two templates, to solve the problem of when an article is merged leaving behind a redirect but the merged article's talk page is kept in place, resulting in talk topics for the destination article being found on two talk pages, including when one or both pages are archived. Once the second talk page is started, a history merger of the talk pages is almost always inappropriate, because it is not a true merger but an overwriting and there's a need to preserve old content and attributions for copyright reasons. So the talk pages should be kept but readers of either should be told of the other. Cross-references between current talk pages are needed. (They're not needed on archival pages.)

I created similar messages on both models, but using the {{Notice}} template, at Talk:Wife selling (Chinese custom) (post-redirection) and Talk:Wife selling (destination). I did not find any similar or related template and I don't remember ever seeing a similar situation on another talk page.

The destination article's talk page should tell readers that a companion talk page can be found where the old talk page was. The talk page for the former article that is now a redirect should have a notice discouraging talk except to improve the redirect but otherwise recommending that talkers go to the destination article's talk page.

The default text should not speak of merger because, to be precise, that is not always the process, and move seems generic enough. I'm not sure the losing article would always be a redirect; I suppose it's possible (although apparently lately uncommon) for an article to be deleted but the talk page kept (I have seen an archive kept when both the article and the current talk page were deleted), and therefore the default text should not assume that the losing page is a redirect. It also should not be assumed, when drafting the default text, that a redirect will always stay a redirect. Each new template should have a parameter for naming the other talk page and that parameter should be mandatory. Both should have icons; the destination page's template should have an icon for a notice while the former article's talk page's template should have an icon for a stop sign. Substitution probably should not be used.

One could be named Template:Talk_destination. I don't know what to name the other (Template:Talk_...).

The notices I created can, presumably, be replaced with the new templates.

Thanks. Nick Levinson (talk) 16:07, 30 June 2013 (UTC) (Corrected phrasing and moved text: 16:15, 30 June 2013 (UTC))

tables with floating header row

check out the big table on this page:

once I've scrolled past the header, I can't see it without scrolling back up, which bugs the crap out of me when I'm trying to compare countries.

So what is the solution?

a) the table header row should float down with me while the table is on the screen

b) (regarding comparing rows) a filter by [header key]:[verb]:[value] directive.

eg. Filter by 'Nation' 'equals Israel' OR 'contains Palestin' would let me compare the row for 'Israel' and 'Occupied Palestinian Territory' (the 'contains' verb would allow me to not have to know what they called those territories here now) and then compare them side by side.

Downtowncanada (talk) 16:51, 3 August 2013 (UTC)

Hi Downtowncanada! I think there are no such features existing in Wikipedia. Some editors have already requested for the floating headers to be made possible[1]. ···Vanischenu (mc/talk) 13:51, 5 October 2013 (UTC)

Ramesh Kshitij

You are kindly requested to help me to add standard templates to add Ramesh Kshitij page and i want to standardize it with notably.

Neelatmg (talk) 21:57, 22 September 2013 (UTC)

tentatively request template for talk xref

A talk page may really be about a closely-related talk page, such as if an article was merged or redirected but the talk page was not and might or might not still be in use. The two best solutions seem to be to move content from one talk page to the other or to add a message box high on each talk page cross-referencing the other. Moving risks losing a history for attributions, needed because of copyright; that could happen if a now-empty talk page is associated with an article or a redirect and both the article or redirect and the associated talk page are deleted. Adding a tag is easier. I've already created custom messages for a couple of talk-page pairs. I don't know if anyone else has done this. I don't know if we need a standard template for the purpose, but I understand there is a preference that if a message has to be posted enough times then it should be made into a template. These are cases I know of:

• Talk:Rafael Viñoly paired with Talk:Rafael Vinoly
• Talk:Wife selling referencing Talk:Wife selling (Chinese custom) (the latter opposes new topics)

This does not have to be designed all at once to be at least minimally useful. A simple template can be made somewhat more sophisticated later.

I suggest that text be from a choice of two sentences and a custom string and that there be one parameter for the talk page to be referred to. The two sentences, the first being the default:

• There is additional content at
• There may be additional content at

Either sentence or the custom string would be followed by the destination (as a link) and a period.

Designing to be small seems to be visually good.

It may be useful to advise readers normally to post to one or the other to the exclusion of current practice. To that end, a choice of two additional sentences could follow the basic sentence, separated by a space, using one optional parameter:

• Future topics for either talk page generally should be started on the [[...|other talk page]], not this one.
• Future topics for either talk page generally should be started on [[...|this talk page]], not on the other one.

The ellipsis would be replaced by the value of the parameter for the other talk page or by the current talk page's title, respectively. If topics could generally be started on either talk page, the parameter would not be applied.

A final optional parameter could support a custom string.

If it is desired to be especially emphatic in discouraging starting new topics on the current talk page, a parameter might make the box not small, replace the icon with a more intense choice, and apply a more directive sentence, such as:

• Please do not post any discussion here unless you are posting about the present ... [page/article/redirect/other]. Previous ... [page/article/redirect/other] contents were merged into ... [destination] and any new discussion should be posted to Talk:... [destination].

I don't know if a maintenance category is needed, but adding it can wait, since its effect would be retroactive for pages still tagged.

Nick Levinson (talk) 21:43, 5 October 2013 (UTC) (Corrected a talk page title: 21:49, 5 October 2013 (UTC))

Do we have a collapsible box that expands to full width?

Our current collapsible templates seem to have fixed width. I would like a collapsible box that, when expanded, changes its width to 100%.

Something that could we could float right and allowing article text to wrap-around, but when expanded could take up the full width of the column.

Do we already have that? if not, is it possible to create it? --HectorMoffet (talk) 19:57, 27 November 2013 (UTC)