(as described on Category:Topics).) |
(→Disadvantages: add one, strike one) |
||
Line 6: | Line 6: | ||
==Disadvantages== | ==Disadvantages== | ||
* In web searches (Google etc), a hit with the title "Category:..." doesn't seem so appealing - doesn't look like it will be an interesting page to read. | * In web searches (Google etc), a hit with the title "Category:..." doesn't seem so appealing - doesn't look like it will be an interesting page to read. | ||
* Can't move category pages, so can't preserve history. (Unless there's a workaround, e.g. using [[Special:Export]] and [[Special:Import]]?) | * Where there is a lot of topic information, the listed pages are pushed to the bottom of the page. | ||
<s>* Can't move category pages, so can't preserve history. (Unless there's a workaround, e.g. using [[Special:Export]] and [[Special:Import]]?)</s> ''Problem solved - see [[Appropedia:Moving category pages]].'' | |||
==Alternatives== | ==Alternatives== |
Revision as of 03:46, 10 January 2008
Appropedia currently uses "topic category" pages, much of the time (as described on Category:Topics). Topic information (as opposed to how-tos, projects...) is placed on the category page.
Advantages
- Due to the different content types on Appropedia, a category page is a natural place for topic info, higher in the hierarchy, with pages in the category listed below it.
Disadvantages
- In web searches (Google etc), a hit with the title "Category:..." doesn't seem so appealing - doesn't look like it will be an interesting page to read.
- Where there is a lot of topic information, the listed pages are pushed to the bottom of the page.
* Can't move category pages, so can't preserve history. (Unless there's a workaround, e.g. using Special:Export and Special:Import?) Problem solved - see Appropedia:Moving category pages.
Alternatives
- Use a standard template, including a category tree, at the end of every topic page (which will generally have the same name as the category - but the cat name should perhaps be an argument as well, just in case the page gets moved without the category being move. If there a way of "move-protecting" that might be an alternative, but more restrictive i.e. not preferable).
- Note that this does not show all articles in the category. However, as categories grow and have hundreds of pages, this may not be a bad thing.
- There could be an issue with editors adding to a "See also" section - it could get subjective as to what deserves to be listed there.
- I'm not sure if this is relevant, but thought it was worth exploring. --Chriswaterguy · talk 06:25, 18 December 2007 (PST)
Just looking at the SCA wiki, I noticed they use a template to put links at the top of pages, to link ideas in a hierarchy: e.g. for a Social wellbeing page like this one they use a template at the top which creates these links:
< Ideas Bank, < Social wellbeing
Immediately after that they might list a page or pages which are subordinate in the hierarchy - in this case:
< Ideas Bank, < Social wellbeing, > Community involvement UK