How EMs, PMs, PDs and TWs collaborate to create feature documentation to the handbook
There is currently a process (or processes) EMs, PMs, PDs and TWs follow to create feature documentation but it's not anywhere in our handbook. As a result, we're not sure what teams are doing and how we can all benefit from best practices. We need to find out what different teams are doing, what the best process/guidance can be and explore whether it should be added to:
-
Product handbook: https://about.gitlab.com/handbook/product/product-processes/#writing-about-features -
Product handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/ -
Link to existing documentation for this workflow from the product development flow www-gitlab-com!98400 (merged) -
Engineering handbook pages (as the initial draft is created as part of the feature MR by engineers) -
Tech writing handbook pages
This is some currently available documentation to be linked to from the overview that's written up: https://docs.gitlab.com/ee/development/documentation/workflow.html https://about.gitlab.com/handbook/engineering/ux/technical-writing/workflow/
Edited by Farnoosh Seifoddini