How To Support Composer Previews With Multiple MX

How Does Composer Previews Gets Impacted by MX?

From the content authoring tools, only integration point you need to consider the impact of multiple MX is; Composer Preview functionality. You most likely already set up your preview resolver, templates that renders any story for your websites in your current bundle, and PageBuilder.

Example composer preview URI (configured in in Composer Settings):

https://orgname.arcpublishing.com/pf/preview/{_id}/?_website={canonical_website}

This configuration should not change in Composer Settings. But if a content’s canonical URL now is being rendered by a non-default MX, your preview page should be redirected to an MX-specific preview path.

For example, you started splitting your sports section, including your sport articles that gets rendered by a new Sports MX from now on. The Composer Preview URL setting (above) that will render the content using default MX. This will most likely work ok, but it will continue previewing your content in your default bundle’s rendered page. If your Sports MX bundle is rendering your sports articles differently (example: different features, or different styles), you will want to allow your Editorial teams to preview sports articles using Sports MX bundle.

Implementation of Cross-MX Composer Previews

In order to do this, you need to update your global content source that is configured with your preview URLs, to detect a story’s canonical URL and match same pattern that your Sports MX is configured with, and when you catch a sport story that should be rendered by Sports MX, you should issue a redirect from this content source that resides in your default MX preview, to go to a new preview URL format that will be caught with Sports MX router. Example: /sports/preview/.... The resolver configuration, template, global content source for your preview in Sports MX will be almost identical to your default MX.

You will probably need to replicate same site + path prefix pattern you are using in MX Service for each MX. For example, we mentioned Sports MX, which might be configured as simple as all sites, URLs starting with /sports/ path prefix. If that’s the case, the preview URL pattern example we gave above for Sports MX will be /sports/preview/... which should automatically be handled with MX router.

Once the redirection is done from default MX, to the target MX, the preview should render as expected using the target MX bundle contents and styling (if different). This redirect should be completely silent, and invisible to your Editorial user when they click Preview on a story, that they would get redirected to correct MX’s and see preview of the article they are editing.