[wp-hackers] Achieving faceted navigation

[Mike Schinkel]

In summary, categories are just a built-in taxonomy so either will work as long as you don't overload one taxonomy when you should be using multiple.

There may be other issues that other's know about but if so I'm unaware of them.

-Mike


On Dec 8, 2010, at 5:58 PM, Haluk Karamete wrote:

>>> If given a choice I'd go with the custom taxonomy because I like to reserve the otherwise too-generic "categories" for "Posts" ($post_type=='post').
> 
> from above, I hear you say, it is OK to not use cats at all, u seem to
> entertain the idea of with cus. taxes all the way...   that's point
> #1.
> 
>>> It seems to me that many people overuse  $taxonomy=='category' and then get into an issues of coupling where their categories for posts are different than their categories for other post types.
> 
> interestingly, we would then be on the other edge of the spectrum that
> is no use of $taxonomy=='category' ! u sure there are no harms going
> this way?
> 
>>> Unless semantically they are using the same categorization for those other post types, such as if all post types really are content items but different types of content and then category can be used as a major site structuring mechanism.
> 
> from above, I am getting confused. for my example, r u saying it is OK
> to use category? if so, doesn't the use of cats conflict with what I
> hear from you on point #1?
> 
>>> Also, I think that most sites with 10 or more top level categories have too many:
> 
> Agree..  that's the result of complicated thinking as opposed to
> simplified thinking. it is odd but very easy to come up with a
> complicated category system, it almost takes no time/brain. but it
> takes a whole lot of experience & intelligence to simplify it.  Enough
> is said here > http://www.greatest-quotations.com/search.asp?quote=simplification
> 
> 
> On Wed, Dec 8, 2010 at 1:46 PM, Mike Schinkel
> <mikeschinkel at newclarity.net> wrote:
>> On Dec 8, 2010, at 4:26 PM, Haluk Karamete wrote:
>>> but what about step 4? are u fine with that?
>>> 
>>> step 4 was this;
>>> ....
>>> What's the alternative to compare with?
>>> ....
>>> Basically, what we are doing here is to completely ignore category
>>> taxonomy from the get go and to the launch and use a custom taxonomy
>>> called topics as a replacement
>>> .....
>>> what i am saying, when going with this approach, from a
>>> coding and/or mind set point of view, are there any benefits at all?
>> 
>> If given a choice I'd go with the custom taxonomy because I like to reserve the otherwise too-generic "categories" for "Posts" ($post_type=='post').
>> 
>> It seems to me that many people overuse  $taxonomy=='category' and then get into an issues of coupling where their categories for posts are different than their categories for other post types.  Unless semantically they are using the same categorization for those other post types, such as if all post types really are content items but different types of content and then category can be used as a major site structuring mechanism.   I'm working on a client project right now where the offshore team used category before I got on the project and they would have been better off having used a custom taxonomy instead.
>> 
>> Also, I think that most sites with 10 or more top level categories have too many:
>> 
>> http://www.useit.com/alertbox/short-term-memory.html
>> 
>> Hope this helps.
>> 
>> -Mike
>> 
>> 
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>> 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers