Structures look interesting because you can reorder entries manually, generate breadcrumbs and visually see a hierarchy of entries. Besides this, what are the primary consideration when choosing a Structure over a Channel?
Add a comment
|
Ordering and Hierarchy are the main benefits but they create a couple of side benefits such as the ability to
- get the "children" and "parents" of an entry
- get siblings including next and previous siblings
The best part is there no real downside, they have all the features and functions of a regular channel PLUS the structure.
-
1Also worth noting: You can always convert a Channel into a Structure or vice versa, without loosing field-data. – Victor In Sep 7 '14 at 18:37
-
3The only downside of a structure over a channel is that there is overhead associated with keeping track of all that extra information (hierarchy, ordering, etc.). If you don't need the features of a structure, then a channel is much more efficient. – Brad Bell Sep 7 '14 at 19:47
-
2"much more efficient" - how much so? What sort of performance impact are we talking here? – Matt Wilcox Apr 25 '16 at 10:27
