Template talk:Subpage list

Don't you think we should be using numerical IDs? Surely we'll have more than 26 subpage types in the long run. I anticipate hundreds... --Larry Sanger 14:39, 19 July 2007 (CDT)

In that case number would be good. i was using letter for now to get the A, AA, and AAA. However, 1A, 1B and 1C works equally well. Chris Day (talk) 16:25, 19 July 2007 (CDT)

Hundreds? Wow. Can you elaborate?  —Stephen Ewen (Talk) 18:37, 19 July 2007 (CDT)

Think of specializations and the special types of information they deal with. Music: collections of abcs or other files. Anthropology and archaeology: 3D models of the human body and of archaeological sites. Geography and history: maps (distinguished from images).

But I think what I had in mind, which made me say "hundreds," were special applications of existing subpage types. So, for example, for articles about countries and demographic topics we might have Statistics pages that are essentially types (applications) of Table/Catalog pages. For articles about artists, our galleries might be renamed in some distinctive way (but "gallery" is perfect in this case...).

On the other hand, there might be value in keeping the list of types of subpages to something only a little more expanded than what we have now.

I would like to have some advice on this, actually, from an LIS person. --Larry Sanger 00:08, 29 July 2007 (CDT)

Default button option

Thinking a bit more about the default vs optional subpages, there seem to be two formats to consider.  

1. Subpage buttons always appear in the same relative order (although some may be missing if optional).  Conseqently if there are two default subpages A page and D page, all CZ pages using the template will have buttons for A and D.  But if B and C pages are present for a particular article then the buttons will appear in the order A,B,C and D.
2. Subpages buttons will cluster, default one first, followed by tthe optional buttons. Conseqently if there are two defaults A page and D page, all CZ pages using the template will have buttons for A and D.  But if B and C pages are present for a particular article then the buttons will appear in the order A, D, B and C.

The current subpages template is coded to give the first solution. One advantage is that only values have to be attributed to the designated Default pages others will be optional automatically.  

For the second option to work all subpages in the "subages list" template must be given an attribute, either "Default" or "Optional". Larry, from what you wrote in the forum it sounds like you would prefer the second option.

In the forum it was also mentioned that it would be good for the optional buttons to sort alphabetically. The current code is not set up to do that.  And i'm not sure if it is even possible (my ignorance at work here). This could be solved by doing it manually in this subpages list template but would lead to a logistical nightmare when adding new pages.  A possible solution is for someone to write a simple script to regenrate the list each time a new button is added. Chris Day (talk) 00:39, 20 July 2007 (CDT)

I just set up the code in the {{Subpages}} template to function in the way described above in option2. Parameter #C must now be in one of three states.

• Left blank: will be ignored as a button, even by the {{unused subpages}} template.
• Set as "Default": will be added to the top of the subpages template even if the subpage does not exist. Will also be included in the unused subpages template.
• Set as "Optional": will only be added to the subpages template if the subpage exists. These buttons will always be after the default buttons.

I have set up this subpage list to demonstrate the functionality of this template. Timelines is now a default button* but is listed near the bottom. There are also two "free buttons" that have no text in their #C parameter, thus, they are not included in the unused subpage list. Chris Day (talk) 12:18, 20 July 2007 (CDT)

* I just set timeline back to an optional status. Chris Day (talk) 10:23, 21 July 2007 (CDT)

Lists and catalogs?

We might want another subpage type for lists and catalogs. For example, on a genus page, there could be a list of species, the philosophy page has a Catalog of famous philosophers, etc. I think these are different from related articles. I am working off and on on a "Catalog of commercial wood species" which should be linked from the Wood page. Luigi Zanasi 13:38, 28 July 2007 (CDT)

At present this comes under tables but we could change the names to be more descriptive of the table content. Chris Day (talk) 13:51, 28 July 2007 (CDT)

Yes, I'm thinking that "Catalog" was more apt than "Table" after all. "Table" just doesn't convey any clear notions, it just says what the format is. Well, a timeline might be in a tabular format. Hmm. I think I've convinced myself again..."Catalog" is a little better. Thoughts? --Larry Sanger 13:56, 28 July 2007 (CDT)

Agree. Chris Day (talk) 14:43, 28 July 2007 (CDT)

I don't think catalog is that obvious to someone who is not familiar with Citizewndium terminology. How about "Tables, catalogues & lists"? Luigi Zanasi 23:31, 28 July 2007 (CDT)

It's a bit long, too long for one of the buttons in the navigation box, for example. Catalogs and lists might be about as long as you can go. Chris Day (talk) 23:41, 28 July 2007 (CDT)

Noinclude text from template body

Pasted here for storage until figure out bug. Chris Day (talk) 14:41, 30 July 2007 (CDT)

The {{subpages}} template is designed to be used within article clusters and their related pages.
It will not function on Template talk pages.
The page contains all the variable parameters for the subpage navigation template.

Usage

Currently, this template has a master list button and their variables, including the actual subpage name that is targeted by the button and the text seen on the button; these two are not always the same. Any button can also be set to either a default or an optional status. Default buttons will always appear in the navigation box even if there is that subpage does not exist in the article cluster.

In the future, it will be possible to control the colours and styles of the button/tab's.

Master list of buttons

This master list of buttons is used to define the buttons on the {{subpages4}} navigation box template.

• #A= name of subpage
• #B= name seen on the button
• #C = Indicates if the button represents a "Default" or "Optional" subpage, or a non functional button. Any subpage labelled "Default" will be placed at the top of the {{subpages4}} template whether the subpage exists or not (i.e. could be a red link button). Those labelled as "Optional" will only appear in the {{subpages}} template if they exist (i.e. will only show blue links). If the #C parameter is left blank it will be ignored as a button, even by the {{unused subpages}} template.

Buttons labelled "Button available" can be utlised for new subpages names after they have been approved by either the Editor-in-Chief or the Editorial Council. For a description of the full process see the following guide: How to add subpage types

1A = Related Articles 1B = Related Articles 1C = 2A = Bibliography 2B = Bibliography 2C = 3A = External Links 3B = External Links 3C = 4A = Works 4B = Works 4C = 5A = Discography 5B = Discography 5C =

6A = Filmography 6B = Filmography 6C = 7A = Catalogs 7B = Catalogs 7C = 8A = Timelines 8B = Timelines 8C = 9A = Gallery 9B = Gallery 9C = 10A = Audio 10B = Audio 10C =

11A = Video 11B = Video 11C = 12A = Code 12B = Code 12C = 13A = Tutorials 13B = Tutorials 13C = 14A = Student Level 14B = Student Level 14C = 15A = Signed Articles 15B = Signed Articles 15C =

16A = Function 16B = Function 16C = 17A = Addendum 17B = Addendum 17C = 18A = Debate Guide 18B = Debate Guide 18C = 19A = Advanced 19B = Advanced 19C = 20A = Recipes 20B = Recipes 20C =

Button colours

Tab based

To be continued, currently an experimental idea.

• Button ON

Body

body on A =

body on NA =

Lines

top on =

left on =

right on =

bottom on = (same as body on with A and NA variable)

• Button OFF

Body

body off =

Lines

top off =

left off =

right off =

bottom off =

• Table

Body

body A = (same as body on for Button ON)

body NA = (same as body on for Button ON)

Lines

top =

left =

right =

bottom =