This article will show you how to review and fine-tune sites that were automatically migrated from Scroll Viewport to Scroll Sites.
Find Your Auto-Upgraded Sites
The transition process from Viewport to Scroll Sites migrates and upgrades all existing Viewport sites to the new app.
Scroll Sites is its own, unique, app in Confluence. To open Scroll Sites:
-
In the Confluence sidebar, click Apps.
-
Click Scroll Sites.
-
Review your migrated sites in the My sites section.
Look for sites with the auto-upgraded label.
From now on, you can manage and update your sites in Scroll Sites.
Review the Auto-Upgrade Using the Upgrade Summary
The live site will remain live and still running until you complete the upgrade and re-activate the site from Scroll Sites.
From the My sites screen, follow these steps:
-
Look for the site that you want to upgrade and click the site name.
-
Review the items in the Auto-Upgrade summary box in Site settings in the same order in which they are listed in the box:
-
Click the first item in the list.
The page will scroll down automatically to the respective site settings. -
Open the setting and adjust it to reflect your original Viewport site.
Use the table below to help you make the adjustments. -
Scroll back to the Upgrade summary box and use the tick box to mark the item you’ve adjusted as completed.
-
Repeat the process for all items in the list.
-
Adjust settings of individual sites
The following table will help you review the specific details of your sites.
|
Setting |
How to adjust |
|---|---|
Look and Feel
Some files couldn’t be collected from Scroll Viewport. Review your theme configuration and upload the missing files. |
To add missing files, navigate in Scroll Sites to Site settings > Look and feel > Customize theme. Click through all of the tabs on the left hand side panel. Identify any Upload file fields that are empty. and upload the respective files. The theme preview will not work until the auto-upgrade is completed. |
Custom CSS
Your custom CSS code was transferred but may need minor adjustments due to design token differences between the products. |
Ensure that you adjust tokens, HTML attributes, components, etc. as needed. To identify which parts of your custom code need to be re-written, see Migrate Custom Code From Scroll Viewport to Scroll Sites. |
Custom JavaScript
Your custom JavaScript was transferred but may need adjustments depending on what it does. |
|
AI search
Add your AI integration credentials to enable AI Search. |
To add your OpenAI API key, go to https://platform.openai.com/api-keys and copy paste the same key you used in your Viewport site into the OpenAI API key field under Site settings > AI. |
Differences between Scroll Viewport’s and Scroll Sites' Help Center theme
While Viewport sites are migrated automatically, there are some differences between the outgoing Viewport app and new Scroll Sites:
-
🎨 Visual changes. The help center theme in Scroll Sites is not identical to the one in Scroll Viewport. Visual tweaks include font sizes, size of components, images etc.
-
📏 Banner images are centered. The banner image in Scroll Sites' help center theme is centered (both vertically and horizontally) while the one in Scroll Viewport is aligned to the top. We recommend you review and adjust your banner image file as needed.
-
🗑️ Removed icons from the portal and content source pages. The small material icons were removed from Scroll Sites' help center theme due to technical reasons. An improved solution will be coming.
-
📑 TOC now considers H2 to H6. The table of contents in Scroll Viewport’s help center theme only showed heading levels 2 to 4. Scroll Sites' help center theme will include headings up to level 6. However, from the information structure and readability perspective, we advise you to use headings segmentation on a page wisely and find the balance between using headings and child pages.
-
No full support for legacy pages. While Scroll Viewport never officially supported pages created with the Confluence legacy editor, some of its content still was rendered in acceptable ways. Since Confluence is deprecating the legacy editor soon, Scroll Sites no longer supports legacy editor elements. We recommend that you auto-convert all your pages to the new editor. Read more on Convert pages to the cloud editor.
-
🤖 Scroll Sites are AI ready. Every Scroll site includes
llms.txtandllms-full.txtfiles to support large language models. The Help Center theme provides the Use with AI menu that lets your site visitors easily copy articles as Markdown or open them directly in ChatGPT or Claude.
Complete Your Update
After you check off all the items in the Upgrade summary box, you can complete the upgrade and activate your Scroll site.
From the banner on top of the Site settings, follow these steps:
-
Click Mark as completed.
Scroll Sites prepares and sets up the new site. This process may take some time. -
To finish the upgrade process and switch your live site to the new site, click Complete upgrade.
Your site is now live and served from Scroll Sites.
Choose Your Update Strategy
By default, Scroll site's update strategy is set to the Manual updates option, to mirror the behavior of your Viewport site as closely as possible (content changes are published on demand by clicking a button).
In Scroll Sites you also have the option to switch to Live updates. That means that the moment you publish or update a Confluence page, the changes will appear in your Scroll Sites' website automatically within a couple of seconds.
If you'd like your content changes to reflect almost instantly in your site (no additional action required on your part), check out this new option from Site settings > Update strategy.