Editorial Endpoint Configuration
We are actively working to improve this documentation. The content you see here may be incomplete, subject to change, or may not fully reflect the current state of the feature. We appreciate your understanding as we continue to enhance our docs.
While the GCA primarily uses a "code as configuration" approach where developers define schema settings in Java, Brightspot also supports editorial creation and configuration of GCA endpoints entirely through the CMS user interface. This editorial approach enables non-developers to create and manage GraphQL endpoints, configure exposed content types and view models, enable mutations, and control access permissions without requiring code changes or deployments.
Editorial GCA endpoint configuration is ideal for scenarios where content administrators need to create API endpoints on-demand, when you want to delegate endpoint management to non-technical users, or when rapid iteration without code deployment is valuable. Through the Brightspot UI, users can configure all the same capabilities available in code-based endpoints including which content types to expose (equivalent to readonlyEntryClass), enabling mutations (equivalent to mutableEntryClass), adding view models and static methods, and configuring editorial features like preview and revisions. This document covers when to choose editorial versus code-based configuration, how to create and configure endpoints through the UI, and the full range of settings available with step-by-step instructions and screenshots.