[MGNLFE-8] Nested pages in Angular SPA Created: 14/Nov/19  Updated: 27/Apr/20  Resolved: 06/Jan/20

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: Angular Renderer
Affects Version/s: None
Fix Version/s: 1.0.0

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Canh Nguyen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 5d 5h
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLFE-12 DOC: SPA can get its content from a M... Closed
dependency
depends upon MGNLFE-3 Assemble an Angular SPA Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes
Epic Link: SPA Editor
Sprint: SPA Editor 13, SPA Editor 14
Story Points: 5

 Description   

As a SPA developer, I can create a SPA which can load content from different Magnolia pages, depending on the url route, so that I can fulfill a 'website-like' SPA requirement.

It should be possible for an SPA to get its content from a Magnolia page, or its subpages.

For AC see:

https://jira.magnolia-cms.com/browse/MGNLFE-7



 Comments   
Comment by Christopher Zimmermann [ 16/Dec/19 ]

To be explicit: The pages could have different page templates chosen by the author. 

Generated at Mon Feb 12 05:43:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.