Navigation docs

[paolodamico]

Draft proposal of navigation documentation. Related to PostHog/posthog#1775

[paolodamico]

Largest changes for which I'd particularly like to get input:

1. Merging Actions & Events. From a user call yesterday (using Experiment: Improving actions UX? posthog#1841), seems like a natural step in the mental model. This is now a section of user interactions / user engagement, where events is any interaction and action is a particular interaction or series of interactions.

2. Should we keep project config in the main nav? Project config can already be accessed from the top bar (see screenshot below), based on the settings available in the project configuration it seems like this page will seldom be accessed, and with the command palette users may discover the exact settings they need anyways.

3. Should we keep retention in insights? My bet is that once we get this up to speed with CH and Retention allow selection of A and B event posthog#1344 & Retention cohorts graphs posthog#1936 this will be a hot feature. It also goes to the point of setting standards and helping users understand how to do product analytics, by putting it in a prominent place, we'll nudge more users to measure and optimize this metric.

[Twixes]

I feel like settings should be somewhat more prominent. I think that we should keep the sidebar analytics-focused, though making settings just a small icon in the project selectors also seems to obscure them a bit. Not sure yet about alternatives.

[paolodamico]

I feel like settings should be somewhat more prominent. I think that we should keep the sidebar analytics-focused, though making settings just a small icon in the project selectors also seems to obscure them a bit. Not sure yet about alternatives.

Yup, how about we A/B test this? A -> Having the small icon + command palette only. B -> Small icon, command palette & main icon in sidebar.

[yakkomajuri]

This sounds to me like it's more Handbook than Docs, since it discusses the rationale for adding new items to the nav and all

[paolodamico]

Re @yakkomajuri well I would argue this is documenting something related to the app, the handbook feels more for company stuff, but I'm not too set on having it in any particular place.

[yakkomajuri]

I see the value of this in the Docs, but bits like this:

Adding navigation items

When adding features, the following guidelines can be followed to understand where to place the navigation items.
...

Are instructions for us on how to do things, which generally goes on the handbook