Recherches récentes
Pas de recherche récente

Steve Moss
Adhésion le 16 oct. 2021
·
Dernière activité le 03 mai 2022
Suivis
0
Abonnés
0
Activité totale
6
Votes
0
Abonnements
3
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Steve Moss
Steve Moss a ajouté un commentaire,
Hi Sorin. I would be interested in talking with you about collaboration options. What's the best way for me to get in touch?
Afficher le commentaire · Publication le 03 mai 2022 · Steve Moss
0
Abonnés
0
Votes
0
Commentaire
Steve Moss a ajouté un commentaire,
Thanks for the update Katarzyna. One option that would simplify our current workflow would be an "export article" feature. At the moment, the articles have to be copied and pasted into Google Docs, but a bulk export to HTML, Word or even GD directly would save a lot time and effort.
Afficher le commentaire · Publication le 03 avr. 2022 · Steve Moss
0
Abonnés
0
Votes
0
Commentaire
Steve Moss a ajouté un commentaire,
Hi Katarzyna. In our documentation development workflow we need to be able to allow multiple reviewers to check the articles (around 20 in this current release cycle). Reviewers need to be able to add comments and suggestions but not actually change the material. We have used this approach as we believe it is the simplest way for non-tech writers to indicate what changes need to be made, rather than spending time trying to come up with suitable wording and replacing text themselves.
One way of achieving our goal is to copy/paste updated (but not published) articles from preview mode directly into a Google Docs document. This document can then be shared with the reviewers (who can see who has already said what) and they can add their own comments, as required. When they are finished, we update the Google Docs version of each article. If the changes were significant, the reviewers can then look at the GD version again to check that their suggestions are correctly applied. In most cases the changes are straightforward, so they are simply applied to the original version of the updated article and then published in the usual way.
The main benefit of this approach is to leverage the power of GD as a collaboration tool. It also means that reviewers do not have to be familiar with using Guide editor or needing to use a license seat.
Is there any way that some or all of this approach can be used with the current review features in Zendesk Guide?
Afficher le commentaire · Modification le 16 mars 2022 · Steve Moss
0
Abonnés
1
vote
0
Commentaire