New top level schema: Art Asset

[RustoMCSpit]

I think Skins should remain classified as presets but I want each skins' assets to be classified under assets.

Furthermore, I want skins to be dissected for every asset they have so that we can make a huge library for plugin developers to take from like as seen in the asset site https://uiverse.io

Also, I want the default plugin skins dissected to.

Files needed for asset:

• a file or a file url of the asset
• a project file for the software used to make the asset
• an image to display the asset

Metadata needed for each asset:

• what type of asset it is (fader, toggle, etc.)
• what software was used to make it
  • version of software
• file type (archive, installer)
• file contains ( .png, .svg, etc.)
• what plugin it was originally designed for
• license
• author
• aesthetic tags
• date
• version
• description
• file size
• checksum
• file url
• file bundle? CMS: Adding and downloading individual files to bundles with their own metadata #138

I have been asking around a load of repos and I think there is a demand for something like this. The end product would work be an open source version of this https://uimother.com/collections/gui-kits

[kmturley]

Interesting idea. Who is the audience for these downloads?

The reason I ask is that the Open Audio Stack schema so far is targeted at Musicians/Producers. Plugins, Presets and Projects are all downloads to help music-making.

Skins such as: https://surge-synthesizer.github.io/skin-library/ would fall under customization of DAW and plugins which would be for musicians

UI libraries/kits such as https://uimother.com/collections/gui-kits/products/open-type appear to be more for plugin developers. Who can purchase a UI component library to make plugins with. These are beautiful BTW!

With StudioRack I tried to provide tools for plugin developers such as plugin templates and GitHub actions, but struggled to gain adoption. I think a collection of UI libraries and kits is a little bit out-of-scope for OAS at this time, as it is not the same audience as Plugins/Presets/Projects.

I do think that Skins are in-scope, and we should think about how they are defined in the schema, either as Presets or something else. I've not tried to customize skins before, so would need to try them out to see how they work.

[RustoMCSpit]

Interesting idea. Who is the audience for these downloads?

Plugin developers

I think a collection of UI libraries and kits is a little bit out-of-scope for OAS at this time

It is but only in a target audience sense, all the functionality is already built.