A command-line tool written in Go that generates API documentation from GraphQL schemas or endpoints.
gqldoc is a command-line tool that generates API documentation from GraphQL schemas or endpoints. It automates the creation of documentation by introspecting GraphQL schemas, either from local files or live endpoints, and outputs structured documentation files. This solves the problem of manually maintaining API docs for GraphQL services.
GraphQL API developers and teams who need to generate and maintain up-to-date documentation for their GraphQL schemas, especially those working with multiple schema files or automated CI/CD pipelines.
Developers choose gqldoc for its simplicity, direct integration with GraphQL introspection, and automation capabilities via GitHub Actions, reducing manual documentation overhead and ensuring docs stay synchronized with schema changes.
The easiest way to make API documents for GraphQL
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates documentation directly from GraphQL endpoints with headers and custom queries, as shown in the command example using -e and --header flags for authentication.
Handles multiple schema files via repeated -s flags or glob patterns, ideal for complex projects with fragmented schemas, per the README examples.
Includes pre-built GitHub Actions for automatic documentation updates on schema changes, reducing manual maintenance effort.
Automatically creates a README.md with a table of contents in the output directory, improving document navigation and structure.
Missing key GraphQL features like subscriptions and directive support, as admitted in the TODO list, limiting functionality for advanced APIs.
Lacks custom template support, so users cannot tailor documentation styling or format, which may not suit brand-specific needs.
Focused on markdown output with uncertain HTML rendering support, making it less suitable for teams requiring web-based docs.
Labeled as alpha in the README, indicating potential instability, breaking changes, or incomplete documentation for production use.