From ed152174e2340bed34c489f3d3978fa4921d62d2 Mon Sep 17 00:00:00 2001 From: Danilo Campos Date: Tue, 28 Jan 2025 10:49:01 -0500 Subject: [PATCH 1/3] Add detail about docs gardening --- contents/handbook/content-and-docs/docs.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/contents/handbook/content-and-docs/docs.md b/contents/handbook/content-and-docs/docs.md index cd08f6f1221b..2cfa507ae2a7 100644 --- a/contents/handbook/content-and-docs/docs.md +++ b/contents/handbook/content-and-docs/docs.md @@ -134,6 +134,16 @@ Use the following settings: - Remove any zooming-in for clicks, as this can sometimes make videos hard to follow. - For exporting: use MP4, 720, 60 fps, and "web" quality +## Docs gardener + +Each week the content & docs crew picks someone to review the state of feedback across these channels: + +- #docs-feedback +- #content-docs-ideas +- Zendesk tickets where **root cause** is `documentation unclear` + +Where appropriate and actionable, the gardener should create new issues to capture what surfaces from such feedback. This should occupy no more than 2-4 hours of effort each week. + ## FAQ ### I'm really busy, can the content team write docs for me? From 48faa607e92e87c004c1fa28885292756b40e3a9 Mon Sep 17 00:00:00 2001 From: Danilo Campos Date: Fri, 31 Jan 2025 15:45:05 -0500 Subject: [PATCH 2/3] Update contents/handbook/content-and-docs/docs.md Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com> --- contents/handbook/content-and-docs/docs.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/contents/handbook/content-and-docs/docs.md b/contents/handbook/content-and-docs/docs.md index 2cfa507ae2a7..4f81d836cab2 100644 --- a/contents/handbook/content-and-docs/docs.md +++ b/contents/handbook/content-and-docs/docs.md @@ -140,6 +140,8 @@ Each week the content & docs crew picks someone to review the state of feedback - #docs-feedback - #content-docs-ideas +- #ask-max for questions missing content +- [Inkeep](https://dashboard-9txgpp4yi.preview.inkeep.com/posthog/projects/clz7fyu8i001bomqpr7t8lds8/reports) - Zendesk tickets where **root cause** is `documentation unclear` Where appropriate and actionable, the gardener should create new issues to capture what surfaces from such feedback. This should occupy no more than 2-4 hours of effort each week. From e7040301d80648e3562f434fc0f0fe0ee7374829 Mon Sep 17 00:00:00 2001 From: Danilo Campos Date: Fri, 31 Jan 2025 15:47:25 -0500 Subject: [PATCH 3/3] Add link to Zendesk view for docs unclear --- contents/handbook/content-and-docs/docs.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/contents/handbook/content-and-docs/docs.md b/contents/handbook/content-and-docs/docs.md index 2cfa507ae2a7..c393da49e640 100644 --- a/contents/handbook/content-and-docs/docs.md +++ b/contents/handbook/content-and-docs/docs.md @@ -140,7 +140,8 @@ Each week the content & docs crew picks someone to review the state of feedback - #docs-feedback - #content-docs-ideas -- Zendesk tickets where **root cause** is `documentation unclear` +- #ask-max for questions missing content +- Zendesk tickets [where **root cause** is `documentation unclear`](https://posthoghelp.zendesk.com/agent/filters/33465387985947) Where appropriate and actionable, the gardener should create new issues to capture what surfaces from such feedback. This should occupy no more than 2-4 hours of effort each week.