As a Magnolia client developer, I want to have a possibility to get via API a hierarchical structure of Pages  so I can work with the content without having to "build the tree" in client code.

Context & Problems (from: https://wiki.magnolia-cms.com/pages/viewpage.action?spaceKey=DEVINT&title=Norsu+Content+Delivery+concerns)

Getting a tree of content.

The API has changed in a major way from JCR, there is no way to retrieve a tree/heirarchy of content (with multiple page nodes).

One would assume that since the content is treated as hierarchical in the UI apps, it should be also returned in the content delivery endpoint as such.

Norsu returns a flat list, but each item has a path property, so the front end can reassemble the tree structure if needed. It's just extra work.

Acceptance Criteria: 

The API should allow for retrieval of hierarchical structure of Pages and Sitemaps.

The hierarchical structure should accurately represent the page structure and ordering, including parent-child relationships.

The API should be secure, with appropriate access controls and authentication.

To Determine

When to return tree.

Format for the tree -see:

https://wiki.magnolia-cms.com/display/DEVINT/Proposal+for+Delivery+Heirarcy