Scroll Viewport sites are published as static HTML pages in an atomic publishing process that features two steps: Preview generation and Going live.
The preview generation is a long running task and the first step of the publishing process within Scroll Viewport. In this step, Scroll Viewport extracts your selected content and configured theme and creates static HTML pages. These pages are deployed to a web server, where the preview resides under a random URL. This URL is not exposed to web crawlers and can only be obtained from the user generating the preview.
Checklist before generating
To avoid needless repetition of the generation step, which can be time-consuming, we recommend checking the following:
Content source path segment: Make sure to check the configured path segments for the content sources
Theme: Make sure your theme is configured to your liking, as some changes might require re-publish.
If you're not sure how your documentation will look with the Help Center theme applied to it, you can use the article preview feature to avoid unnecessary publishing.
Once the generated preview is ready for production, the site can be taken live by clicking the Go live button in the preview and confirming it after being taken back to Confluence. This step switches the URLs of the preview content to the previously configured production URLs. From this point on, it will be available to your readers under the correct URL and will be visible to search engines.
Updating an existing site
Once your Viewport site has gone live, the Update site button will become active on the site details screen.
If you want to update a live Scroll Viewport for Cloud site, it works in the same way as mentioned above, by generating a preview of the site with updated content and then going live.
Should something go wrong during the update process, your live site remains untouched until you are ready to Go live with an updated site.
Using the change log to decide if the site needs updating
Viewport helps you to identify if you have content or theme changes that aren’t live yet. You can use the app’s change log and status indications to decide if your site needs to be updated or not.
Viewport’s change log will count all the text changes, moving and deleting of pages since the update button was last clicked. Multiple changes to a page are counted as 1 change:
The status messages will tell you if the theme was edited or if new content sources were added since the last site generation:
Note that updating your site will regenerate all pages that are part of your site’s content sources (e.g. all pages of the space).