Why you need static documentation for your GraphQL API

This page summarizes the projects mentioned and recommended in the original post on dev.to

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • graphiql

    GraphiQL & the GraphQL LSP Reference Ecosystem for building browser & IDE tools.

  • By dynamic documentation, I mean a documentation that interacts with your API directly. GraphiQL is probably the most popular tool out-there to do this.

  • swagger-ui

    Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.

  • If you used REST before, there are many great tools that can do this, like Swagger, which generates a schema (swagger.json) out of your endpoints. This schema can then be used to generate dynamic or static documentation.

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo
  • magidoc

    Autogenerate customizable static GraphQL API documentation

  • Given the circumstances, I personally took the initiative to create on a new tool: A tool that would allow for extensive customization, while also being simple. That's how Magidoc was born. With this project, I aim to provide various templates and starters that are easily customizable.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts