Linking between versioned spaces

Comments

5 comments

  • Avatar
    Roman Serazhiev

    Hi Nigel,

    When you are publishing to a new or existing space, the target space will be unversioned. Currently, it is not supported to publish to a versioned space: https://k15t.jira.com/browse/VSN-2054. Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, comment on or vote for this issue. You'll then get a notification for every status update on the issue.

    So, in your use-case scenario when the new version is about to come out, you can created a new version in the master space, do the changes, and the publish it to a space that always contains information form the latest version. For example, "Latest" space.

    That way links will always be to the same space.

    Did I understand you correctly with your requirements?

    Cheers,

    Roman.

    0
    Comment actions Permalink
  • Avatar
    Nigel Whitaker

    Hi Roman,

    Thanks for the response.  I'm not trying to publish to a versioned space (as in VSN-2054).   Instead we were thinking about publishing to a set of spaces, the 'current' or latest version and a number of our supported older versions.  Very similar to how Atlassian do it, for example this page with the versions combo-box at the top:  https://confluence.atlassian.com/doc/confluence-installation-guide-135681.html

    You suggested publishing to a space that always contains latest version.   And I can see how I would always have a live latest space, but that doesn't give me the old spaces.   I'll try to use Atlassian as an example and lets imagine that I am working at Atlassian on Confluence version 5.9....

    So the live confluence site has CONF (the 'Confluence Latest' version which is 5.8),  CONF57, CONF56, CONF55 etc...

    In the master space I can use scroll versions to "Add Version" can create a 5.9 version number.  And we can update the master content with the 5.9 new changes and features.

    If I "publish to existing Space" with version=5.9 and SpaceKey=CONF then the latest CONF space will be updated.  But I won't then have a CONF58 space for the 5.8 documentation.

    If I "publish to a new space'  with version=5.9 and SpaceKey=CONF59  then I get a proper space for my new version but my 'latest' or CONF space is now out of date.

    I was wondering if there was a:  "copy latest to previous version (using the list in the manage versions page),  and then update latest" mechanism?

    Or should I publish my 5.9 twice? once to a new CONF59 space and also to the existing CONF space.   I can see this being a painful problem then keeping them both in sync - for example with the 5.9.1, 5.9.2 release notes etc.

    I hope this example illustrates what we are trying to do.

    Thanks,

    Nigel

    0
    Comment actions Permalink
  • Avatar
    Nigel Whitaker

    And in the above example I links between spaces would use the latest space, so for example  CONF:page and wouldn't need updating on every product release.

    0
    Comment actions Permalink
  • Avatar
    Nigel Whitaker

    Or perhaps when 5.9 is ready I do two publishing processes:

    1. "Publish to existing"  with version=5.9 SpaceKey=CONF
    2. "Publish to new" with version=5.8 and SpaceKey=CONF58

    I'm trying to understand how scroll versions would be used by a documentation setup similar to Atlassians with spaces for previous versions or even your site with the VSN, VSN10 and VSN21 spaces.

    Thanks,

    Nigel

    0
    Comment actions Permalink
  • Avatar
    Nils Bier

    Hi Nigel,

    Atlassian is using Scroll Viewport to provide their documentation in their corporate design and to display the version and product dropdown on the page you've mentioned.

    Once they release a new version, they publish the latest version within the same space (spacekey "DOC") and publish the previous version to a new space with a version related spacekey (in their case "CONFxx"). Those spaces are then linked from the dropdown.

    By following this approach, the links to space "DOC" always show the latest information and a reader can simply switch to the version he's using by selecting it in the drop down provided by Scroll Viewport.

    I hope that information helps. Please let us know if you have any further questions.

    Best,Nils

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk