Yes.

Indeed, GraphQL for Content Fragments is just a part of full headless content. In fact I talked about this very point in my session at the AEM Skill Exchange (recording is available). In a nutshell, for digital assets including image metadata you could use the HTTP Assets API for headless access. But we've also built an extension of the GraphQL interface to include digital assets, Experience Fragments and content pages in a that same GraphQL endpoint. One request, all types of content returned. In summary: I agree with you - but it's in fact available!

@@matthiaswermund88 Hello Matthias, thank you for your gracious response. I know about the assets api and we use it for bulk uploads/changes on DAM, but we didn't want to mix REST with GraphQL. The problem we're having now is we need to have image properties like title and description available on imageRef's at a query. We need it for properly-made alt tags - especially for images with product codes as names. What you describe sounds great. Is it a publicly available video? If so, can you share the link here? If not, can you give us the title of the video and we can follow up with our technical account manager at Adobe to access it.

​@@Edirneli YT is stripping out the link unfortunately. Google for "aem skill exchange experience maker spotlight", it should be the first hit on Adobe Experience League. The relevant part starts around 21m35s. One note: The single, universal GraphQL endpoint is a custom extension that we've built on top of standard AEM. You could apply the same approach in your implementation, or you could use a GraphQL Mesh to translate/combine HTTP Assets into a GraphQL endpoint. Your consuming client can then rely purely on GraphQL - I talked about that approach in the session as well.