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

Coalesce pageview/visitors graph bars #119

Closed
t3hmrman opened this Issue Sep 5, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@t3hmrman
Copy link

t3hmrman commented Sep 5, 2018

I'm not 100% sure if this would be a UI improvement, but it would certainly give you more space to show more data -- I think you can reasonable make the two graph bars that appear for every time period now into one graph-bar.

If I'm understanding the metrics correctly, 1 visitor implies at least 1 page view, so one bar will always be bigger than the other -- if you laid them on top of each other I think you could impart the information you want (how much searching around/other pages were visited versus people who actually came to the site) and save some space.

Here's a mock:
fathom-graph-mock

@dannyvankooten

This comment has been minimized.

Copy link
Collaborator

dannyvankooten commented Sep 6, 2018

Hey @t3hmrman,

@pjrvs and I agree - in fact this is how it used to be before the redesign but somehow we did not re-implement this. We will now though!

@t3hmrman

This comment has been minimized.

Copy link
Author

t3hmrman commented Sep 6, 2018

Hey @dannyvankooten glad it seemed like a reasonable thing to do! I actually didn't know of Fathom before the redesign, which is why I didn't see you guys had already done it once!

This is somewhat unrelated but before I make a different issue I wanted to float the idea -- what about a super loose JSON object/blog based user-preferences store? I present this as a general solution to my actual problem which is that for the main page I actually most often want to see the day's visits (not the week's). SQLite has some JSON support but requiring that extension is present might be an unacceptable blow to setup difficulty/stability in practice. Something simliar could be relatively easily implemented with a generic k/v user_preferences table as well, with every value being a string-marshalled JSON value.

If that sounds at all desirable/something you guys haven't talked about yet, I can definitely make an issue for it.

Also, I promise I'll find some time to contribute some code instead of just making issues :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.