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

[Feature] Traffic map across all of Juliahealth web artifacts #130

Open
divital-coder opened this issue Feb 10, 2025 · 2 comments
Open

[Feature] Traffic map across all of Juliahealth web artifacts #130

divital-coder opened this issue Feb 10, 2025 · 2 comments

Comments

@divital-coder
Copy link

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 :

  • Juliahealth meeting recordings on youtube
  • Juliahealth website
  • Juliahealth blogpost
  • Juliahealth mentions in official Julia Zulip, Forem and Slack
  • JuliaHealth Org github stats and stars across overall repos under the org.

The embed will be progressive in nature, offering support for upstream sources down the road.

@TheCedarPrince
Copy link
Member

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:

provide an analytics dashboard

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":

  • A single webpage of plots displaying various metrics (barplots, line plots, etc.) across different sections
  • Static tables showing relevant counts or curated lists (like "Top 5 most active packages")
  • Description within each section about the metrics or plots being shown

In the future, maybe we could use some embedded things like Bonito.jl or StippleMakie.jl

offering support for upstream sources down the road.

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:

  1. Create a pipeline for GitHub.jl to pull GitHub metrics (probably set-up a secret or authentication somewhere)
  2. Pull various monthly metrics such as:
    1. Stars across repos (across all repos and individually)
    2. Activity across repos (Commit frequency)
    3. Number of issues opened vs. closed
  3. Use DataFrames.jl and CSV.jl to process data metrics
  4. Create relevant GitHub plots using Makie.jl
  5. Write a literate Quarto blogpost that displays these plots
  6. Save the analysis data used somewhere to the repo and add links to the data at the end of the blogpost (for transparency)
  7. Write a GitHub Action that runs this analysis once a month and updates this blog post

I imagine this blog post to be updated once per month automatically.

juliahealth official website

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!

@divital-coder
Copy link
Author

Thank you so much for jotting this down @TheCedarPrince

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

2 participants