Move assets and content outside the osparc-simcore repository (except defaults)

[mrnicegyu11]

All product-specific assets and content (images, stylings, templates) should not be placed in the osparc-simcore repo but live in a different place (to be devised).

Ideally, content should be served via some agnostic service (cdn.osparc.io)

[pcrespov]

• PROS 👍: Placing "design" assets outside of the code repository will decouple code development and design workflows nicely! Here some advantages I see:
  • The design team can do any changes/improvements independently of the dev team.
  • The design team can release new designs to any of the available deploys independently of the ops team.
  • It critically reduce the time to production of new designs/themes since this workflow is independent from the workflow that the code base is required to follow (which is more time consuming and strict).
  • keeps osparc-simcore repo size in check (binaries accumulated in time will increase the repo size and tend unnecessarily degrade git performance)
  • the development of product design assets can be done in private repos
• CONS 👎 :
  • Requires some conventions/agreement (e.g. naming, file formats, ...) between the front-end code development and design team
  • Requires a release/versioning workflow (to match assets with deploys). This could be achieved by using one analogous to others already in place as osparc-simcore repo, services, APIs, ops configs, etc