[PAGES-239] Personalization features in SPA Editor Created: 10/Feb/20  Updated: 17/Dec/21  Resolved: 07/May/21

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Canh Nguyen
Resolution: Done Votes: 1
Labels: VN-Analysis
Remaining Estimate: Not Specified
Time Spent: 6.5h
Original Estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue Links:
Problem/Incident
Relates
relates to MGNLFE-95 Update SPA samples to fetch and displ... Closed
dependency
depends upon MGNLPN-474 Get (stateless) personalized content ... 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)
Date of First Response:
Epic Link: Headless p13n
Sprint: HL & LD 28
Story Points: 5

 Description   

As a marketer I want to control the personalization of a SPA in the page editor with the normal Magnolia personalization UI so that my SPA provides a personalized experience for its users.

Acceptance Criteria:

  • Make sure that page-editor controls and actionbar shows personalization options
  • Author can create multiple variants of a component

Investigate (dependent on MGNLPN-474):

  • Each component can be different
  • Author can target each variant in the normal way
  • SPA shows only the variant that matches the current user in the page editor
  • SPA works with personalized REST endpoint response


 Comments   
Comment by Canh Nguyen [ 06/May/21 ]

As you can see the image below shows that page-editor controls and actionbar shows personalization options, and we can create multiple variants:

I'm going to close this ticket and create a new ticket to update frontend-helpers' samples that use the new REST personalization endpoint to fetch the content. Because fontend-helpers doesn't make REST calls, and the displayed data depends on REST data and 3rd party developers' components.

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