Please outline and describe your proposal. Share a short paragraph about your proposal. This is your moment to share your idea!
This project aims to automate the creation of subgraph documentation for all projects built on The Graph. Our initial MVP is a single page application that takes the contents of a schema.graphql file as input and returns Markdown-based subgraph documentation for schema entities and sample queries. The next phase of the project aims to extend graph-cli functionality so that it automatically prepares documentation for any subgraph built with the utility. Documentation is a huge time investment when completed entirely manually. This tool will save time for developers and make their subgraphs easier to query.
Goals & Milestones. Please include the overarching goals, milestones and targeted measurable KPIs. Let us know what your vision of success is and please include as much detail as possible. Include timelines, what stage the project is currently in (eg. pre-development, demo, launched).
Examples: Month 1 - Building 4 Subgraphs; Month 2 - Translating 6 documents; etc...
Month 1
Complete prototype single page application back end (Python)
Build out QA testing automation for back end
Investigate how to translate back end functionality from Python to TypeScript
Month 2
Complete single page application front end
Build out QA testing automation for front end
Deploy phase 1 MVP (Python)
Month 3
Begin prototype CLI utility (TypeScript)
Begin prototype QA testing automation
Investigate extending graph-cli utility
Month 4
Complete prototype CLI utility and QA testing automation (TypeScript)
Start integrating functionality into graph-cli
Month 5
Complete integration into graph-cli
Month 6 and beyond
Ongoing maintenance
What sort of impact will your project have on The Graph? What value will your project produce?
Our project will dramatically reduce the amount of time subgraph documentation teams spend on tedious Markdown table formatting and error-prone copy + paste operations. Likewise, subgraph consumers will be delighted that schema entity and sample query documentation is always available (so long as development teams share it publicly).
We would like to learn more about why you're interested in contributing to The Graph. What can you share with us?
We are a group of Graph AdvocatesDAO members who met during Graph Day 2022. Our shared interests in creative problem solving, automation, and improving the protocol are complemented by our uniquely diverse backgrounds. This project was born out of mild frustration from manual documentation and the desire to streamline the process for ourselves and other subgraph developers.
How much funding are you looking for? Please only include funding that would be required to create your project. Although all grants are paid in GRT, please quote your funding in USD.
schema.graphql
file as input and returns Markdown-based subgraph documentation for schema entities and sample queries. The next phase of the project aims to extendgraph-cli
functionality so that it automatically prepares documentation for any subgraph built with the utility. Documentation is a huge time investment when completed entirely manually. This tool will save time for developers and make their subgraphs easier to query.graph-cli
utilitygraph-cli
graph-cli
copy + paste
operations. Likewise, subgraph consumers will be delighted that schema entity and sample query documentation is always available (so long as development teams share it publicly).