[PAGES-1138] CLONE - Support Norsu Content Store to generate Hierarchical Structure responses Created: 21/Apr/23  Updated: 02/May/23  Resolved: 02/May/23

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: New Feature Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Canh Nguyen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLREST-678 Support Norsu Content Store to genera... Closed
Template:
Acceptance criteria:
Empty
Documentation update required:
Yes
Epic Link: SaaS Migration - DevX
Sprint: DevX 36
Story Points: 0
Team: DeveloperX
Work Started:
Approved:
Yes

 Description   

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

 


Generated at Mon Feb 12 06:25:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.