Template talk:Documentation

From Wikipedia, the free encyclopedia

Contents

[edit] Use

Using :

<noinclude>{{documentation}}<noinclude>

will cause the documentation to show in the template when used. This should be:

<noinclude>
{{documentation}}</noinclude>

Ed

Fixed, thanks. --PEJL 18:01, 22 October 2007 (UTC)
Thanks. I thought I was doing something crazy for a few minutes.  :-) --Gadget850 ( Ed) 18:08, 22 October 2007 (UTC)

[edit] Reverted 20:51, November 3, 2007: Subsection edit links issue

Edits made 2007-11-02 and 2007-11-02 break subsection edit links. I shall revert those edits immediately.
To illustrate the issue the last version before reversion was copied to {{Documentation/sandbox}} and a test cases page was created at User:ConradPino/template/documentation.
Conrad T. Pino 20:50, 3 November 2007 (UTC)

[edit] Failing code analysis

{{#ifexist:{{{1|{{SUBJECTPAGENAME}}/doc}}}|{{{{{1|{{SUBJECTPAGENAME}}/doc}}}}}}}

{{ #ifexist:{{{1|{{SUBJECTPAGENAME}}/doc}}}|{{ {{{1|{{SUBJECTPAGENAME}}/doc}}} }} }}

{{ #ifexist:page|{{ page }} }}

The problem is a template expansion

{{ page }}

occuring within a parser function

{{ #ifexist:page| {{ template expansion of page }} }}

Conrad T. Pino 22:03, 3 November 2007 (UTC)

[edit] Recommendation

Invert the structure to parser function within template expansion

{{             template expansion            }}

{{ {{           parser function           }} }}

{{ {{#ifexist:page|page|Documentation/none}} }}

{{ {{#ifexist:{{{1|{{SUBJECTPAGENAME}}/doc}}}|{{{1|{{SUBJECTPAGENAME}}/doc}}}|Documentation/none}} }}

Conrad T. Pino 22:17, 3 November 2007 (UTC)

[edit] Revision 1

When first implemented {{Documentation/none}} contained

<!-- Template:Documentation/none -->

This revision blanked {{Documentation/none}} at 23:33, November 3, 2007 – Conrad T. Pino 08:28, 6 November 2007 (UTC)

[edit] Revision 2

Borrow from {{Template doc}} and eliminate the {{Documentation/none}} page.

{{      template expansion     }}

{{ {{    parser function    }} }}

{{ {{#ifexist:page|page|ns:0}} }}

{{ {{#ifexist:{{{1|{{SUBJECTPAGENAME}}/doc}}}|{{{1|{{SUBJECTPAGENAME}}/doc}}}|ns:0}} }}

Conrad T. Pino 08:39, 6 November 2007 (UTC)

[edit] Implementation complete

In the spirit of be bold and only after careful testing the Recommendation (above) was implemented taking care to lead with a new line. The differences are here.

Note: Page {{Documentation/none}} must NOT be deleted!

Conrad T. Pino 22:40, 3 November 2007 (UTC)

[edit] Implementation reverted

See Reverted 23:36, November 3, 2007 to 17:20, October 20, 2007 version below. – Conrad T. Pino 00:09, 4 November 2007 (UTC)

[edit] Failure analysis

When first implemented {{Documentation/none}} contained

<!-- Template:Documentation/none -->

which is definately NOT the similar to the empty or space strings. This is no longer the case as I blanked {{Documentation/none}} at 23:33, November 3, 2007 which made it possible for another user to restore the implementation with no reported incidents. – Conrad T. Pino 06:12, 6 November 2007 (UTC)

However failure to find an incident report on this talk page doesn't mean one didn't happen. The restore was reverted again by a third user. – Conrad T. Pino 06:26, 6 November 2007 (UTC)

[edit] Reverted 23:36, November 3, 2007 to 17:20, October 20, 2007 version

[edit] Problem report

[edit] Re: Template:Documentation reverted 20:51, November 3, 2007

Hi there. I don't understand what problem you were trying to solve at Template:Documentation, but you've broken the template so that it includes too much whitespace at the beginning. See WP:SONG#Infobox Single. As I don't understand the code well enough to fix it, would you mind trying to restore the previous behavior, where such excessive whitespace was not generated. Thanks in advance. --PEJL 23:30, 3 November 2007 (UTC)

[edit] Revert request completed

But that doesn't seem to help the reported problem. I'll assist in anyway possible. – Conrad T. Pino 23:45, 3 November 2007 (UTC)

That did fix it. (Sometimes you need to purge the page to see these kinds of changes.) --PEJL 23:47, 3 November 2007 (UTC)
Thank you for letting me know. – Conrad T. Pino 00:01, 4 November 2007 (UTC)

[edit] Merge from Template:Template doc

The merge proposal discussion occured here. – Conrad T. Pino 08:14, 6 November 2007 (UTC)

[edit] Merge goals proposal by priority

0. Remove "...transcluded from..." display inconsistency.
1. No functional differences.
2. No visual differences.
3. Improve /sandbox and /testcases support. (Wikipedia:Template test cases)

Conrad T. Pino 08:56, 6 November 2007 (UTC)
Conrad T. Pino 22:58, 11 November 2007 (UTC)

[edit] Functional issues

[edit] SUBJECT... versus FULL...

This section is archived: Template talk:Documentation/merge/archive/2.1

[edit] (2.2) Documentation /doc use cases

[edit] (2.2.1) /doc best practice

The best practice provides designed behavior with least maintenance.

[edit] (2.2.2) /doc acceptable practice

The acceptable practice provides designed behavior with more maintenance.

[edit] (2.2.3) /doc questionable practices

The questionable practices visibly deviate from designed behavior.

The above list is not comprehensive but I stop here since visible behaviors become noticable and therefore hopefully corrected soon after discovery. – Conrad T. Pino 22:37, 11 November 2007 (UTC)

[edit] Template behavior differences

{{Documentation, template}} transcludes {{Documentation}} and unless explictly stated otherwise any {{Documentation}} behavior described here applies to both.
Conrad T. Pino 00:21, 16 November 2007 (UTC)

[edit] Display heading and content
(template icon) Template documentation
(no icon) Documentation
(template icon) Template documentation

Conrad T. Pino 01:22, 16 November 2007 (UTC)

[edit] Display /doc content

Conrad T. Pino 01:04, 16 November 2007 (UTC)

[edit] Display in-line content

Conrad T. Pino 01:12, 16 November 2007 (UTC)

[edit] Display "...transcluded from .../doc. (...)"
  • {{.../doc}} transcluded (but not always)

Conrad T. Pino 00:21, 16 November 2007 (UTC)

[edit] Template parameter differences

{{Documentation, template}} transcludes {{Documentation}} and unless explictly stated otherwise any behavior described here applies to both.
Conrad T. Pino 00:57, 16 November 2007 (UTC)

[edit] Parameter for in-line content

Conrad T. Pino 00:57, 16 November 2007 (UTC)

[edit] Parameter for /doc path
and then transcluded
1={{ {{SUBJECTSPACE}}:{{{1}}} }}
2={{SUBJECTSPACE}}:{{{1}}}

Conrad T. Pino 00:57, 16 November 2007 (UTC)

[edit] Merge process progress

This section shall track the progress of the merge process as it proceeds. – Conrad T. Pino 07:22, 7 November 2007 (UTC)

[edit] Merge objects

The following templates participate in this merge. – Conrad T. Pino 07:31, 7 November 2007 (UTC)

[edit] Merge from templates

Conrad T. Pino 07:31, 7 November 2007 (UTC)
Conrad T. Pino 12:51, 9 November 2007 (UTC)
Conrad T. Pino 22:00, 9 November 2007 (UTC)
Conrad T. Pino 22:12, 9 November 2007 (UTC)
Conrad T. Pino 22:12, 11 November 2007 (UTC)
Conrad T. Pino 08:49, 13 November 2007 (UTC)
Conrad T. Pino 05:05, 16 November 2007 (UTC)
Conrad T. Pino (talk) 09:30, 17 November 2007 (UTC)

[edit] Merge into templates

Conrad T. Pino 07:31, 7 November 2007 (UTC)
Conrad T. Pino 12:51, 9 November 2007 (UTC)
Conrad T. Pino 21:20, 9 November 2007 (UTC)
Conrad T. Pino 02:08, 10 November 2007 (UTC)
Conrad T. Pino 15:43, 11 November 2007 (UTC)

[edit] Merge objects tagged

The following merge objects now include a merge process template:

Merge Object Merge Process Template
{{Documentation}} {{Mergingfrom}}
{{Documentation subpage}} {{Mergingfrom}} (3 2 1 times)
{{Documentation, template}} (new) {{Mergingfrom}} (new, 2 times)
{{Template doc}} {{Merging}} (not redirectable)
{{Template doc inline}} (later) {{Merging}} (not redirectable)
{{Template doc page}} {{Merging}} (redirect)
{{Template doc page transcluded}} {{Merging}} (not redirectable)
{{Template doc page viewed directly}} {{Merging}} (redirect)

Conrad T. Pino 07:43, 7 November 2007 (UTC)
Conrad T. Pino 13:57, 9 November 2007 (UTC)
Conrad T. Pino 22:08, 9 November 2007 (UTC)
Conrad T. Pino 02:09, 10 November 2007 (UTC)
Conrad T. Pino 15:47, 11 November 2007 (UTC)
Conrad T. Pino 21:36, 11 November 2007 (UTC)

[edit] Merge template subpage directory

The following merge templates have subpages as follows:

Conrad T. Pino 11:26, 7 November 2007 (UTC)
Conrad T. Pino 12:48, 9 November 2007 (UTC)
Conrad T. Pino 22:03, 9 November 2007 (UTC)
Conrad T. Pino 22:19, 9 November 2007 (UTC)
Conrad T. Pino 00:45, 11 November 2007 (UTC)
Conrad T. Pino 21:39, 11 November 2007 (UTC)
Conrad T. Pino 21:50, 11 November 2007 (UTC)
Conrad T. Pino 08:52, 13 November 2007 (UTC)

[edit] Merge into template protection

The merge into templates are protected as follows:

Merge Object Template In Code Current Level Merging Level Permenant Level
{{Documentation}} {{pp-semi-template}} Semi-protection Semi-protection Full-protection
{{Documentation subpage}} {{pp-semi-template}} Semi-protection Semi-protection Semi-protection
Move-protection
{{Documentation, template}} {{pp-semi-template}} Unprotected
Semi-protection		 Semi-protection Full-protection

Conrad T. Pino 02:17, 10 November 2007 (UTC)
Conrad T. Pino 23:17, 11 November 2007 (UTC)
Conrad T. Pino 06:18, 12 November 2007 (UTC) Thank you Pathoschild for this protection edit.

DO NOT implement the permenant protection level until after merge is deemed complete per consensus here. – Conrad T. Pino 23:17, 11 November 2007 (UTC)

[edit] Merge from template protection

The merge into templates are protected as follows:

Merge Object Redirect Target Template In Code Current Level Merging Level Permenant Level
{{Template doc}} (not redirectable) {{pp-semi-template}} Semi-protection Semi-protection Full-protection
{{Template doc inline}} (not redirectable) {{pp-semi-template}} Semi-protection Semi-protection Full-protection
{{Template doc page transcluded}} (not redirectable) {{pp-semi-template}} Unprotected
Semi-protection		 Semi-protection Full-protection
{{Template documentation}} {{Template doc}} {{pp-semi-template}} Unprotected
Semi-protection		 Semi-protection Full-protection
{{Template doc page}} {{Documentation subpage}} Semi-protection Semi-protection Full-protection
{{Template doc page viewed directly}} {{Documentation subpage}} Unprotected
Semi-protection		 Semi-protection Full-protection

Conrad T. Pino 00:22, 12 November 2007 (UTC)
Conrad T. Pino 06:34, 12 November 2007 (UTC) Thank you Pathoschild for this protection edit.
Conrad T. Pino 06:34, 12 November 2007 (UTC) Thank you Pathoschild for this protection edit.
Conrad T. Pino 09:23, 12 November 2007 (UTC) Thank you Patrick for this protection edit.

DO NOT implement the permenant protection level until after merge is deemed complete per consensus here. – Conrad T. Pino 00:22, 12 November 2007 (UTC)

[edit] Merge Phase 1: service templates

The "service templates" are all those templates identified in Merge objects above and are distinguished as documentation service providers for client templates. – Conrad T. Pino 05:17, 16 November 2007 (UTC)

[edit] Service behaviors moved

All Merge from templates behavior occurs soley in the Merge into templates. – Conrad T. Pino 05:17, 16 November 2007 (UTC)

[edit] Full redirection impossible

Three (3) Merge from templates are noted (not redirectable) due to Template behavior differences or Template parameter differences making redirection impossible without breaking client template documentation or creating /doc double {{Documentation subpage}} displays. Once Merge Phases 2 and 3 are complete redirection is moot. – Conrad T. Pino 05:17, 16 November 2007 (UTC)

[edit] Merge Phase 2: client templates

[edit] {{Template doc inline}} clients - completed

After the {{Template doc}} transcludes {{Template doc inline}} link was broken the {{Template doc inline}} links page shrank considerably making manual client editing feasable. Few clients still transclude {{Template doc inline}} and most are in User space or are /testcases created for this merge.

Completing this work requires just one admin edit: Template talk:Tls#Edit requested 16-Nov-2007. – Conrad T. Pino 07:22, 16 November 2007 (UTC)

Y Done - Nihiltres{t.l} 16:36, 16 November 2007 (UTC)
Thank you. – -- Conrad T. Pino (talk) 19:31, 16 November 2007 (UTC)

All {{Template doc inline}} clients are updated and the remaining trancludes are all /testcases in Template space or test cases with other names in User space. – Conrad T. Pino (talk) 08:37, 17 November 2007 (UTC)

[edit] {{Template doc}} clients

The {{Template doc}} links pages have between 1,500 and 2,000 entries. – Conrad T. Pino 07:41, 16 November 2007 (UTC)

Bot or script wanted!

Any volunteers? If you make the time I'll provide the specification. – Conrad T. Pino 07:41, 16 November 2007 (UTC)

Formal bot request opened

A formal bot request with specification was opened for review. – Conrad T. Pino (talk) 03:45, 18 November 2007 (UTC)

[edit] Merge Phase 3: /doc pages

Who is using whom:

Conrad T. Pino (talk) 10:05, 17 November 2007 (UTC)

[edit] Pretty icon eye candy

Check out this icon eye candy I found User:ConradPino/project/Documentation/eye candy and this is how it might look:

[edit] Documentation
This documentation is transcluded from Template talk:Documentation/doc. (edit | history)
This template has a sandbox (edit) and testcases (edit) for editors to experiment.

Sample documentation.

Any objections to making the above sample the {{Documentation}} default? – Conrad T. Pino 04:45, 12 November 2007 (UTC)

Yes; the icons are unnecessary, and using icons simply for aesthetic appeal gives pages an amateurish look. Whenever possible, icons should be avoided on serious pages unless something needs to be strongly emphasized, which isn't the case here. "Documentation" is just a heading, like any other; it just happens to be in a template and faked for technical reasons. —{admin} Pathoschild 08:40:06, 12 November 2007 (UTC)
Everything you've said is true. I'm just easily lead astray by pretty faces! :) Conrad T. Pino 09:30, 12 November 2007 (UTC)
Too bad! :) —{admin} Pathoschild 12:19:45, 12 November 2007 (UTC)
Ohh, another pretty face, I swoon before such persuasion. :) Conrad T. Pino 08:40, 13 November 2007 (UTC)
I agree with Pathoschild, an icon is not needed.—Patrick 11:05, 12 November 2007 (UTC)
Thank you. – Conrad T. Pino 08:40, 13 November 2007 (UTC)

OBJECTION! Examiner is leading the witness by implying the evidence as mere "eye candy". The defense suggests an impartial line of questioning. —Down10 TACO 06:47, 23 November 2007 (UTC)

[edit] Why do you feel the need...

...to inform me, for no apparent reason, that there are no testcases and no sandbox (your formatting) for 99% of Wikipedia's templates that will never need such pages (indeed, I disagree with the idea of such pages in the first place; if you want a sandbox, we already have a sandbox)? It looks stupid – Gurch 10:52, 13 November 2007 (UTC)

I agree there is no universal need. However many templates are {{esoteric}}/{{intricate}} with parser functions or {{editprotected}} or both. I view {{editprotected}} templates as contribution stifling necessities. My biased software engineer's perspective favors wide Wikipedia:Template test cases adoption and Wikipedia:Template documentation as well.
In this case having the extra baggage simplified continued non-admin contribution.
The "...has no sandbox and no testcases for..." contains sandbox testcases edit links supporting rapid creation. Preloading /testcases already occurs, preloading /sandbox is coming. The creating edit links save time and reduce errors. In cases where a /sandbox and /testcases (both) harm then code
{{Documentation|sandbox-testcases=hide}}
I'm open to adding "sandbox=hide" and "testcases=hide" if found useful.
This template's past behavior was display the messge only when both /sandbox and /testcases were present. Today's behvior displays 1 of 4 message variations in the Template or User namespaces. Revisions to this behavior change are best discussed here.
Wikipedia:Template test cases is a how-to guide far from guideline or official policy and worthy continued "I disagree with the idea of such pages in the first place;" discussion preferably on that talk page.
Conrad T. Pino 20:06, 13 November 2007 (UTC)

[edit] Transcluded from /doc message link changes

First line below heading displays in part "...is transcluded from /doc. (view | edit | history)" where "/doc", "view", "edit" and "history" are all hyperlinks. Malyctenar proposed removing "view" link as redundant to "/doc" link. I reverted the edit for other reasons but committed to stating reasons. This change is minor and of little consequence. I shall edit it back shortly. – Conrad T. Pino 11:37, 14 November 2007 (UTC)

Edit done in {{Documentation}} and {{Documentation/sandbox}}. Conrad T. Pino 11:51, 14 November 2007 (UTC)

[edit] 10:26, November 14, 2007 edit reverted

I reverted edit by Malyctenar with summary, "I'm pretty sure people know that clicking on the blue pagename link thingy makes them see it; also no need to test SUBPAGENAME within noinclude of a single template". My revert edit summary was, "have reasons for all; will put on talk or doc within 48 hours; thank you" and I keep that commitment now.

The reverted edits included:

1. Change "...transcluded from .../doc. (view | edit | history)" to remove "view" link.
2. Remove "<noinclude>...{{ #ifeq: {{SUBPAGENAME}} | sandbox | {{Template sandbox notice}} | {{pp-semi-template|small=yes}} }} ... {{ #ifeq: {{FULLPAGENAME}} | Template:Documentation | ... }}</noinclude>".
3. Change #switch: test value layout, from the same line to multiple lines.
4. Remove 1 comment marking begin #if: true location and wording change others.

My comment on each of the above:

1. Change reapplied to reverted version, see Transcluded from /doc message link changes above.
2. The "/sandbox copy / paste solution" to the "{{editprotected}} problem", an evolving solution scheduled for change once consensus for latest {{Template sandbox notice}} becomes clear in time.
3. I honor any general or template specific #switch: layout consenus. I'm ignorant of #switch: layout consenses as I've been corrected for both styles.
4. Comments are idiosyncratic. I'm ignorant here also and seek knowledge of consensus, if any.

A clear statement and discussion of the "{{editprotected}} problem" and "/sandbox copy / paste solution" I leave for later and another place. Thank you all. – Conrad T. Pino 21:01, 15 November 2007 (UTC)

[edit] {{Documentation, template}}'s final fate

{{Documentation, template}} was created to hide behavior and visual differences between the {{Template doc}} and {{Documentation}} families while Merge Phase 1: service templates was in progress.

All behavior variations are implemented in {{Documentation}} controlled by new optional parameters to be documented later.

The visual differences are implemented in {{Documentation, template}} which trancludes {{Documentation}}.

The behavior overrides were in {{Template doc}} and {{Template doc inline}} and both transclude {{Documentation, template}} for their classic look.

Merge Phase 2: client templates is upon us making this the optimum moment to decide {{Documentation, template}}'s final fate.

[edit] Costs avoided

[edit] Costs imposed

  • Client templates are 1 transclude away from {{Documentation}}
  • Adding new-parameter with no default to {{Documentation}} requires editing {{Documentation, template}} from 
    {{ Documentation | heading=...}}
    to 
    {{ Documentation | heading=...| new-parameter={{{new-parameter|}}}}}
    then within {{Documentation}} new-parameter is always defined causing 
    {{{new-parameter|some-value}}}
    to ignore some-value and require 
    {{ #if: {{{new-parameter|}}} | {{{new-parameter}}} | some-value }}
    to maintain expected behavior.
  • Adding new-parameter with a default-value to {{Documentation}} requires editing {{Documentation, template}} from 
    {{ Documentation | heading=...}}
    to 
    {{ Documentation | heading=...| new-parameter={{{new-parameter|default-value}}}}}
    then within {{Documentation}} new-parameter is always defined causing 
    {{{new-parameter|default-value}}}
    to ignore default-value but with no ill effect.
  • Maintaining new-parameter default value coherence requires 
    {{ Documentation | heading=...| new-parameter={{{new-parameter|{{ Documentation/npdv }}}}}}}
    and within {{Documentation}} 
    {{{new-parameter|{{ Documentation/npdv }}}}}
    adding 2 transcludes.
  • See {{Documentation/docname}} and count how many times it's transcluded during one client transclude. The number may startle but IMO it's worthwhile keeping this one.

[edit] Please comment here

As the above may become documentation. – Conrad T. Pino 09:42, 16 November 2007 (UTC)

[edit] Option 1: redirect all

Redirect {{Template doc}} AND {{Documentation, template}} to {{Documentation}}.

Consequence: No default support for classic "(icon) Template documentation" heading.

Documentation
This template has a sandbox (edit) and testcases (edit) for editors to experiment.

Sample documentation.

[edit] Option 2: redirect one

Redirect {{Documentation, template}} to {{Template doc}}.

Revise {{Template doc}} to default to classic "(icon) Template documentation" heading.

Consequence: Costs avoided and Costs imposed move from {{Documentation, template}} to {{Template doc}}.

Documentation
This template has a sandbox (edit) and testcases (edit) for editors to experiment.

Sample documentation.

[edit] Option poll

AzaToth supports "Option 2: redirect one" as evidenced by his {{Template doc}} revert with summary "(Reverted to revision 172237017 by ConradPino; it should still have the same look as the template it's deprecated against. using TW)" of my {{Template doc}} defaults to {{Documentation}} heading edit with summary "(let's find out who care's about classic heading: (icon) Template documentation)". – Conrad T. Pino (talk) 19:20, 18 November 2007 (UTC)

I suggest "Option 1: redirect all" for simplicity, but I also did like that template icon. Is it possible to adjust the display of the heading with a #switch, based on {{SUBJECTSPACE}} = "Template"? Or perhaps adding an optional "showicon" parameter? It's purely aesthetics, and not a vital feature of the template(s), but the icons did add some "friendliness" to the header.
I would also suggest moving the transclusion, sandbox & testcase lines up above the heading rule to as to not mix them in with the main documentation content. That's a separate issue, however. —Down10 TACO 00:38, 19 November 2007 (UTC)
All your icon suggestions are feasable but that's not the direction the Pretty icon eye candy discussion (above) is currently going. I suggest making an argument there and if so the poll becomes 2 and 2, far short of consensus. Please understand supporting "Option 1: redirect all" means no default icon unless an icon favoring "Pretty icon eye candy" consensus emerges. The present alternative is parameter heading which supports text, images or both and will be elaborated upon in the documentation. – Seperate issues warranting prior discussion will benefit if opened soon as seperate threads while the merging notice is drawing attention here. – Conrad T. Pino (talk) 09:33, 19 November 2007 (UTC)
I am in favor of Option 1: redirect all, for uniformity.--Patrick (talk) 01:19, 19 November 2007 (UTC)
I favour option 1 (redirect all) as well; these should be standardized. (I thought that was the whole point of all this ;) ). —{admin} Pathoschild 03:41:14, 19 November 2007 (UTC)
Your thought inspired reviewing the merge proposal discussion. Aesthetics, coding and standards, all there in general, little in specifics and nothing on the heading. Another lost opportunity, the Merge goals proposal by priority went unheeded. Pray tell me Sir, who shall save us from ourselves?!! :) Conrad T. Pino (talk) 09:33, 19 November 2007 (UTC)

[edit] {{Template doc inline}}'s final fate

It's officially retired per {{Template doc inline}} clients - completed above. {{Template doc inline/doc}} states the reasons {{Template doc inline}} can't be redirected. Comments regarding it's final fate are solicited. – Conrad T. Pino (talk) 09:02, 17 November 2007 (UTC)

Sorry, sometimes I'm slow. With no clients the behavior differences are moot. Redirection to discourge using the deprecated version is now an option. – Conrad T. Pino (talk) 09:06, 17 November 2007 (UTC)
After discussion with myself and finding consensus, this template was redirected to {{Documentation, template}}. – Conrad T. Pino (talk) 09:33, 17 November 2007 (UTC)

[edit] Spanish version

The Spanish version listed on the page right now is not useful at all. The Spanish equivalent of this template is called "Plantilla:Template doc". You can see it at es:Plantila:Template doc. Can somebody change this please? — Cuyler91093 - Contributions 09:40, 5 January 2008 (UTC)

[edit] Doc view and edit links

Could we remove the [view] link at the top of the page since it rather jars with the normal [edit] links and we have one bellow the header. And while we're at it rename [edit] when there's no page to [create] since it much more description about what's going on? —Dispenser (talk) 20:42, 17 January 2008 (UTC)

[edit] New parser

As a note, due to the new parser, there is no longer a benefit in placing template documentation on a subpage. Everything in <noinclude> is fully ignored. So the usage of this "system" is now purely cosmetic and easy of use, without technical benefit. A test like this will clearly show you this in the comments. --TheDJ (talk • contribs) 11:30, 30 January 2008 (UTC)

Actually it isn't, using this system still allows you to edit the documentation of a protected template and reduced server load as the pages transcluding the template wont be reparsed. — Dispenser 11:53, 30 January 2008 (UTC)
And it is nice to have a standardized way to do documentation. There are still a lot of lesser used templates where the documentation is on the talk page. --— Gadget850 (Ed) talk - 12:10, 30 January 2008 (UTC)
The ability to edit documentation without editprotected requests is the more important feature of the doc subpages. That reduces the admin workload greatly. On nonprotected templates you are correct that it makes less difference. — Carl (CBM · talk) 14:24, 30 January 2008 (UTC)

[edit] Merger

Hi,

The page Template:Usage of template (backlinks, edit) fulfils the same role as this template, and content forking is discouraged. The aesthetics of {{Usage of template}} appeal to me more than this one; it would be nice if some elements could be incorporated into this template rather than the latter disappearing completely.

Thanks, Verisimilus T 17:40, 10 February 2008 (UTC)

It doesn't look so good with the monobook skin. I am guess your using the modern skin? If so you should go to MediaWiki:Modern.css and ask to add classes that will make {{documentation}} look better. —— Dispenser 19:54, 10 February 2008 (UTC)

[edit] Purge link

I'd like to see a purge link ([{{fullurl:{{ns:10}}:{{PAGENAME}}|action=purge}} purge]) for the template. I often edit templates and find that it's annoying to have to manually purge them. I'd like to suggest adding it as one of the first lines, eg.:

This documentation has been transcluded from ...
This page can be purged

-- SkyLined (talk) local time:07:20, 13 June 2008 (CET), server time: 17:29, 14 April 2008 (UTC)

[edit] Icon eye candy, again?

I just noticed that the eye candy and heading from the older template was added to this template today. That is, this image:

Currently when this template is used on template pages it shows the icon and has the heading "Template documentation". When shown on other pages it shows like it used to, no icon and the heading "Documentation". But this template is more or less only used for template documentation.

Such eye candy has been discussed on several talk pages, the latest round was above at section Pretty icon eye candy. I thought the consensus was that we should not use it. I think it just adds to the overall "information stress" of the design. And I liked the shorter title "Documentation". Simply using "Documentation" as heading also makes the code simpler since then we don't need the name space detection code that was added today.

--David Göthberg (talk) 21:56, 16 April 2008 (UTC)

[edit] Some technical details needed

I am making a wiki on MediaWiki, and would like to implement the Documentation class of templates. So, may I ask, what extensions and common.css classes are required for the proper functioning of these templates? Thanks!

Cheers,

--Samuel di Curtisi di Salvadori 02:59, 21 May 2008 (UTC)