Difference between revisions of "Talk:Table of contents"

From ArchWiki
Jump to: navigation, search
(Add Table of Contents link into left navigation panel: re)
(Add Table of Contents link into left navigation panel)
Line 74: Line 74:
  
 
:Actually this seems a pretty cool idea to me! It's as easy as editing [[MediaWiki:Sidebar]]: what about putting the link in second place, right below the link to [[Main Page]]? -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 09:50, 23 June 2012 (UTC)
 
:Actually this seems a pretty cool idea to me! It's as easy as editing [[MediaWiki:Sidebar]]: what about putting the link in second place, right below the link to [[Main Page]]? -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 09:50, 23 June 2012 (UTC)
 +
 +
:: That is my prefered location too. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 14:02, 24 June 2012 (UTC)

Revision as of 14:02, 24 June 2012

ToC restructuring

I propose the following (major) changes to the ArchWiki category tree:

Removal of Category:Pages sorted by type (English)
Currently we distinguish between four types of articles: FAQs, General, Guidelines, and HOWTOs. I believe that the majority of FAQ articles should be merged into the main FAQ; the general category is not helpful in any way; almost all articles under guidelines deal with package management (see Category:Package development instead); and every article is a HOWTO in the sense that it explains how to install/configure/etc. something (further, ArchWiki is moving away from the HOWTO style of writing (step 1, step 2, step 3...))
Flattening of the tree
The Category:System administration and Category:Desktop user's guide (English) categories are unnecessary and confusing. Consider Desktop user's guide -> Category:Utilities (English) (utilities not used for system administration?) and System administration -> Software -> Category:Display managers (display managers not used by desktop users?) Similarly, the Category:Hardware (English) and Category:Software categories can easily be eliminated. Categories that relate specifically to hardware can be renamed (e.g. Hardware -> Category:Graphics can become Graphics hardware).
i18n standardization
Non-English categories should follow the naming scheme Title in English (Language). See Help:i18n for details. Template:i18n should be included on all category pages. Furthermore, all category titles should be appropriately capitalized (Like a Title).

Are there any objections? I will prepare an outline of my imagined category tree shortly.

-- pointone 20:20, 10 May 2011 (EDT)

+1 for all. :-) Unfortunately I don't have much time and will have even less. -- Karol 20:33, 10 May 2011 (EDT)
I'm in favour of points 1 and 3 but basically against the systematic flattening of the tree, but it's just a matter of taste, and we are 2 vs 1 here, so I'll just shut up now :D -- Kynikos 09:21, 11 May 2011 (EDT)
Phew! That was one mess of work! No longer do we distinguish between article topics and types. I will propose changes to the tree regarding (2) in detail before committing to anything. -- pointone 17:08, 10 June 2011 (EDT)
Very good job pointone, it has surely been worth the effort! -- Kynikos 10:24, 11 June 2011 (EDT)
How about using native category names with redirects to i18n named categories on category pages? --AlexanderR (talk)
Actually I was thinking to propose the liberalization of titles for all pages (not only categories), but only after implementing Help_talk:I18n#.22Dummy.22_interlanguage_links_and_deprecation_of_Template:i18n. Please, until then let's stick with the current standard: we'll discuss this thing after that, there's already lots of stuff going on in that talk page :) -- Kynikos (talk) 20:30, 8 June 2012 (UTC)
Done. Thank you for pointing to Help_talk:I18n. Good luck with i18n work! --AlexanderR (talk)
i18n standardization split to its own topic. Close fininshed ToC restructuring part. -- Fengchao (talk) 04:08, 21 June 2012 (UTC)

i18n standardization

Non-English categories should follow the naming scheme Title in English (Language). See Help:i18n for details. Template:i18n should be included on all category pages. Furthermore, all category titles should be appropriately capitalized (Like a Title).

Are there any objections? I will prepare an outline of my imagined category tree shortly.

-- pointone 20:20, 10 May 2011 (EDT)

How about using native category names with redirects to i18n named categories on category pages? --AlexanderR (talk)
Actually I was thinking to propose the liberalization of titles for all pages (not only categories), but only after implementing Help_talk:I18n#.22Dummy.22_interlanguage_links_and_deprecation_of_Template:i18n. Please, until then let's stick with the current standard: we'll discuss this thing after that, there's already lots of stuff going on in that talk page :) -- Kynikos (talk) 20:30, 8 June 2012 (UTC)
Done. Thank you for pointing to Help_talk:I18n. Good luck with i18n work! --AlexanderR (talk)

Capitalization

[split from a previous discussion, now closed. -- Kynikos 16:48, 23 April 2012 (EDT)]

As I began sorting and standardizing the Spanish categories, I realized that many English categories have improper capitalization. These issues could probably more efficiently be dealt with simultaneously. --Emiralle 21:46, 10 September 2011 (EDT)

I can easily solve this one with my bot, although it's not urgent. -- Kynikos 16:48, 23 April 2012 (EDT)
Maybe not so easily, since I'd need a dictionary of words that should be left lower-case. -- Kynikos (talk) 20:51, 15 June 2012 (UTC)

"also in" links

Do you like seeing the "also in" links next to categories that have more than one parent? -- Kynikos 06:56, 1 March 2012 (EST)

Related discussion: Help talk:Style#Category pages - tree or otherwise? If we return to a tree structure, "also in" links would not exist. -- pointone 19:18, 13 March 2012 (EDT)
But maybe in that case displaying them would be even more important, as a means of detecting violations to the rule. -- Kynikos 08:27, 14 March 2012 (EDT)
Quite right. My vote is conditional upon the tree decision, then. If a tree structure is enforced, display it to detect violations. If we allow multiple categories, however, hide it to avoid clutter. -- pointone 13:04, 15 March 2012 (EDT)
Ah kk your position is perfectly clear. However I wouldn't consider the ToC only as a tool for end-users, I think it's also very useful for maintainers, in fact being able to spot multi-parent categories (be them allowed or not) gives a clearer idea of how the articles are structured.
Some ideas to reduce/avoid clutter:
(I'll probably implement this solution for the next update)
(for this option, place the mouse on the asterisk; we can use another symbol, like + ^ #  !)
-- Kynikos 07:06, 16 March 2012 (EDT)
The first idea is implemented currently with <small>. -- Kynikos 11:56, 18 March 2012 (EDT)

Poll

Display it
[vote with : ~~~~]
thestinger 00:48, 2 March 2012 (EST)
Skydiver 00:51, 2 March 2012 (EST)
Kynikos 05:09, 2 March 2012 (EST)
Don't display it
[vote with : ~~~~]
Fengchao 20:09, 1 March 2012 (EST)
pointone 19:18, 13 March 2012 (EDT)

"also in" translations

Currently only Spanish, French, Italian and Portuguese have a translated "also in" string for categories with more than one parent, all the others are using the English wording. Please request new translations here. -- Kynikos 05:59, 12 March 2012 (EDT)

Add Table of Contents link into left navigation panel

Sometime I want to visit this Table of Contents page. Right now I have to click to Main Page and then Click the link on the top. Why not add a link into navigation part on left page. It will be more visiable their. -- Fengchao (talk) 04:14, 21 June 2012 (UTC)

Actually this seems a pretty cool idea to me! It's as easy as editing MediaWiki:Sidebar: what about putting the link in second place, right below the link to Main Page? -- Kynikos (talk) 09:50, 23 June 2012 (UTC)
That is my prefered location too. -- Fengchao (talk) 14:02, 24 June 2012 (UTC)