Publishing versioned spaces to remote Confluence instance

Comments

4 comments

  • Avatar
    Roman Serazhiev

    Hi Annica,

    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?
    If you need all versions — not just the latest — on the remote side, then I would suggest publishing as you proposed: versions to new separate spaces and then new versions to an existing “latest” space. You can then combine these published spaces into a version picker.

    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?
    I don't think you need to move pages out of the space before publishing. If there are not approved pages in the master space, you could enable a checkbox in the publishing dialogue that would prevent those page from publishing. In this case, only Complete pages are published.

    we currently use Scroll Ignore macros... How would you hide such content from being shown on the remote Confluence site?
    This depends if you have Scroll PDF and HTML Exporters installed on the remote side. If they are — same behaviour, if they are not — they are rendered as unknown macros. 

    Does this help?

    Roman.

    -1
    Comment actions Permalink
  • Avatar
    Annica Waltersson

    Hi Roman,

    And thank you!

    Regarding the internal content included in Scroll Ignore macros on the master spaces, we would ideally like to continue having this kind of internal instructions available for editors internally but would like the information to be hidden from customers viewing the published content on the remote instance. I was thinking there might be another macro available or a way to hide content by tweaking the Viewport theme?

    Would it be possible to discuss our use case in a more private matter? We would also like to find out more on theme development assistance.

    Thanks again,
    Annica

    0
    Comment actions Permalink
  • Avatar
    Roman Serazhiev

    Hi Annica,

    if the content you would like to hide is part of the page content then it is a little bit tricky but possible. This is what I would recommend.

    1. Put the information you want to display only for internal audience in the scroll-ignore macro (or even create your own simple macro to do that).
    2. In your theme create a macro override following this instructions and put the following inside the template (name of the velocity file should be "scroll-ignore.vm"):

    #if($user.isInGroup("internal-user-group"))
    $body
    #end

    internal-user-group is the name of the confluence group your internal users are in. Only users that are part of this group will see the output of the macro.

     

    If you would like to discuss theme development with us, please email our Professional Services team at sales@k15t.com to arrange a call.

    Cheers,
    Roman.

    0
    Comment actions Permalink
  • Avatar
    Annica Waltersson

    Hi Roman,

    Thank you, I will give your recommendation a try and also reach out to your Professional Services team to discuss theme development.


    Cheers,
    Annica

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk