Uploaded image for project: 'Magnolia Personalization'
  1. Magnolia Personalization
  2. MGNLPN-474

Get (stateless) personalized content from the Delivery endpoint

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.8
    • Fix Version/s: 2.1
    • Component/s: None
    • Labels:
    • Release notes required:
      Yes
    • Documentation update required:
      Yes
    • Epic Link:
    • Sprint:
      HL & LD 28, HL & LD 29, HL & LD 30, HL & LD 31
    • Story Points:
      8

      Description

      User story:

      As a SPA developer, I want to get personalized content from the website workspace statelessly, so I can deliver personalized experiences in my SPA.

      Notes:

      Personalization is one of the enterprise features that pure headless CMS do not have, now that we know many customers want to use the pages editor and personalization to populate headless frontends we should provide this.

      Acceptance criteria:

      • The REST call specifys which traits or segments should be used in the resolution (rather then using the info in the user session) - at least by querystring as well as possibly other approaches.
        • This gives more flexibility. Gives better caching possibilities. 
        • Important for middleware / SSR / SSG
      • By default,  a delivery endpoint delivers the same non-personalized format that it delivers now, including all of the variants. (This can still be useful if a developer wants to implement personalization in the frontend itself.)
      • This is only expected to work on any workspaces that are saved to by a "pages app", but there should be no limitations as other app types may eventually also support variant nodes.

        Checklists

        Acceptance criteria

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                jsimak Jaroslav Simak
                Reporter:
                viet.nguyen Viet Nguyen
                Votes:
                4 Vote for this issue
                Watchers:
                8 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Date of First Response:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0d
                    0d
                    Logged:
                    Time Spent - 3d 1h 31m
                    3d 1h 31m