Tobias Diez

> I noticed, in the meantime, that, on the page https://github.com/JabRef/jabref/wiki/Donations, the link to the imprint (https://www.jabref.org/impressum.html) leads to a 404 error. > > And, on https://www.jabref.org/, there is no...

Thanks @negotiamini! That looks already like a pretty good start. May I ask you to open a PR?

From Frédéric Darboux: https://ist.inrae.fr/wp-content/uploads/sites/21/2020/09/R%C3%A9sum%C3%A9-Choisir_logiciel_bibliographique_2020-09.pdf

Good overview: https://aut.ac.nz.libguides.com/managingreferences

I think this would have make sense for 4.3.1 5.0, but it's a bit late for this. Thus, I'll close this issue. We should have this in mind for the...

I agree there is potential for improvement. Since you went through the config process just now, could you expand on the explanation by editing the docs at https://github.com/JabRef/user-documentation/edit/main/en/finding-sorting-and-cleaning-entries/filelinks.md ?

Good suggestion. Could you prepare these changes by editing https://github.com/JabRef/user-documentation/blob/master/en/collect/jabref-browser-extension.md and open a PR? Thanks!

In the best case, we should add unit gui tests and use testfx's DebugUtil.captureScreenshot to automate this. Then it would be easy to always have updated screenshots.

I've configured everything on azures end, and added the deployment secret to github. The website is "live" at https://lively-ground-0d7c50410.azurestaticapps.net/ An example workflow can be found at https://docs.microsoft.com/en-us/azure/static-web-apps/build-configuration?tabs=github-actions#build-configuration

PRs and main are published to azure, but both cannot be sideloaded at the moment. Some comments how this may be done: https://github.com/JabRef/JabRef-Word-Addin/pull/216#pullrequestreview-794551189