Can we re-use Context Expression Target Groups for custom personalization?
I want to move "personalized" Component containers (Link Lists with metadata) to personalization at a Component Presentation (CP) level. Currently Component Templates render fields in Containers into wrapping "if/else" logic.
Alternative content model:
- Component Presentations replace Containers
- Regions (and Page template logic) organize CPs
- Page metadata replaces Container metadata fields
If using Context Engine Expressions could (should) I suggest re-using the same Application Data namespace as the Target Group extension? By default this is only available as read-only AppData that comes with SDL CMA integration). I see how this would work in Eric Huiza's post.
If not, would it be better to "template" regular (PnP) Target Groups, which are editable? Or should we use a different namespace and extend Target Groups?
Ideally I'd like the functional approach to also work with SDL Experience Manager, SDL Mobile, Contextual Image Delivery, and SDL Smart Target.