Micro Experiences Editor/Curator Guide

How Does MX Work?

Micro Experiences (MX) allow your organization to create multiple, independent digital experiences using separate PageBuilder instances. Each MX instance can be tailored to specific sites, sections of sites, or even individual campaigns can be used temporarily or permanently. This flexibility helps your team better manage and curate content by isolating different parts of your digital presence into distinct, manageable units.

For example, you might have a “Sports MX” for all sports-related content and an “Election MX” for content related to election coverage. Each of these MX instances can have its own set of features, pages, and templates, making it easier to focus on the specific needs of each section.

How Does MX Impact Your Workflow?

We’ve designed Micro Experiences (MX) to minimize any impact on your editorial workflows. While you’ll have access to multiple instances within PageBuilder, the way you curate and manage content remains largely unchanged. This ensures that your day-to-day operations continue smoothly, with minimal disruption.

Changes You Can Expect in Your PageBuilder Experience

If you’re assigned to work on multiple MX instances, here’s what you might notice:

Multiple PageBuilder Tiles

In your Arc Admin panel, you may see several PageBuilder tiles, each representing a different MX instance. These tiles are clearly labeled (e.g., PB-Sports, PB-Election) to help you quickly identify which instance to work in.

Note

New Micro Experiences added later will be prefixed with PB-. Your existing experience (referred as “default” experience) name will not be changed from “PageBuilder Editor” by default, but you can rename it to anything you want.

More focused list of curation blocks in your Editor Curate workspace

Your team will design and split your digital experiences into more tailored Micro Experiences. This means that you will see a more focused list of curation blocks in your Editor Curate workspace.

Updated PageBuilder URLs

Micro Experiences changes the existing PageBuilder URL format to a new format that includes MX slug or ID in the URLs.

OLD URL FORMAT	NEW URL FORMAT
/pagebuilder/pages	/pagebuilder/experiences/{MX-slug}/pages
/pagebuilder/templates	/pagebuilder/experiences/{MX-slug}/templates
/pagebuilder/tools/resolvers	/pagebuilder/experiences/{MX-slug}/tools/resolvers
/pagebuilder/tools/debugger	/pagebuilder/experiences/{MX-slug}/tools/debugger
/deployments/fusion	/deployments/fusion?mxId={MX-id}
/themesettings	/themesettings?mxId={MX-id}

Access Permissions

Your access rights remain consistent across MX instances. If you have editing permissions in one MX, you’ll have similar permissions in other MX instances, ensuring a smooth and consistent experience.