CZ Talk:Templates: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Caesar Schinas
imported>Caesar Schinas
(→‎Documentation: new section)
Line 58: Line 58:
:What code update is needed to make it work again? [[User:Chris Day|Chris Day]] 14:39, 4 May 2009 (UTC)
:What code update is needed to make it work again? [[User:Chris Day|Chris Day]] 14:39, 4 May 2009 (UTC)
::Not sure, I'm afraid. [[User:Caesar Schinas|Caesar Schinas]] 15:31, 4 May 2009 (UTC)
::Not sure, I'm afraid. [[User:Caesar Schinas|Caesar Schinas]] 15:31, 4 May 2009 (UTC)
== Documentation ==
At the moment two completely different methods of adding documentation are mentioned and used.<br />
I propose that ''one'' be chosen and stuck to. I suggest {{Tl|TlDoc}}, which has several advantages due to the documentation being kept on a subpage of the documented template.<br />
A few advantages are :
* The template page is simplified, giving less scope for error when editing complex templates with complex examples.
* The documentation can be maintained without the risk of damaging the template.
* The size of the template page is reduced.
If nobody objects I will change the instructions accordingly.
[[User:Caesar Schinas|Caesar Schinas]] 17:29, 4 May 2009 (UTC)

Revision as of 11:29, 4 May 2009

Todo

Hey Robert, Be sure to mark unused templates for deletion. (Or, feel free to delete them if you have permissions to do so.) --Larry Sanger 12:07, 22 December 2007 (CST)

I'm eventually going to do that after I sort them. --Robert W King 12:37, 22 December 2007 (CST)
I think I'm pretty much done with media templates. Stephen Ewen 01:47, 23 December 2007 (CST)
Also the constabulary templates. Stephen Ewen 01:47, 23 December 2007 (CST)

Nice work here. Once I'm done grading I am going to try and upgrade the subpages template and then delete all the unnecesary stuff. When that is finished I'll write a description to descripe the functions of each tempalte, maybe draw a diagram too.. Chris Day (talk) 02:34, 23 December 2007 (CST)

One suggestion is to organize content-oriented templates by Workgroup. Another idea is to create a new Workgroup called the CZ:Technical Team Workgroup and place all of the design-oriented templates in it, such as for subpages. Stephen Ewen 23:22, 23 December 2007 (CST)
BTW, most of the technical team already functions as a workgroup. ;-) This idea would just formalize it and open it up some, plus be helpful for recruiting. Stephen Ewen 23:24, 23 December 2007 (CST)
More rationale for Technical Team Workgroup
  • Basically, under the Technical Lead, the workgroup would be a place to coordinate development of the software, inclusive of design, upon which CZ runs. Currently this is handled too much off-wiki, so it is not very newcomer-friendly (you pretty much gotta be "in the know" right now).
  • Workgroup would be responsible over Technical help pages, like CZ:Treeview Extension, and other such.
  • Would be a place contributors can go to for template creation and design help, e.g., "I need help making a template that features V, W, X, Y and Z for the Catalog of Gold Medalist Couples Figure Skaters".
  • Would be a "home" for project-wide templates that merely organizes content, e.g., {{Subpages}}.
  • Basically, if it makes the software or some design feature or user-friendliness feature of it better, this it the home for it, e.g., CZ:How to start a new article, and even the CZ:Upload-Wizard.

Stephen Ewen 00:46, 25 December 2007 (CST)

Phases for CZ:Templates

  • Phase 1- Identify templates Completed.
  • Phase 2- Sort/Seperate THE END IS IN VIEW!!!
    • Phase 2a - Sort by function groups
  • Phase 3- Document template functionality
    • 3A- Create "Template Docmentation Template" to be used when creating new templates Done in advance.
    • 3B- Document process behind 3A
  • Phase 4- Create guidelines for new templates
  • Phase 5-

Overlap

There seems to be a certain amount of overlap between "Infoboxes", "Formatting" (subgroup 'data display') and "Navigation" (subgroup 'inside CZ'). Please note that this precedes my recent attempt to add a bit more structure, which did not (in general) move stuff among these three groups a lot.

I would suggest the following rules for which goes where, and if these are acceptable, we can sort things into these three bins on these criteria:

  • 'Infoboxes' should contains all templates which are intended to display data about the current subject. So, e.g. {{Virus taxon}} would be there, not in 'Formatting'.
  • 'Formatting' would be used to hold templates used to display individual instances of generic data-types, in a common format across articles. So things like {{Height}}, {{Utc}} would go there.
  • 'Navigation' would hold templates intended to allow navigation among groups of articles, so things like {{Editor Policy}} and {{Constellations_iau}} would go there.

Sure, this won't be perfect, but it will give us some guidelines as to what goes where. J. Noel Chiappa 17:24, 2 June 2008 (CDT)

Suggestions / Questions here

Will phase one be needed to be reviewed periodically in case someone makes a template under the radar? Is there a bot for scanning or something? I don't know how these things work. Tom Kelly 14:00, 3 June 2008 (CDT)

Comments

Brilliant! This makes so much sense and will be extremely useful. Tom Kelly 13:59, 3 June 2008 (CDT)

--Robert W King 11:44, 9 January 2008 (CST)

Treeview

Treeview extension seems to be messing the page up, showing "<treeview449fed0537e129 id='49fed0537e129'>*Infobox series " etc rather than treeviews. Will it be fixed or should code for it be removed from the page? Caesar Schinas 11:28, 4 May 2009 (UTC)

What code update is needed to make it work again? Chris Day 14:39, 4 May 2009 (UTC)
Not sure, I'm afraid. Caesar Schinas 15:31, 4 May 2009 (UTC)

Documentation

At the moment two completely different methods of adding documentation are mentioned and used.
I propose that one be chosen and stuck to. I suggest {{TlDoc}}, which has several advantages due to the documentation being kept on a subpage of the documented template.
A few advantages are :

  • The template page is simplified, giving less scope for error when editing complex templates with complex examples.
  • The documentation can be maintained without the risk of damaging the template.
  • The size of the template page is reduced.

If nobody objects I will change the instructions accordingly. Caesar Schinas 17:29, 4 May 2009 (UTC)