This project is read-only.

Container And Taxonomy

Topics: General
May 17, 2011 at 10:23 PM

Don't you  think Taxonomie's are just another way to implement nested containers?

The same would be possible if you create nested containers for example and allow to choose multiple containers?


So what's the correct purpose/best practice for correct use of containers/taxonomy?


Are the containers just for lists for example products,

and then you would create for example sections in taxonomy (USA, Asia, Europe) and relate the products.

Or create a list and add to the list the containers USA, Asia, Europe and add the products correctly to the sections.


I hope my english is readable ;)

May 17, 2011 at 10:24 PM

Sure, it's one way to look at it.

May 17, 2011 at 10:29 PM
Edited May 17, 2011 at 10:32 PM
bertrandleroy wrote:

Sure, it's one way to look at it.

Do you personally prefer containers or your taxonomy module?

Taxonomy doesn't have a section content type which renders all members like a list does?

Or is this planned?

Ah sure it actually has with the implementation itself a possibility to display all the members.
To add it to the menu you have just to copy and paste the url and voila.

May 17, 2011 at 10:32 PM

Depends what you are trying to do and what your personal preference is. Did you watch my screencast ( Taxonomies do create content types that you can customize.

May 17, 2011 at 10:41 PM

I just saw the end of the video...thanks.

But the concept of orchard for the data itself is,
that it has no structure?

The structure is just given by Taxonomy, Container or Navigation Module.

And if you begin to nest containers you are actually creating a structure for the data.
Which also could be displayed as a sitemap or export in navigation items.

Orchard is really wild :) There are just no rules..

May 17, 2011 at 10:56 PM

Yes, that sounds about right :)