Open friep opened 11 months ago
I'm wondering what the strategy should be. I generally see two options.
I think 1. has the advantage of using familiar libraries that are very much build for analytics. But we'd have to think a little harder about the build process and how to potentially document it if it stretches across another repository.
The second approach would be a lot simpler wrt. the build process and documentation but I'm not sure how much implementation work needs to be done. There are probably node packages we can use but I'm not familiar with them yet. This might be feasible if we have a fairly stable set of KPIs etc., but if that's still a little more exploratory the js implementation efforts might be unreasonable high.
I vote for the second option and would suggest ECharts for visualizations. I have used this library recently and like its ease of use while still being very customizable
For now, add basic stats to top of projects db. Clarify that only some of CorrelAids projects are displayed
we could include some reporting on our (impact measurement) metrics, e.g. using the project data see the report
projects.qmd
here: https://github.com/CorrelAid/projects/tree/main/_reportspossible location: new page
impact
under about