[PAGES-218] SPA Editor Backlog Created: 16/Dec/19  Updated: 15/Jan/24

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

Type: Epic Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: VN-Implementation
Remaining Estimate: Not Specified
Time Spent: 1h
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLREST-329 ReferenceResolver should provide acce... Accepted
dependency
depends upon PAGES-190 Assist SPA developers to make SPA's e... Closed
Template:
Epic Name: SPA Editor Backlog
Acceptance criteria:
Empty
Team: DeveloperX

 Description   

Enterprise SPA Editor use-cases, often asked for.

Personalization

  • Allow authors to personalize and target content in the editing UI.
  • Allow them to preview personalization in the Preview App.
  • REST endpoints deliver personalized conent.
  • Allow developers to easily implement personalization in their frontends.
  • Ensure the personalization Preview App works with Visual SPA.

SPA frontend used for editing UI can be hosted on an external server.

  • Convient for developers, no need to deploy SPA to magnolia server at all.
  • Works with external SSR/SSG servers such as Next, Nuxt, Gatsby

Support VUE.js


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