From Requirement to Production
This walkthrough covers the core Hub flow: start from a UI requirement, design the query your consumer needs, propose the schema change, and ship it.Before you start, create or import a graph. The HR platform starter template works well for following along. If you already have a graph, see Explore Your Graph to orient before making changes.
1. Create a branch
Open the branch dropdown in the header and fork from main. Main stays read only, all changes happen on your branch.2. Start from a requirement
Drop a UI mockup onto the canvas. Highlight what needs data, and Hub creates a connected Operation Builder for each one.3. Build the dream query
In the Operation Builder, pick the operation type (query, mutation, subscription) you need. Select fields from the explorer, and use + to create any types or fields that don’t exist.4. Assign ownership
New fields need to live somewhere. Open the subgraph menu on any unassigned field and use Assign to to place it in the right service.5. Open a proposal
Go to the Proposal tab and click Create Proposal. If available, select collections for impact analysis — Hub runs schema checks, flags breaking changes, and displays the complexity impact.Proposals require a graph connected to a schema registry.
6. Review, discuss, ship
Review the operations changed and complexity metrics. Start discussion threads on any type or field. Once all of the threads are resolved, approve the proposal, then merge. With GitHub connected, merging moves draft PRs to ready for review and syncs your schema files automatically.What else can you do with Hub?
Guides
Design queries from UI requirements, make safe schema changes, enable governance
Concepts
Dream queries, fission, branches, and governance