Hmm.. this somehow makes accessing products "easier" if you have few objects.
But I have a few comments: What about sites with 100k+ objects? Your list will become somewhat difficult to manage and use. And what about creating objects? Your users still have to place the new objects somewhere where it makes sense. This means that they have to learn how to use the tree which would have solved the problem in the first place...
Additionally there is the confusion over seeing the same item twice, but in a different manner... which one is "right"?
"What about sites with 100k+ objects?
Your list will become somewhat difficult to manage and use."
Smart filter and sort options would take care of that and if not, one could always opt for the good old "find it by navigating to it" way of access.
"And what about creating objects?
Your users still have to place the new objects somewhere where it makes sense."
Why? Content objects are self contained and doesn't need a placement in the structure to exist in the system. A placement can be attatched later on (by you or someone else).
Smart filtering:
Then you need something else than the screenshots you proposed.. they don't open for filtering, and the default of showing "all" will work only for a small percentage of our shop users. (We have users with 300k+ products) How do you filter out: All ear-rings made of gold for women? This is difficult unless you create options for all this for all your products.
Not placing objects: This means that you can't browse to your objects at all, but rely completely on very well organized data about your products which will have to be filled in for each product.
Personally, I don't think this would work very well for the general user. But you are of course free to prove me wrong. Implementing a module that does what you are talking about shouldn't be too hard.
You must be logged in to post messages in this topic!
