-
Type:
Story
-
Status: Closed
-
Priority:
Major
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: Master
-
Component/s: Content Page Experience Personalization
-
Epic/Theme:
-
Epic Link:
-
Sprint:SP | Sprint 9 | Mar6 - Mar15, SP | Sprint 10 | Mar18 - Mar29, SP | Sprint 11 | Apr1 - Apr12
Design Deliverable (Review Workflow and Component page on Figma):
- Mockups: https://www.figma.com/file/EC1hz5JRPDvlaoXnT4ejUQLc/lps-90663-view-changes-in-pages?node-id=0%3A1
Acceptance criteria
Customize content per experience
- GIVEN 2 segments
- WHEN adding one content page AND one component for the default experience AND adding a new experience AND editing component content for new experiences
- THEN component content varies across experiences
Customize content per experience (publishing)
- GIVEN 2 segments
- WHEN adding one content page AND one component for default experience AND adding a new experience AND editing component content for new experiences AND publishing the changes
- THEN component content varies across experiences
Customize content per experience (discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one component for default experience AND adding a new experience AND editing component content for new experiences AND discarding changes
- THEN experiences (default and new one) have no content
Customize content per experience (publishing and discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one component for default experience AND adding a new experience AND editing component content for new experiences AND publishing changes AND re-editing content page AND discarding changes
- THEN the experiences have the same content when they were published
Add new component in non default experience
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND adding a new fragment to non default experience
- THEN new fragment is shown only in non default experience
Add new fragment in non/default experience (publishing)
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND adding a new fragment to non default experience AND publishing changes
- THEN new fragment is shown only in non default experience
Add new fragment in non/default experience (discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND adding a new fragment to non default experience AND discarding changes
- THEN experiences (default and new one) have no content
Add new fragment in non/default experience (publishing and discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND adding a new fragment to non default experience AND publishing changes AND re-editing content page AND discarding changes
- THEN the experiences have the same content when they were published
Remove component from an experience (likewise publishing / discarding / publishing and discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND in non-def experience, remove common fragment with default experience
- THEN fragment is shown in default experience, but not in non-default one
Remove section from an experience (likewise publishing / discarding / publishing and discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND in non-def experience, remove a section with fragments common with def experience
- THEN section is shown in def experience, but not in non-def
Change background color in non-def experience (likewise publishing / discarding / publishing and discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND editing the section background color on the non-def experience
- THEN Change is only applied to non-def experience
Change background image in non-def experience (likewise publishing / discarding / publishing and discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND editing the section background image on the non-def experience
- THEN Change is only applied to non-def experience
Change section spacing in non-def experience (likewise publishing / discarding / publishing and discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND editing the section spacing on the non-def experience
- THEN Change is only applied to non-def experience
Add new sections and fragments to non-def experiences (likewise publishing / discarding / publishing and discarding)
- GIVEN 2 segments
- WHEN adding one content page AND one fragment for the default experience AND adding a new experience AND Adding new sections
- THEN changes affect only current experience
- demands
-
LPS-95111 JS Error when discarding content page changes with more than one experience
- Closed
- depends on
-
LPS-86141 As a Page Author I can display a "Content Set" with items of a single type defining the presentation visually
-
- Closed
-
- fixes
-
LPS-86256 As as Inbound Marketer, I can add or remove different sections of a page for different audiences
-
- Closed
-
- is demanded by
-
LPS-87171 As an Inbound Marketer, I can specify different background images for different audiences
-
- Closed
-
-
LPS-92939 As a Marketer, I want to be able to propagate layout changes from the default experience to other experiences
-
- Closed
-
- is related to
-
LPS-93726 As an Inbound Marketer, I can preview the content of the content set personalized variations
-
- Closed
-
- links to