You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

GREYMulti ChannelGREY

Rationale

  • the same content should be delivered differently (different HTML, format, ...)
    • a channel can be: a device, location, medium
  • content can be excluded or made exclusive to one channel

Configuration

  • the channels are configured in site/channels (ordered map)
  • each channel has a resolver

Detection

  • AggregationState has a channel property
  • the aggregation filter sets this value by using a ChannelResolver
    • the STKChannelResolver uses the configured channels
  • Default value is Channel.ALL
  • a channel parameter can be passed

Caching

  • the channel is part of the cache key

Rendering

  • the template variation resolver uses the current channel name

Content Structure

  • content can be marked for specific channels (multiple channels)
  • in the STK we provide a tab used by all the page properties dialogs
  • the channels are stored in the multivalue property channels

Content Delivery

  • urls to /website/* map to the physical workspace website
  • /* maps to the virtual workspace magnolia
  • the virtual session
    • uses the aggregation state to exclude/include content
  • No labels