Add a statistics page

[Zethson]

We keep having to generate statistics for our talks and it would be awesome to have the growth of our community publicly displayed. The role model is of course https://nf-co.re/stats .

Ideally, we'd find a way to have live updates but this would be much harder given that we only have a static site. I currently think that we should have a CI job that uploads a JSON file of the stats somewhere just like we upload the scverse-tutorial Artifacts (see https://github.com/scverse/scverse-tutorials/actions/runs/14186216329/job/39741895697 for a run). Then we download such an Artifact on our website and display it. It would be an open question whether we cache it or ask for the stats on request if the JSON file is small.

This is just a rough description but we can flesh it out with a proposal or just start small and iterate.

[maltekuehl]

Implemented the data collection and deployment CI/CD in: https://github.com/complextissue/scverse-stats

Data available at: https://scverse-stats.complextissue.com/stats.json

Happy to move it to the scverse org and to adapt to any specific charts that should be shown. Do we have Cloudflare available or should it use GitHub pages? And can DNS be configured, too?

[flying-sheep]

scverse.org is GitHub pages. I think @ivirshup and @Zethson have access to DNS. Could you please put the credentials into 1password?

[Zethson]

Not sure whether it's me. @gtca can you maybe help here, please?

[flying-sheep]

Ah, sorry, yeah. You have access to CIRun, and @ivirshup and @gtca to DNS.

We need to eliminate all these personal-access-only things!

[maltekuehl]

Discussed with @Zethson, perspectively, it would make sense to combine with scverse-tutorials to have a single source that generates dynamic data for the website. While that CI is broken however and to move things along, I will move the existing repo to the scverse org and just deploy through GitHub pages alter this week, so no need for any DNS right now.

But that is only 1/2 of this issue, two questions remain:

• Should we show this on a dedicated stats page? Or integrate into the landing page (something along these lines)?
• Is there a way to access Zulip stats via API as well, and if yes, do we need a token from a Zulip admin?

[Zethson]

Should we show this on a dedicated stats page? Or integrate into the landing page (something along these lines)?

I'd probably make it a dedicated page like https://nf-co.re/stats

Is there a way to access Zulip stats via API as well, and if yes, do we need a token from a Zulip admin?

https://zulip.com/api/get-subscribers

I'd say it's possible. I am a zulip admin and can probably help with tokens.

[maltekuehl]

My API key as a member was sufficient to get all users, have it working locally and will update the repo soon. Apparently, Zulip is now at more than 1000 members!

[grst]

Just happend to get involved in a discussion on the new nf-core stats page they are building. Their old solution was falling apart and they now switched to these framework for gathering their statistics + building the stats page:

• dlt for data loading. Data from various sources is stored in a Motherduck instance (it works with many backends)
• evidence (website | docs) for building the dashboard.

[grst]

The stats page exists: https://scverse.org/stats/

It can always be extended, but we should link it from the main website.

[maltekuehl]

The frontend is not integrated with the main one, though. If somebody tried to tackle this, would likely only take an hour to vibe-integrate it into this repo, as the data source already has all the information (https://scverse.org/stats/stats.json and https://scverse.org/stats/contributors.json).

[Zethson]

@maltekuehl I'll have a shot at this.