create an assets schema (assets.json) with queries and resolvers for assets as data

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

Add support for automatically creating an "assets" graph of everything in the assets/ directory, which could really be useful and helpful for things like photo galleries.

Details

Currently as the assets/ folder is automatically known and copied by Greenwood on every build, it might be nice to expose any files as data, just like we do for content. As documented in #570 , this might help ease the burdened, at least at the workspace level, of plugins needing to have to bring too much to the table.

In other words, by using conventions in an assets/ directory, e.g.

src/
   assets/
     gallery1/
       photo1.png
       photo2.png
     gallery2/
       photo1.png
       photo2.png
       photo3.png

You could create whole photo galleries or other multi-media pages and content and access it all with GraphQL. Or using REST, as we would probably also want to generate an assets.json in the CLI, just like we do for the graph.