https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/29998 introduced a rake task that generates GraphQL documentation based on our schema. Some additional steps are needed in order to make the documentation reliable, useful and automated. * Use a rubocop rule to always add descriptions to GraphQL resources on GitLab schema * Use alert bot to make sure changes made directly into the generated docs are not merged * Use alert bot to remind when documentation is outdated * It should be simple to change the templates and add more resources to our generator but we should have some docs to help other developers do it. * Add more GraphQL resources to templates like mutations, queries, interfaces, deprecation messages, alerts etc. * Allow to use Haml partials template files to be included, right now we have one single page for Graphql objects. We should have one page for each resource type. * Generate the documentation automatically when a change is made on GraphQL schema. * Keep GraphQL [developer documentation](https://docs.gitlab.com/ee/development/api_graphql_styleguide.html) up-to-date with how the GraphQL docs system works.