Needs links that always go to the latest version of a page, on Cloud

Comments

4 comments

  • Official comment
    Avatar
    K15t Team

    Hi Kelly,

    I'm Laura from the Scroll Viewport team. First, thanks for your questions and for evaluating Scroll Viewport and Scroll Documents as your documentation publishing solution.

    Programmatically directing users to the latest version of documentation on your online help center is unfortunately not (yet) possible with Scroll Viewport - unless you only maintain one version on the live site at a given time.

    If you’re only showing the latest version in your help center, then we recommend you add the working version of your Scroll Document to your Viewport site, as explained in our help article Which Document Versions Should I Add to My Site?.

    From there, simply Save a version with Scroll Documents before making any changes to your documentation (e.g. for a new release). That way you can keep an internal version history that references older versions of your documentation. Once your version with the outdated content is saved, you can proceed to overwrite the content on the working version with the planned changes. Then it’s simply a matter of clicking Update Site in Scroll Viewport to bring the changes live on your site.

    However, if you’d like to still show older versions of your documentation to your customers for them to see and access in the help center, then you would unfortunately be facing the issues that you describe (the latest version of your articles would always receive a new pageID).

    Having said that, we do plan to make URLs more stable in the future (especially across versions). As part of those plans we are also considering support for functional URL formats that contain virtual versions such as "latest”. That improvement would give you the flexibility you need to always direct your users to the latest version of your content - even if there are several versions to select from on your site.

    I'm very sorry for the current limitations and any inconvenience caused.

    On a different note. Since you mention that you keep two separate sets of documentation, one for your Desktop Site and one for your Mobile App: Perhaps you are interested in knowing that we are currently working on a new feature in Scroll Documents (which will then be supported by Viewport as well) that would allow you to manage content variants from one document set while specifying which pages of your document belong to the Mobile App and which to the Desktop App. That is especially helpful if there is lots of overlap between these sets of documentation.

    With the variants feature, you would then have the option to deliver these content variants to two separate sites or to the same site, displaying a variants switcher. This switcher would look similar to the current version switcher and allows your users to pick the content variant that is relevant for them.
    If you’re interested in the feature, we’d be more than happy to invite you to test out the beta version when it’s ready. Just shoot me an email (lparraga@k15t.com) so I can note down your contact details on our list of beta testers.

    Let me know if you have further questions on any of this!

    Cheers,

    Laura

    Comment actions Permalink
  • Avatar
    Amit Kapoor

    Hi,

    I want to add this.

    Why do you want to jump to the latest version when ideally, the customer should see the corresponding matching version of another (MA/DS) and not the latest?

    Once you have somehow managed to implement, you will probably end up in trouble of fixing user's context of where he is, where you want him to go, and what was he wanting to go. So I think what is implemented right now is better. I have not seen anyone doing what you are looking for. Or, just do it like Laura suggested. That's the only way out.

    Also, from usability perspective - "people/users spend more time on other websites than your website". So doing something so different that they are not used to or have seen might give them a not desirable experience. But by all means, if you are sure - please go ahead. My best wishes.

    -Amit

    0
    Comment actions Permalink
  • Avatar
    Kelly S

    Laura, I very much appreciate the time you took to answer the question. I appreciate your thoughts on the workflow and the insight into the changes you're working on/planning to address down the road. I will play around with it according to your suggestions and see if I can make it work for us. I had an inkling that that's kind of how we'd have to organize things to achieve the result I'm looking for, but it is very helpful to get confirmation on that (so I know that I'm not just missing something). The variants feature sounds awesome, I can't wait to see how that works. Thank you for the invite to be a beta tester - I don't think I'm quite ready for that yet (since I'm kind of still figuring out how to put everything together just to get started) but I will definitely keep that in mind.

     

    Amit, I also appreciate your thoughts. I do understand people spend more time on other websites than on mine, so the website should act the way they expect it to. That is actually the issue I'm trying to address - linking them to the content they will expect when they click on a link. I simplified my situation for the sake of the question, but my reality is that I have a dozen software products that are all related (and so their info needs to link back and forth a lot), but they're all updated on totally different schedules. There really aren't "corresponding matching" versions between the different products. It's unfortunately not as simple as "if a user is on MAv8 then I know they'll be on DS v1." When I'm writing my DS v1 information, I have no idea if the eventual reader will be on DS v1 + MA v5 + widget v52, or if they'll be on DS v 1 + MA v8 + widget v65, etc.

    So - if I can't know what version my reader will be on, then the safest thing to do is the default to the latest information whenever I'm linking from 1 product's info to another (knowing that most of my users will be on the latest version of any of my products, most of the time).

     

     

     

    As I'm typing this out, I'm slowly realizing - maybe the best way to approach this is to create a a dozen different viewport sites, one for each of my products, instead of 1 viewport houses them all. I will have to think more about that.

    0
    Comment actions Permalink
  • Avatar
    K15t Team (Edited )

    Thanks Kelly!

    If you do change your mind on the variants testing, just let me know! And any further questions you might come across as you figure out your ideal Viewport setup, we're more than happy to help!

    Cheers,

    Laura

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk