Scroll Sites

Changes Introduced by Our Forge Migration

Scroll Sites is moving from Atlassian Connect to Atlassian Forge to improve security and reliability, and to align with Atlassian's cloud platform. How you use the app stays the same, but you may notice a few differences in the app and in how fast your sites update.

The documented changes are a result of the migration to Atlassian Forge and reflect current platform capabilities and limitations. We continue to work with Atlassian's evolving platform and will make improvements as Atlassian expands Forge's capabilities.

What's Changing

Not much changes for you. Most of the move happens behind the scenes. Here's what you may notice.

Site updates can take longer

Scroll Sites updates your site when content changes in Confluence. On Forge, Atlassian sends these change events to Scroll Sites, and sometimes they arrive with a long delay. So it can take much longer than before for a change to appear on your live site.

Your changes aren't lost. They show up on your site once the event arrives.

When you open a link from Scroll Sites to a page outside Confluence, like your live site, Atlassian first shows a confirmation dialog. This is a Forge security feature, and apps can't turn it off. Click Continue to open the link.

The URL you use to open Scroll Sites in Confluence change. If you bookmarked the app, open it from Confluence again and save the new link.

Your live sites aren't affected. Site URLs, custom domains, and links to your published content stay the same.

Small visual differences

You may notice small visual differences in the app. Forge currently limits how apps control their layout inside Confluence, so we can't always match the previous look exactly. Only the look changes. Everything works the same way.


Do I Need to Do Anything?

No, the move happens automatically.

You might want to save the new link to Scroll Sites if you had the app bookmarked

Last updated: