Where To Store Content?
One thing that comes up a lot for customers when they are planning to use Arc XP products is where and how they should store their content in Arc XP. There are many different ways to store content in Arc XP; however, the technical, performance, and practical implications of those decisions can be hard to understand at first glance. This guide will help you understand who, what, when, where, and why you might choose to store content in one place over another. After the chart, you will find a visual example of how to manage the content and links to the documentation.
Comparison Chart
| Type | Edit in Composer? | Edit in PageBuilder Editor? | Edit for Sections? | Edit Using API? | Description | Recommended Usage |
|---|---|---|---|---|---|---|
| Kicker/Labels | Yes | No | No | Yes | A free-form text field or a pre-defined drop-down list in Composer. | Adding custom fields/pre-defined values to an article for editors and writers |
| Tags | Yes | No | No | Yes | A free-form, text-based input for entering multiple string values on an article in Composer. | Adding custom data to articles when you need a set of free-form values (no pre-defined values) |
| Custom Fields | No | Yes | No | No | A mix of input fields that apply only to a specific component on a single page or template. | Changing the look and feel/layout arrangements on a component or content source selections for a component |
| Plugins | No | Yes | No | No | A component that you can use to control one or more custom fields or additional data passed to a specific component or group of components. | Presets, date pickers, query builders, or setting values on multi-components at the same time |
| Custom Embeds | Yes | Yes | No | Yes | You can create a custom component in Composer that adds custom content inside an article body that you can render and edit with custom fields in PageBuilder Editor. | Third-party oEmbeds or other custom content you want embedded into an article body by editors and writers. |
| Site Service | No | No | Yes | Yes | A mix of input fields that can be applied programmatically throughout all PageBuilder Engine components. This can also be used to refine settings in Composer. | SEO content that changes frequently, section-specific content, sponsored article content |
| Site Properties | No | No | No | No | Hard-coded values for each site for things that rarely change | Facebook/Instagram links, advertiser IDs, advertisement configurations, site title and description, footer text |
| Arc XP Native Specification (ANS) | No | No | No | Yes | The format in which all data in the Arc XP platform is stored and shared across products | Maintaining legacy content in articles that you no longer wish to support in Arc XP |
Kicker/Labels
See How to Use Kickers and Labels.
Tags
See How to Configure Permissions for Managing Tags.
Custom Fields
Plugins
See PageBuilder Editor: Plugins.
Custom Embeds
See Getting Started with the Custom Embed Power Up in Composer.
Site Service
See How to Set Up Site Service for Themes.
Site Properties
See How To Use Site Properties.
ANS