Hygraph CMS: schemas, review and content APIs

Evaluate Hygraph for reusable retail content. Check schemas, editorial stages, preview and API delivery before connecting guides to the storefront.

Hygraph CMS fits reusable retail advice when your team wants structured content delivered through GraphQL and can build the storefront integration around it. Its draft and published stages separate editing from delivery. Your implementation must carry that separation through preview, page caching and any customer-answer source that consumes the content.

Model advice separately from product transactions

Use Hygraph for the advice your editors own, with product identifiers connecting that advice to the commerce system. A buying guide can reference a policy record and several products without copying live stock into its text.

Hygraph’s content models define fields such as rich text, Markdown and JSON. Fields can be required or localised. References connect entries across models, while components group reusable fields within content.

For a hypothetical outdoor furniture guide, create a Guide record with buying advice and product identifiers. Reference one CarePolicy record from each relevant guide. Editors then change the care advice once, while the storefront resolves the referenced products against the commerce catalogue.

Plan reference direction and whether each field accepts one entry or several before implementation. Hygraph’s reference documentation warns that changing these choices can require rebuilding the field. Reuse needs a content model that matches the publishing job, not a single large text field containing every policy.

Hygraph also supports remote data. Its remote field instructions describe connecting REST data through a configured Remote Source. The same page states that GraphQL remote fields are not supported in Hygraph Studio. Assess the connection type in the interface your team will use.

An external connection does not decide who owns price or stock, nor whether the consumer can show the response to customers. Keep that ownership with the commerce system and define handling for unavailable products and stale responses.

Hygraph is the current name of the product previously called GraphCMS. For an inherited setup, inspect its endpoint and integration code before applying older GraphCMS instructions.

Review the editorial stages

Hygraph has two system content stages, DRAFT and PUBLISHED. Saving an edit changes the draft, while publishing promotes the content to the published stage. A record can therefore have newer draft wording beside an older published version.

Use a single care-policy change to assess the workflow. In this hypothetical example, an editor corrects which cleaning products are suitable for a furniture finish. Save the revised policy as a draft. The reviewer must see that draft with a guide that references it, while public delivery continues to use the earlier approved wording.

Roles combine content permissions with permissions for project management. Content permissions can distinguish editing from publishing. Test the editor’s ability to save the policy and their inability to publish it when approval is required. Use the intended account role for this check.

Locales belong to configured fields within an entry, rather than requiring a separate copy of every record. Hygraph’s localisation guide explains this field-level model. Include each customer-facing locale in the policy review and define what happens when a translation is missing.

Treat media as content that needs approval too. The Asset model holds files and can have added fields for alt text or captions. Replace an image in the trial policy change and inspect the guide’s published output, including its alternative text.

Deliver the reviewed content version

Hygraph generates GraphQL access from the schema. Each environment has its own endpoint, with read/write and high-performance delivery options. Set the environment and content stage deliberately in every consumer.

For preview, use a restricted credential that can read drafts. Keep that credential on the server and protect the preview route. The storefront tutorial separates public published-content delivery from draft access through a Permanent Auth Token.

Keep public delivery limited to approved models and stages. Hygraph’s content permissions can restrict access by model, locale and stage. A working preview query does not prove that a signed-out visitor receives the published policy.

Trace the care-policy change through both consumers:

  1. Publish the approved policy and any changed dependencies required by the guide.
  2. Run the storefront’s configured rebuild or cache refresh. Load the guide outside preview and confirm the approved wording appears.
  3. Refresh the customer-answer source through its own ingestion process. Ask a question about the cleaning restriction and inspect the source version used.
  4. Withdraw or replace the policy in the test setup and confirm that both consumers stop serving the superseded advice.

Publishing in Hygraph changes the content stage. Your integration owns the later rebuild, cache expiry or ingestion work. If the page updates but customer answers stay stale, inspect that second consumer’s refresh and removal process.

Check service limits and an exit route

Size the plan against your workload and approval requirements. Hygraph’s plan comparison lists two stages on Hobby and Growth, with additional stages and custom roles on Enterprise. A review stage and restricted publishing role can therefore change the plan you need.

The comparison also lists one environment on Hobby and two on Growth. Count content entries, media and locales before choosing. Assets count towards the entry limit, and API usage includes traffic from the systems consuming your content. Budget for a storefront build, repeated preview queries and knowledge-source refreshes as separate workloads.

Use environments to test schema changes separately. Cloned asset URLs can change, so inspect references held outside Hygraph too. An environment for development has a different purpose from a content stage used for editorial approval.

Implementation work includes the frontend, permission setup and consumer refresh logic. Assign an owner to failed refreshes and plan-limit alerts before the publication becomes a customer-answer source.

For an exit route, Hygraph documents fetching content as JSON through its Content API, with pagination for larger collections. Export every required model and locale, preserving identifiers and relationships. Keep copies of the media files as well as their URLs.

The schema-as-code feature exports the project schema through the Management API. A schema export is separate from a content export. Rebuild a sample guide with its referenced policy outside the original project before relying on your exit plan. Choose Hygraph when that structured reuse and controlled delivery justify the integration your team must maintain.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup