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

Make Dashboard widgets more readable and less busy-looking #3093

Closed
mattab opened this issue Apr 5, 2012 · 9 comments
Closed

Make Dashboard widgets more readable and less busy-looking #3093

mattab opened this issue Apr 5, 2012 · 9 comments
Assignees
Labels
Critical Indicates the severity of an issue is very critical and the issue has a very high priority. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Apr 5, 2012

The Piwik dashboard is very useful and practical, but it can be a daunting for a first time user.

Each dashboard widget shows footer icons, pager, ... but they are usually rarely used. Especially since we store changes in the database and apply them when opening the dashboard again. Therefore we want to hide the widget footer by default but give users the possibility to "expand" the footer. Some reports that provide further controls should be able to add controls to this by default hidden footer to hide complexity. It's up to each report to define useful default values.

Also made the dataTable and All Websites Dashboard look nicer. For instance removed some borders.

@mattab
Copy link
Member Author

mattab commented Apr 5, 2012

Attachment: example simpler dashboard design with only 3 css changes
lights switched off dashboard.png

@julienmoumne
Copy link
Member

Great idea

Shouldn't this be built as a theme ? #177

@mattab
Copy link
Member Author

mattab commented Apr 6, 2012

Maybe a bit too simple use case for a theme.

But maybe even better... Could we simplify the Piwik design such as in the screenshot by default for all dashboards? (and not make it an option)

Note: the widget border and bar would still display on hover on the datatable.

@mattab
Copy link
Member Author

mattab commented Jun 4, 2012

In fact we could even

  • hide the Piwik logo
  • move up the whole screens & reports and save many pixels!
  • show the top menu on hover only (show with 50%opacity otherwise ?)

These changes + the clarification / opacity of the dashboard widgets would basically make a nice "full screen" piwik experience.

See also suggestion post at: http://sfew.websitetoolbox.com/post/Web-Analytics-Dashboard-for-Review-5932963

Icon could be: http://www.iconfinder.com/icondetails/8809/32/idea_light_bulb_power_icon and http://www.iconfinder.com/icondetails/3474/32/idea_light_bulb_tip_icon

or http://www.iconfinder.com/icondetails/54428/32/lightbulb_icon and http://www.iconfinder.com/icondetails/59272/32/lightbulb_icon

@mattab
Copy link
Member Author

mattab commented Aug 7, 2012

What do you think about this?

@gka
Copy link
Contributor

gka commented Jan 12, 2013

Attachment:
piwik-lights-off.png

@halfdan
Copy link
Member

halfdan commented Mar 11, 2013

This is beautiful and will look even more beautiful when combined with a vertical menu (which I'll be working on for 2.x).

@mattab
Copy link
Member Author

mattab commented Aug 13, 2013

Not as important now that we will have ability to easily theme piwik #3942

@mattab
Copy link
Member Author

mattab commented Apr 14, 2014

reduced scope of ticket

Fixed in: #260

If you have more ideas on how we can make Piwik more usable and looking simpler, please let us know!

Your feedback is welcome

@mattab mattab added this to the 2.x - The Great Piwik 2.x Backlog milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Critical Indicates the severity of an issue is very critical and the issue has a very high priority. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

5 participants