Update the output URL for Rosey

Migrating to Rosey can cause the CloudCannon Visual Editor to become misconfigured.

CloudCannon uses your output files as the webpage preview in the Visual Editor. Because Rosey moves your output files from their original paths (e.g. /about/⁠) to language-prefixed ones (e.g. /en/about/⁠), the Visual Editor may no longer find them.

How you resolve this depends on where you want Rosey to serve your default language:

• Under a language prefix (e.g. /en/about/⁠), which is Rosey's default. Update your Collection URLs to match, using one of the methods below.
• At the root path (e.g. /about/⁠), by setting default_language_at_root in your rosey.yml. Your default language's output URL doesn't change, so the Visual Editor continues to find those pages without a Collection URL update; only your non-default languages move to prefixed paths. Note that this disables Rosey's redirect page, so visitors landing on / get your default language instead of being sent to their locale.

Update Collection URLs in CloudCannon#

To update the URL in CloudCannon, navigate to the relevant Collection in the Collection Browser and enable Configuration Mode using the switch on the right of the Site Header — purple Edit Configuration buttons will appear. Click Edit Advanced in the top right to open the Edit Advanced data panel, enter the language-prefixed template string in the URL field, and save your Site. Repeat for each Collection.

Update Collection URLs in your Configuration File#

To update the URL in your local development environment, edit the url key for each Collection in cloudcannon.config.yml.

collections_config:
  pages:
    url: /en/[slug]/

Once you've updated the url key for each Collection, the Visual Editor will be able to locate your pages correctly after every build.

In the next step of this guide, we'll point you to further resources for going deeper with Rosey and CloudCannon.