Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add detail about docs gardening to handbook #10501

Merged
merged 4 commits into from
Jan 31, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions contents/handbook/content-and-docs/docs.md
Original file line number Diff line number Diff line change
Expand Up @@ -134,6 +134,17 @@ 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
daniloc marked this conversation as resolved.
Show resolved Hide resolved
- #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.

## FAQ

### I'm really busy, can the content team write docs for me?
Expand Down