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

Settings 4000 #26470

Open
corywatilo opened this issue Nov 27, 2024 · 0 comments
Open

Settings 4000 #26470

corywatilo opened this issue Nov 27, 2024 · 0 comments

Comments

@corywatilo
Copy link
Contributor

corywatilo commented Nov 27, 2024

Finding the right setting in PostHog is sort of tricky. While settings generally all live in the same section, there are multiple entry points which can make it confusing since I'm never quite sure where each option is going to land me. And I'm not sure if I'm missing settings when I get taken different places.

We previous did some work on organizing settings based on this original proposal for the PostHog 3000 UI.

Top of mind issues/things to solve

  • It's weird to have project-related settings and product-specific settings mixed together.
    • As we move toward each product being self-contained, product-specific settings should be accessible within each product. (Session replay is a good example of this! They're all available at the Configure button which opens a side pane with the relevant settings.) But we should standardize this and use the same button label.
  • There's an Integrations tab - not sure the status of this since we're replacing most of this with Pipelines?
  • You can click on a settings subheader to see all settings for a category, but can also click on a child option which only shows a subset, which seems funky/unnecessary.
  • Most of the options under the user dropdown menu are duplicated
    • You can get to account options and org options from the settings button, you can switch orgs in the breadcrumb
    • But it's the only place you can access billing. And billing doesn't make sense here since it's really an org thing and not a user thing. It also makes changing the theme more visible, though a lot of people miss this too.
  • We have a lot of text in the settings, and the info hierarchy could be improved. I tried to create some better patterns in this wire below.

image


Related: There's also a VS Code-inspired idea for managing settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant