Storage structure
How are page variants stored?
How should the difference to the "master page" be stored? As delta or as a ful copy?
How are segment-associations stored?
Activation
How are page variant handled during when activating contents/pages? tbd
UI / UX
Needed UX components
- Tag selectors
- In a separate Tab with ordinary dialog components (see comment of Andreas below)
- Semantic layer in dialog (UX/UI Improvement)
- In a separate Tab with ordinary dialog components (see comment of Andreas below)
- Add audience (segment) / Choose audience (segment)
- Create variant (adding an audience will implicitly create a variant of a page)
- Audience/segment selector for
- Pages
- above green edit bar in Preview & Edit mode
- to edit different page variants and their contents
- to preview the different page variants (Selection will render "personalized" page)
- in the dialog of page properties
- to edit and compare values of page properties relevant for different segments
- above green edit bar in Preview & Edit mode
- Components (for dynamic components)
- What's the equivalent on component level? Seems to work differently in here (i.e. no preview, just visible in edit-mode)
- Pages
Rendering
What we need:
- Dynamic components
- components to be added to a page capable of displaying content targeted to different segments/audiences.
Caching
What are we caching and how?
Open Questions
Arch questions
- How are facets stored and identified (JCR mixin)?
- How do facets relate to tags/categories?
- How are associations to facets stored in contents? (custom mgnl:facet property)
- By identifier
- By name
- How/what are segments (reminder: a segment is actually a facet that may be just a combination of other facets) stored/managed in the system?
- How many segments can a page variant be associated to? Just ONE
or MANY? - How are page variants stored?
- As subnode on the page node itself with a mixin.
- Will we store a delta between master and variant page or will we store a full copy?
- We need this for components/contents too
- Syncing changes from master to variant: Meeting with Jan Schulte
Multi-treevs. single-tree personalization (similar to i18n), do we support multi-tree? >> NO
UI questions
- Tag selection clarification:
- Tags (here: facets?) are selected and added in a separate dialog tab (no semantic layer for now)
- Segment management app:
- Could be content app that stores in JCR
- Segment selector:
- Creating a variant is not a separate action
- Simplification
- Adding an audience will automatically create a variant
- Audience selector
- In Preview mode it is sticky (it stays when switching to other page, even though it might not have a page variant)
- In Edit mode it might disappear because on other pages there might not be a page variant
- Dynamic Components have to be previewed in page preview modex
- Marker (or somehow interface boolean isMarker()) interface to show special icon / highlight dynamicness
- Page Properties Dialog won't have a switcher
- Props of a variant are edited in edit mode of a page by switching to the audience and editing the page props. as before
- Audience & Previev
- If an audience(s) is(are) defined, we have (all of) them in the Preview
Others
- Wouldn't be handy for authors to be able to define new tags/categories right when they're tagging their content, instead of opening a new app separately, create the new category/tag and then back to the other app to use it?
Overview
Content Tools