We are trying to get our heads around how to implement remote publishing of versioned spaces and hope you can shed some light!
We have several internal documentation spaces for different software products and use Scroll versions to manage versions and Comala workflows for the internal review process. Our documentation spaces are edited across engineering teams and we use the Public Master Space approach but only really use the Author view. The documentation is currently made available for customers using Scroll PDF and HTML exports of certain parts of the documentation spaces.
We are now trying to figure out a straightforward workflow for also publishing certain content from the documentation spaces to a remote Confluence instance (available to anonymous users) using Scroll Versions, Scroll Remote Publishing Endpoint, and Scroll Viewport.
Would you suggest publishing the internal spaces to the remote instance by publishing versions to new separate spaces and then new versions to an existing “latest” space? And then use Scroll Viewport on the remote instance to allow styling and use of a version picker?
And since it does not seem possible to publish only parts of a space, do you recommend using the Comala Workflow integration to only publish completed pages or would you rather exclude this information by moving (copying the versioned pages) to another separate internal space?
Also, we currently use Scroll Ignore macros to hide internal content from being included in the PDF and HTML exports (content such as internal instructions and Export to template buttons, Workflow reports, and Recently Updated macros). How would you hide such content from being shown on the remote Confluence site?
Best and many thanks,
Please sign in to leave a comment.