Dataverse marketplace and modularity

This is a follow up from last weeks front-end meeting where I presented a small example of how plugins could be integrated within an SPA. You can re-watch it on DataverseTV and inspect the code here.

According to @GPortas the addition of a marketplace and plugin-support is more of a long-term goal than something that should be implemented in this phase. Hence, this issue is set as a reminder and collection of ideas how we can conceptualize this even further.

I am happy to further investigate this and it would be awesome to collect ideas within this issue. Here are my previous thoughts condensed into some bullet points:

• Marketplace for community and Dataverse plugins (+ metadatablocks?)
• Plugins could modify the Dataverse UI and add extra buttons/tabs (Small utilities such as an ORCID Finder)
• Plugins could transfer data to another web-app (such as a Review Tool)
• Dedicated Plugin-Registry from which users can choose and transfer to the "Plugin-Store"-State

Start by reviewing the linked DataverseTV presentation and the CodeSandbox plugin-store example. Compare the marketplace, plugin-registry, UI extension, and data-transfer ideas, then clarify a concrete scope and acceptance criteria; this issue currently defines no implementation target or completion condition.