Issue tracking: Docs feedback
Establish a process for tracking feedback that comes in from the Docs footer.
Goals:
- New feedback is triaged within some SLA. Triaging involves assigning labels to note the state and related groups.
- TWs know how to act on feedback after it is triaged.
- Customer feedback helps us drive depth-over-breadth customer value.
- We have some way to see bigger-picture trends rather than just point solutions.
- Get a view into pending, active, and resolved feedback.
Related:
- https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/issues/234+
- Add lightweight feedback option to docs pages (docs-gitlab-com#202 - closed)
- https://docs.gitlab.com/development/documentation/workflow/#review-and-triage-documentation-only-backlog-issues
- Add a "docs feedback or ideas" section to TW page (gitlab-com/content-sites/handbook!13093 - closed)
- Coordinate reviews of docs website backlog (#624 - closed)
Edited by Amy Qualls