search

PostHog / meta

This is a place to discuss non-product issues in public.
MIT License
18 stars 4 forks source link

RFC: Marketing & Content – questions, process etc. #108

Closed andyvan-ph closed 1 year ago

andyvan-ph commented 1 year ago

As per my PR on the handbook, the Marketing team is evolving to take greater ownership of all content, specifically working with Website & Docs to ensure the docs are up-to-date and maintained to a high-standard.

This RFC is to discuss implications, how we'll make this work as a team, and how the content team and website team work together.

ivanagas commented 1 year ago

My thoughts on when to work on docs:

  1. New, updated feature, product (triggered by small team)
  2. Dogfooding. Everything we (the whole PostHog team) want to do with PostHog is well documented, we can link to relevant docs as support answers.
  3. The quality-to-readership ratio remains high, we make sure the most read docs are readable, useful. Feedback is positive.
andyvan-ph commented 1 year ago

2. Dogfooding. Everything we (the whole PostHog team) want to do with PostHog is well documented, we can link to relevant docs as support answers.

This is a great point. To me, we want to reach a point where most community questions can be answered with a link to the docs, or a tutorial.

I'm wondering if we should start keeping a record of questions (inc. Slack) where the answer wasn't in the docs?

joethreepwood commented 1 year ago

I'm wondering if we should start keeping a record of questions (inc. Slack) where the answer wasn't in the docs?

Well, bear in mind we're edging towards just removing the Slack. And also, we ideally want these questions in the forum so that we don't have to manually log them.