Potential problems with adding entire subdomain/domain as designation for where package is hosted.

[afragen]

Currently the plugin card and the modal both indicate the domain for the package. In Git Updater's case, it is currently registered via fair.git-updater.com. I can surely see where other devs are experimenting and will later change the registration to a new site.

If users were to go to these sites they might not find anything related to the package as the site only serves the purpose of being the registrar.

Would it be better to use the domain and not a subdomain?

[Ipstenu]

Question: Would changing the domain from fair.git-updater.com to api.git-updater.com cause an issue?

Maybe. We need to look into this.

1. Who is this block of info for?
2. Is it helpful to end users or should they only know the repo name?

[jazzsequence]

Could there be controls for how the FAIR repository display (headers/filters/whatever)?
I feel like broadly it's helpful to know that it's a) coming from FAIR and b) where it's coming from, but I don't know that fair.git-updater.com is necessarily as helpful (particularly if there's no site on that endpoint).

[Ipstenu]

All I can think is that "FAIR Repository" itself should be a link or the name?

Plugin available via the FAIR repository [AspireCloud]