How does the new (partial) update process work?

The new update process will look and work exactly the same as before. However, under the hood the “normal” process (initiated through the ‘update site’ button) has changed.

In most scenarios, you won’t perceive any difference at all but in some scenarios your site will generate much faster. This is because our new ‘partial updating’ process just generates those pages and attachment that have been added or changed since the last update and re-uses the rest.

What does the new ‘update site’ process do and what’s the benefit?

The new ‘update site’ process changes the logic with which site are generated. Before, all pages of your site were re-generated, independent of whether you had made changes to them or not.

This meant: if you corrected a typo on a single page, you still had to wait for all the pages in your site to generate. This could be quiet time consuming in sites with lots of pages and with lots of attachments on those pages.

The new process re-uses those pages and attachment if we know they haven’t changed. This will bring the following benefits:

Main benefit: site generations are much faster for specific scenarios (e.g. correcting a typo on a page)
Side effect: the generation is generally more stable because we make less calls to Confluence

To avoid accidentally re-using pages or attachment that have changed (resulting in an outdated site), our implementation is still, at first, very careful when deciding whether to re-use or re-generate.

In short: If it’s hard to know whether content can be re-used or not, the implementation always falls back to generating the content again. Better safe than sorry.

In what cases does Viewport decide it's better to re-generate the content?

All of the site is always re-generated if

any theme settings are changed
any site settings are changed
new versions or content sources are added
a new version of Scroll Viewport is released

Individual pages are always re-generated if

the page is a homepage of a content source
the body of the page uses macros like the children display, content by label, include page or include excerpt macro
the page previously produced a warning in the preview report

My site isn’t updating correctly. What do I do?

Are you finding pages in your site that haven’t been generated correctly. For example, you have updated a page in Confluence or made changes to the theme that are still not reflected in your site after you’ve gone live with the changes.

If such a generation error happens to you, please do reach out to help@k15t.com so we can identify and fix the problem.