We are planning to use scroll versions for our technical documentation. We have to maintain documentation for multiple releases and multiple languages.
When we start with a new version of the documentation for a new release, we want to start from an existing version, and modify the appropriate pages (of the features which have been changed).
What is the best approach to manage 'this page still needs to be translated', or "this page still needs to be reviewed'.
A basic documentation set (one release, one language) contains about 160 pages.
Could we use the workbox in combination with scroll versions ?
I've created a feature request for the integration of the workbox in Scroll Versions: https://k15t.jira.com/browse/VSN-456
Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, to comment or to vote for this issue.
FYI: At K15t, we are using labels (in combination with the content-by-label macro) and "@-mentions" as workaround to manage the workflow. Maybe this works for you too.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG