You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thinking about further changes to help users get started for PostHog/meta#171 and it occurred to me that we are often especially bad at documenting small new features. These go in the changelog and get surfaced through changelog processes, but not the docs. We can (and should and will) solve this through content improvements, but we could also pull changelog items into the docs on each product overview.
Basically, what if we put the latest changes in relevantly tagged products here:
That would help users get started with new features, right?
What kind of request is this?
New docs page / feature
Update to existing pages
Which product is this for?
All
What's the priority?
Urgent AND important ("great scott, this is horribly wrong / out of date")
Important, but not urgent ("we need to do this, but not immediately")
Non-urgent (this could be better / would be nice to have)
Is there a deadline for this change?
Yes (please specify)
No
The text was updated successfully, but these errors were encountered:
Summary
Thinking about further changes to help users get started for PostHog/meta#171 and it occurred to me that we are often especially bad at documenting small new features. These go in the changelog and get surfaced through changelog processes, but not the docs. We can (and should and will) solve this through content improvements, but we could also pull changelog items into the docs on each product overview.
Basically, what if we put the latest changes in relevantly tagged products here:
That would help users get started with new features, right?
What kind of request is this?
Which product is this for?
What's the priority?
Is there a deadline for this change?
The text was updated successfully, but these errors were encountered: