How Atlassian uses K15t Software Scroll Content Management Tools

Hi everybody,

I’m working for K15t Software GmbH, we are specialized on developing content management add-ons for the collaboration platform Atlassian Confluence.

I just wanted to let you know that we’ve released a press release at PR Newswire last week about how the technical writers at Atlassian are using our add-on Scroll Versions.
You can find the whole press release under the following here: K15t Software Helps Atlassian Technical Writers Keep Pace with Agile Development Teams

Please feel free to have a deeper look at the press release.
If you have any questions or need further information, please feel free to ask, I’ll be happy to help.

Looking forward hearing from you.

Cheers,
Nils

Comments

  1. Nils Bier Post author

    Hi Michael,

    thanks for your open feedback, highly appreciated!

    We are tracking the mentioned points about accidentially edited pages in our JIRA system:

    – Restrict the edit of the “Currently Published” version: https://k15t.jira.com/browse/VSN-1334- Allow to set permissions for existing versions: https://k15t.jira.com/browse/VSN-17

    To counteract the described problem with the links, we overwrite the Insert > Link UI.
    However I can understand that using shortcuts is not very practical. That’s a general problem with Scroll Versions – as we need to overwrite some Confluence elements (e.g. the pagetree, the links via UI, etc.) to hide the versioned pages and allow to have multiple pages with the same pagetitle within the same space, it’s hard to define where to stop using our own UI elements.

    In the next versions of Scroll Versions we’ll try to increase the UX and make it more user friendly for “non-technical-writers”.

    Thanks again for your feedback.

    Cheers,Nils

  2. Nils Bier Post author

    Hi Michael,

    thanks for your open feedback, highly appreciated!

    We are tracking the mentioned points about accidentially edited pages in our JIRA system:

    – Restrict the edit of the “Currently Published” version: https://k15t.jira.com/browse/VSN-1334- Allow to set permissions for existing versions: https://k15t.jira.com/browse/VSN-17

    To counteract the described problem with the links, we overwrite the Insert > Link UI.
    However I can understand that using shortcuts is not very practical. That’s a general problem with Scroll Versions – as we need to overwrite some Confluence elements (e.g. the pagetree, the links via UI, etc.) to hide the versioned pages and allow to have multiple pages with the same pagetitle within the same space, it’s hard to define where to stop using our own UI elements.

    In the next versions of Scroll Versions we’ll try to increase the UX and make it more user friendly for “non-technical-writers”.

    Thanks again for your feedback.

    Cheers,Nils

Your email address will not be published. Required fields are marked *