Suggestions for new tab

[StanFromIreland]

---

📚 Documentation preview 📚: https://pydocs-translation-dashboard--64.org.readthedocs.build/

---

📊 Dashboard preview 📊: https://python-docs-translations.github.io/dashboard/64/merge/

[StanFromIreland]

Something needs to be done to speed up the horrendous time it takes to generate metadata. Over 30 minutes!

[m-aciek]

Something needs to be done to speed up the horrendous time it takes to generate metadata. Over 30 minutes!

Maybe a metadata is not appropriate name for this data. We actually build the HTML documentation for every language to see the builds warnings.

[StanFromIreland]

I discovered that, it also uses a lot of bandwith. Is there no way to fetch them from the repos runs?

[m-aciek]

I discovered that, it also uses a lot of bandwith. Is there no way to fetch them from the repos runs?

It would require a specific repos configuration, something we don't have the control over.

[StanFromIreland]

Maybe Julien could help as I presume he has that power?

As for this PR, what do you think?

[StanFromIreland]

@m-aciek What do you think? The build will fail because of Plausible and fixing that here and then merging in to build-warnings-new-tab may introduce complications.

[m-aciek]

Looks good besides the overflow issue. By the way I am thinking now about creating three views: main | details | quality or similar, to have details for more columns that are fast to present/get, and quality for long-time-generated data.

[m-aciek]

Maybe Julien could help as I presume he has that power?

I don't think that's a matter of power. Pragmatically, it's easier to have it calculated in a central place, versus every translation configuring it on their own. Though I would be open to kind of standarise it, but then we would need to accept that some of languages will probably not deliver the gh checks.