What I am proposing is to modify the two generator templates, to produce
the following results. All documentation is shown as it should appear on
the relevant page, without any of the wiki markup (doubtless
fantastically complex) needed to produce it. (I may need to use a lot of
"&something;" HTML character entities.)
* New documentation on the Template:Usage page: "Place the generated
template, {{your-license}}, on the proper Category page, using the
'CatPage' parameter: {{your-license|CatPage}}."
Given a hypothetical {{PDL2}} generated template, with a category "PDL
Version 2 License" and a link to "PDL2.html":
* New documentation on the Template:PDL2 page is particularized: "Place
this template on the [[Category:PDL Version 2 License]] Category page,
using the "CatPage" parameter: {{PDL2|CatPage}} to produce the proper
documentation and to avoid including the category in itself." The double
brackets [[ ]] here indicate a real internal wiki-link, probably red to
start with. The braces {{ }} are escaped.
When {{PDL2|CatPage}} is placed on the Category page, the following will
happen:
* The Category page will /not/ be included in itself.
* In addition to the standard link ("Documentation on this page ..."), a
new line of documentation will be added: "Pages are placed in this
category by the {{PDL2}} template."
* The {{PDL2}} template will recognize the "|CatPage" parameter
specification and do the above.
Testing: Normally I would just test in preview mode, or in the Sandbox,
but this involves three new templates, and a new Category page, and
possibly a new "ordinary" page as well . . . If you approve of the
concept, I hope you don't mind having a few pages marked, {{delete}}
afterward. The template language is hugely complex and powerful; we have
barely scratched the surface of it. I am certain to make some mistakes
in the process. Playing on my "own" pages should avoid disrupting
anything on the wiki.
Phew :-) (sorry for the late reply... I've been trying to get my head
around this idea)
On the testing side, sure, go ahead and make whatever pages you need for
testing. It's easy to remove test pages once the test is over, or move
test pages to live pages if the test is successful.
C.
--
Clayton Cornell ccorn...@openoffice.org
OpenOffice.org Documentation Project co-lead
StarOffice - Sun Microsystems, Inc. - Hamburg, Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@documentation.openoffice.org
For additional commands, e-mail: dev-h...@documentation.openoffice.org
