How do you review your docs prior to release?
| Answer | Count | Percent |
|
The same code review tools that engineers use to review software code | 184 | 24.8% |
|
Collaborative annotation tools like Google Docs or Quip | 101 | 13.61% |
|
Wiki sites like Confluence | 90 | 12.13% |
|
PDFs (e.g., using the commenting features) | 93 | 12.53% |
|
In-person meetings | 138 | 18.6% |
|
People comment on web pages by copying and pasting the text they have comments about | 77 | 10.38% |
|
Other | 59 | 7.95% |
|
|---|---|---|---|---|---|---|---|---|
| Total | 742 | 100 % |
How do you review your docs prior to release? - Text Data for Other
| 03/11/2020 | 58655177 | Wdesk supports comments. |
| 03/10/2020 | 58576961 | Feedback through Slack |
| 03/08/2020 | 58392284 | In my last project, I set up the inventory in Airtable and it is worth a shot! |
| 03/05/2020 | 58190512 | This might change if we go the GitHub route - Developers may edit the source and we will review changes as per the code, etc. |
| 03/03/2020 | 58100976 | company has its own doc review portal |
| 03/02/2020 | 57963812 | PR reviews in GitHub |
| 02/28/2020 | 57782552 | PR reviews in GitHub |
| 02/28/2020 | 57778038 | .doc |
| 02/27/2020 | 57767803 | Engineers review Word docs generated from content |
| 02/26/2020 | 57680804 | Slack |
Loading...
