# Home What is better than a plain old API? An interactive, visual one, that you can work on easily from your browser. With the new GraphQL Editor, this is now possible for every developer! ![Relation view in the Editor](https://2595489265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkU3PZk9D4XQW0UI1bP%2Fuploads%2FnVJFHI7MYjJsuB4tdbkD%2Fimage.png?alt=media\&token=1d7ab309-ad0c-4560-afea-3f5af49dd87a) ### Keep your schema in the cloud. Your GraphQL schema is available in the cloud for all your team members. You can play with a fake backend and attach GraphiQL or bind it to the real one. ### Build using blocks Keep building your schema while being type-safe at the same time! Use our visual editor to create your schema in a much faster and cleaner way. ### Deploy Deploy microservices in TypeScript/Javascript to our GraphQL Editor Shared cloud. ### Document Automatically generate markdown HTML documentation for your schema. {% hint style="info" %} You can also test the newest version of GraphQL Editor at {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guide.graphqleditor.com/graphql-editor/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.