-
Notifications
You must be signed in to change notification settings - Fork 39
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
Consider ways to reduce clutter in "All Popups" table #878
Comments
|
@danieliser Removed the extra css class from the table, hidden title and date by default, and added the extra pointer. |
…te columns are hidden by default Issue: #878
Nicely done. |
With the addition of the enabled toggle, the "All Popups" page is getting a little cluttered when one has tags/categories enabled too, which we know almost 6% of our customers do. This is what it looks like on my laptop screen which is definitely a bit cluttered:
![laptop-example](https://user-images.githubusercontent.com/9730040/93239913-6f4dc200-f751-11ea-8747-f6c6edd54bf7.png)
Even on my larger monitor with the sidebar closed:
![monitor-example](https://user-images.githubusercontent.com/9730040/93239917-707eef00-f751-11ea-85e2-1d14ce9c94e1.png)
We also wanted to add in the conversion counter (see #775) columns too which would make this even more cluttered.
Since we don't recommend people ever use popmake-{name}, do you think we could remove that from the CSS classes? Other than that, the only thing else we could consider removing is the whole CSS classes column or the title column. If we just remove the second CSS class, it wouldn't be too bad on the larger monitor but would be still a bit tight after we add conversion counters.
Alternatively (or additionally), we may be able to get rid of the Title or published date.
The other main question is: Do people use "Screen Options" to adjust these? If so, it's not something we'd have to worry about too much. My hunch is that most people see the clutter and do not think of the "Screen Options".
The text was updated successfully, but these errors were encountered: