We welcome contributions to GraphQL Editor of any kind including documentation, themes, organization, tutorials, blog posts, bug reports, issues, feature requests, feature implementations, pull requests, answering questions on the forum, helping to manage issues, etc.
Changes to the codebase and related documentation, e.g. for a new feature, should still use a single pull request.
We have an Discord Channel where users and developers can ask questions. Please don't use the GitHub issue tracker to ask questions.
If you believe you have found a defect in GraphQL Editor or its documentation, use the GitHub issue tracker to report the problem to the maintainers. If you're not sure if it's a bug or not, start by asking in the discussion forum.
GraphQL Editor is still looking for its direction so remember functionality has to:
- repair existing bugs
- introduce new feature requests
Bug fixes are, of course, always welcome.
If you are interested in helping with the project, we will help you with your contribution. GraphQL Editor is a little bit complicated project touching many technologies feel free to ask us for help on Discord Channel
Because we want to create the best possible product for our users and the best contribution experience for our developers, we have a set of guidelines which ensure that all contributions are acceptable. The guidelines are not intended as a filter or barrier to participation. If you are unfamiliar with the contribution process, our team will help you and teach you how to bring your contribution in accordance with the guidelines.