The platform allows you to apply a tree-style structure to your content.
This paradigm aligns most obviously with use in a website environment. It allows you to specify the tree structure that describes your infrastructure architecture.
The simplest usage of the tree structure is assigning a one-to-one mapping of content entries to tree nodes, but the structure module extends beyond that.
You can specify nodes within the tree that have a dynamic set of children beneath it.
An example where dynamic tree structure would be useful
I have a content model for news articles and want them all to appear at /news/:year/:month/:article-slug
I can configure the /news node to be a dynamic route specifying that the child nodes will be made up of news article entries with the specific URL hierarchy.