Determine approach for maintaining Design assets, and how Designers contribute to the project

[PaulaPaul]

Problem/Concern

Theme Builder design assets were created and maintained in Figma, under a license outside of the control of FINOS. Now that the project has been donated to FINOS we would like to have a sustainable way for design assets to stay associated with the project in the FINOS GitHub (for example, links to design assets in another organization's Figma may change ownership, and can make it challenging to collaborate on and modify designs).

Proposed Solution

There are multiple potential solutions to creating a FINOS repository for design artifacts that can be a long term home for the Theme Builder project. The goal of this issue is to discuss alternatives with the project team and document the approach for contributing and maintaining design assets associated with Theme Builder.

Along the way we may uncover and share best practices for incorporating design assets in open source projects!

Alternatives

• FINOS Sponsored Figma subscription: Pro subscription supporting up to four designers, which can be managed by the core contributors to Theme Builder
• Penpot is open source, and recently added a capability to import Figma designs. This is related to #665
• Other alternatives? Also, this discussion will help us with 'end to end accessibility' and how to deliver that

For any alternative, we have been asked to summarize the approach and costs (if any) for FINOS consideration, ideally with the idea that this approach may apply to other open source projects or open source design efforts in general.