Page deployment can take a while, especially on slower machines & connections, because every page gets generated on each deployment. By first determining which pages have changed (which should be possible since Primo handles both the presentation and content layers), it should be able to only generate pages that have changed & cut deployment time to a fraction of what it is now.
Page deployment can take a while, especially on slower machines & connections, because every page gets generated on each deployment. By first determining which pages have changed (which should be possible since Primo handles both the presentation and content layers), it should be able to only generate pages that have changed & cut deployment time to a fraction of what it is now.