We have been tasked with identifying and understanding the purpose of subgraphs for the current stage of the curation program. I lack some technical experience required to do this in a meaningful way, however, even those with technical experience have to dig through the subgraph code in order to better understand the nature and purpose of the subgraph. This is inefficient, especially when projects might have multiple subgraphs created for different purposes.
A more efficient process would be for the creator of the subgraph to specify the intent or purpose of the subgraph. If they include a summary detailing what the subgraph is meant to query, or what the subgraph is useful for, it could encourage adoption and increase usage of that subgraph, and also help endusers more efficiently find existing subgraphs that are useful and they might want to consume. The summary could be included on the information page when you click on a subgraph (the page that provides a tagline of the Github link, and the IPFS info).
We have been tasked with identifying and understanding the purpose of subgraphs for the current stage of the curation program. I lack some technical experience required to do this in a meaningful way, however, even those with technical experience have to dig through the subgraph code in order to better understand the nature and purpose of the subgraph. This is inefficient, especially when projects might have multiple subgraphs created for different purposes.
A more efficient process would be for the creator of the subgraph to specify the intent or purpose of the subgraph. If they include a summary detailing what the subgraph is meant to query, or what the subgraph is useful for, it could encourage adoption and increase usage of that subgraph, and also help endusers more efficiently find existing subgraphs that are useful and they might want to consume. The summary could be included on the information page when you click on a subgraph (the page that provides a tagline of the Github link, and the IPFS info).