-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Feature] Traffic map across all of Juliahealth web artifacts #130
Comments
Hey @divital-coder, Thanks for writing this up and sharing some ideas for what we could track! Here are some follow-up thoughts I have:
This sounds great! I would say to start with, Makie.jl plots would be sufficient -- we don't need anything too fancy to get things going. In my mind, I envision the following as an "analytics page":
In the future, maybe we could use some embedded things like Bonito.jl or StippleMakie.jl
In my opinion, I think the easiest place to get started would be to use GitHub.jl to pull some JuliaHealth GitHub metrics. What I could imagine we do here is the following process:
I imagine this blog post to be updated once per month automatically.
So I actually think this should be another page on the JuliaHealthBlog and not just a blog post. Like a separate page in the About Us or something where folks can click "statistics". Just some thoughts for now @divital-coder -- let me know what you think! Additionally, I realized this issue should actually be over in: https://github.com/JuliaHealth/JuliaHealthBlog I can migrate this issue over if needed. Thanks for spearheading this Div and let me know how I can support or share ideas! |
Thank you so much for jotting this down @TheCedarPrince |
A progressive embed within the fabric of the juliahealth official website interface to provide an analytics dashboard based on the traffic across various juliahealth artifacts on the internet, including but not limited to :
The embed will be progressive in nature, offering support for upstream sources down the road.
The text was updated successfully, but these errors were encountered: