-
New Feature
-
Resolution: Fixed
-
Major
-
1.8
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
HL & LD 28, HL & LD 29, HL & LD 30, HL & LD 31
-
8
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.
- depends upon
-
MGNLPN-544 Wrappers are not applied to a variant node in RegistryVariantResolver
- Closed
-
MGNLREST-308 Expose JcrDeliveryEndpointDefinition via provider, refactor node wrapping
- Closed
- is cloned by
-
MGNLPN-542 Get (stateful) personalized content from the Delivery endpoint
- Closed
- is depended upon by
-
PAGES-239 Personalization features in SPA Editor
- Closed
-
MGNLFE-95 Update SPA samples to fetch and display personalization content
- Closed
- is related to
-
PAGES-1153 Component Inheritance with Visual SPA Editor
- Closed
- relates to
-
MGNLREST-229 Jersey REST dispatcher impl only registers providers under package info.magnolia.rest
- Closed
-
MGNLPN-66 As an editor I can edit all variants in the pages app
- Closed
-
MGNLPN-545 DOC: Cookie trait with multiple values
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...