dashboard architecture

[mikerspencer]

There seem to be two dashboards, but only a link to one. The weblate dashboard is better documented (info page), but is not the default dashboard from the repo link.

Project architecture

• what is the user journey for viewing the dashboards?
• which should load first?
• should these be the same dashboard? (they largely seem to be duplicated)

[hturner]

Thanks, I moved the comments on repo architecture to a separate issue to make these issues more manageable.

The two dashboards are based on different data sources: the main dashboard shows the status of translations in R-devel, the development version of R that will become the next major/minor release, while the Weblate dashboard shows the status of translations on Weblate, where most contributions to translations are made. The Weblate stats could change every day, where as the R-devel stats are expected to change once a quarter when a patch is generated from Weblate, though there could be other changes made via other means, e.g. directly by R Core developers.

I definitely think its useful to consider the user journey and whether the dashboard layout/visualisations could be improved accordingly. From the main dashboard, users might learn about the current coverage for different languages and which languages need work; while from the Weblate dashboard users might learn about how activity the different translation teams are at the moment. It might make more sense for the Weblate dashboard to focus on recent changes, e.g. over the past month/since the last patch made to R-Devel/since the last major/minor release of R.