Multi-channel Content Gadget

In this module, you will learn about the Multi-Channel Content Gadget in Optimizely CMS. This gadget is designed for organizations working with headless or hybrid CMS setups, enabling the creation and management of headless content that can be shared across websites, apps, and other digital channels.

After completing this module, you should be able to:

• Explain the purpose of the Multi-Channel Content Gadget.
• Create and organize content within the gadget.
• Recognize the difference between headless-only and coupled CMS use cases.
• Decide when this gadget should or should not be used.

Purpose of the Gadget

The Multi-Channel Content Gadget is used to create and manage headless content within the CMS. Unlike the Navigation gadget, which structures traditional website pages, this gadget focuses solely on reusable content elements such as blocks or forms. These elements can then be delivered to multiple channels through integrations like Optimizely Graph.

How It Works

• In headless-only mode, the gadget usually replaces the Navigation gadget. All content is created in this workspace and distributed to downstream systems.
• Content can be organized into folders and subfolders for better management.
• You can create new blocks, forms, or containers directly from the gadget and make them available for use across channels.

Use Cases

The Multi-Channel Content Gadget is most relevant in the following scenarios:

• Headless-only approach: When the CMS is not rendering pages directly but only serving content to external platforms.
• Hybrid setup: When part of the website uses traditional navigation while some content needs to be shared with apps, microsites, or third-party systems.
• Selective use: Even in a fully coupled CMS environment, teams may use this gadget for content intended for reuse in other channels.

When to Ignore the Gadget

If your organization operates purely in a traditional CMS-to-website workflow, this gadget may not be necessary. You can safely ignore it unless there’s a requirement for multi-channel content distribution.

To see the Multi-Channel Content Gadget in action, check out this demo: