We need to explore the feasibility of adopting webpack5 modularizaton within Taranta. Webpack5, and its notion of federated modules, provides ways to configure and separately deploy "pieces" of a javascript web app. With proper modularization, Taranta could become an application based on a pluggable architecture. See some details on "federated modules" in https://confluence.skatelescope.org/display/SE/Micro-frontend+Modular+Federation.

We might want to create 2+ modules that replicate some of the functionalities of Taranta.

Questions to be answered:

1. how much work is needed to specify different kinds of modules. Examples:
   1. a module for the taranta platform (dashboard editor+ dashboard runner + Devices), for eg difficulties in specifying which external libraries like plotly are involved
   2. Another module that includes a single widget (any one would do)
   3. A third module with another widget
   4. A fourth module with a dashboard with 1-2 widgets in it
2. how easily new versions of the second/third/fourth module can be developed and deployed?

This is timeboxed.

NOTE: this is an outcome of the Taranta meeting held last Saturday (June 4 2022).