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

Discussion: Sidebar options #1898

Closed
paolodamico opened this issue Oct 15, 2020 · 10 comments
Closed

Discussion: Sidebar options #1898

paolodamico opened this issue Oct 15, 2020 · 10 comments

Comments

@paolodamico
Copy link
Contributor

Related to #1775, and thanks to a discussion with @Twixes, we landed on two options for the sidebar menu and we need input. Which option should we use for the next design release? The only difference is the layout of the sidebar, the icons and titles are still WIP (do not consider them for this).

Option A

Key benefit: Familar layout
wide-menu

Option B

Key Benefit: More screen space for the main elements
regular-page

@timgl
Copy link
Collaborator

timgl commented Oct 15, 2020

I think I prefer 2, more space = better

@EDsCODE
Copy link
Member

EDsCODE commented Oct 15, 2020

RE: layout—I also prefer 2 for the same reason above.

RE:UI—I'd suggest making the colors and texture more sleek and introduce some retro elements to create a sort of sleek retro style rather than a pure retro interface (I can try to show this better in a followup comment). I'd say the logo and posthog.com landing graphics do a fairly good job of mixing those two styles

@mariusandra
Copy link
Collaborator

What about both, a'la wordpress:

2020-10-15 17 28 32

@macobo
Copy link
Contributor

macobo commented Oct 15, 2020

I really like option 2, gives the main content space to breathe :

@lottiecoxon
Copy link
Contributor

I prefer the second option - it feels cleaner

@yakkomajuri
Copy link
Contributor

yakkomajuri commented Oct 15, 2020

Agree with the "Option C" people have put out where we have the second option with some sort of sub-nav.

Also agree with @EDsCODE and I think I actually get the point. Not too big of a fan of the current design to be honest.

@paolodamico
Copy link
Contributor Author

Thanks everyone for the quick turnaround and honest feedback! Just to be clear, Option C would be doing Option A for large screens and Option B for smaller screens, which I actually tend to agree (at least try it in practice and see how it works).

I'll also work more on the UI based on the feedback from @EDsCODE & @yakkomajuri

@Twixes
Copy link
Member

Twixes commented Oct 15, 2020

Actually I vote B, but I'm concerned about 2 things:

  1. Option "Live" doesn't seem clear (as in: as a user it's not apparent to me what "live" things can be found there) or accurate (it is live data, but it also is all historic data, so I'd also emphasize that it's not just a stream of whatever's coming in, but basically full access to event/action/session data) to me.
  2. How do we lay out organization/project/user settings when they're out of the side bar? This is the crucial difference from the current layout actually, because settings pages are specifically the ones that have been removed from the sidebar in these proposals here. This also includes instance-wide Licenses.

@lottiecoxon
Copy link
Contributor

I did not see the GIF of the menu that pops out when hovered over- this is cool and gives me kinda workspace vibes more than the other two - change my vote to C

@paolodamico
Copy link
Contributor Author

Ok so we're aligned on trying option C as described above, so closing this issue to continue conversation on main (#1775). Will share updated design today. @Twixes great points, will try to address them in the updated designs + PostHog/posthog.com#501

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

8 participants