Frequently Asked Questions

Product Components & Schema Design

What are the main components used in Hygraph's eCommerce tutorial?

The main components include Clothing, Shoes, Accessories, Decor, Product Variant, Related Products, Button, Call to Action, Product Grid, and Link. Each component is designed to modularize content and enable flexible schema modeling. For example, Product Variant allows editors to select relevant fields based on product type, while Related Products enables cross-linking between products. Note: These components are specific to the eCommerce tutorial and may not cover all use cases; consult documentation for broader schema options.

How does the Product Variant component work in Hygraph?

The Product Variant component contains a modular field that presents Clothing, Shoes, Accessories, or Decor based on the product type selected by the editor. This enables a single Product model to handle multiple product types, streamlining schema design and content entry. Note: The modular approach is best suited for stores with diverse product types; for highly specialized catalogs, custom models may be preferable.

What is the purpose of the Related Products component?

The Related Products component enables product pages to display other products a buyer might be interested in. It includes a read-only title field and a reference field that connects to other Product entries, allowing editors to add up to four related products per item. Note: The reference field is read/write, but the title is read-only to ensure consistency across instances.

Features & Capabilities

What are Hygraph's key features for content management?

Hygraph offers GraphQL-native architecture, content federation, rich editing capabilities, localization, scalability, speed-to-market, enhanced customer experience, enterprise-grade security and compliance, AI Assist for content generation and translation, and proven ROI through customer case studies. Note: Detailed limitations not publicly documented; ask sales for specifics on edge cases or advanced workflows.

Does Hygraph support APIs for integration?

Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs for content delivery and management. Developers can integrate Hygraph with any frontend or application. For technical details, see API documentation. Note: API limits and advanced usage scenarios may require consultation with support.

What integrations are available with Hygraph?

Hygraph integrates with Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. For a full list, visit Marketplace Apps. Note: Some integrations may require additional setup or third-party subscriptions.

Technical Requirements & Documentation

Where can I find technical documentation for Hygraph?

Comprehensive technical documentation and developer guides are available at Hygraph Docs. Resources include getting started guides, advanced tutorials, and onboarding overviews. Note: Documentation is updated regularly; check for the latest version before implementation.

How long does it take to implement Hygraph?

Implementation timelines vary by project complexity. Simple use cases can be set up within a few days using starter projects and templates. More complex implementations may take longer, but structured onboarding, documentation, and community support are available. See starter projects and onboarding overview. Note: Custom integrations or advanced workflows may extend setup time.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 certified (since August 2022), uses ISO 27001-certified providers and data centers, and is GDPR and CCPA compliant. Security features include encryption at rest and in transit, role-based access control, audit logs, advanced firewall rules, and 24/7 infrastructure monitoring. For more details, visit security features page. Note: Some compliance requirements may depend on regional hosting options; verify with sales for specific needs.

Performance & Scalability

How does Hygraph perform under high-traffic scenarios?

Hygraph's global CDN, region-based hosting, and Smart Edge Cache ensure fast and reliable content delivery. Case studies include Gamescom supporting 3.5 million simultaneous sessions and 60 million API operations in three days, and Telenor achieving under 100ms latency on millions of API calls. Note: Performance may vary based on region and integration complexity; consult technical documentation for optimization tips.

Use Cases & Customer Success

Who can benefit from using Hygraph?

Hygraph is suited for marketing and content teams, product managers, developers, and enterprise IT teams. Industries represented in case studies include technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media and entertainment (Gamescom), travel and hospitality (HolidayCheck), scientific publishing (GDCh), government (Statistics Finland), sports/events (DTM), and retail/e-commerce (Stobag). Note: Teams with highly specialized workflows may require custom schema design.

What business impact can customers expect from using Hygraph?

Customers report up to 50% reduction in maintenance costs, 3X faster time-to-market (Komax), 20% higher monetization on websites, and improved customer engagement by 15% (Samsung). Gamescom handled 3.5 million simultaneous sessions, and Dr. Oetker manages content for 40 countries from a single platform. Note: Actual results may vary based on implementation and industry; consult case studies for detailed outcomes.

Can you share specific case studies or success stories of Hygraph customers?

Yes. Samsung improved customer engagement by 15% (case study), Komax achieved 3x faster time-to-market (case study), Gamescom supported 3.5 million simultaneous sessions and 60 million API operations in three days (case study), Stobag increased online revenue share from 15% to 70% (case study), Dr. Oetker manages content for 40 countries (case study), Telenor achieved under 100ms latency (case study), and HolidayCheck eliminated developer bottlenecks (case study). Note: Results are specific to each customer; review full case studies for context.

Pain Points & Problem Solving

What problems does Hygraph solve for its customers?

Hygraph addresses dependency on developers, legacy tech stacks, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management challenges. For example, HolidayCheck eliminated developer bottlenecks, and Komax accelerated time-to-market. Note: Teams with highly specialized requirements may need custom solutions; consult sales for advanced scenarios.

Customer Proof & Industry Coverage

Who are some notable customers of Hygraph?

Named customers include Samsung, Coca-Cola, Epic Games, Telenor, Dr. Oetker, Komax, Gamescom, and Stobag. These organizations span industries such as technology, consumer goods, telecommunications, media, retail, and e-commerce. Note: Customer logos and case studies are available on the Hygraph website for further reference.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Hygraph
Docs

#Lesson 4.1 - Build components

In this lesson, you will build all components the project needs. These components must exist before you can attach them to models in Lesson 4.2.

The Related Products component enables product pages to display other products a buyer might be interested in. It contains a read-only title field and a reference field that connects to other Product entries.

Add Related Products component field
  1. In the Schema editor, click +Add next to Components.

  2. Provide the following information, and click Add Component to save:

    FieldInput
    Display NameRelated Products
    API IDRelatedProduct
    Plural API IDRelatedProducts
  3. Add the following fields to the Related Products component:

    Single line text - Title:

    FieldInput
    Display nameTitle
    Use as title fieldSelect checkbox
    Make field requiredSelect checkbox
    Set initial valueSelect checkbox, and enter Related Products in the initial value field
    Field visibilityRead only

    The read-only title with an initial value ensures every instance of this component displays the same heading without editors being able to change it.

    Reference - Products:

    FieldInput
    Reference typeAllow only one model to be referenced
    Model to referenceProduct
    Reference directionsOne-way reference
    Allow multiple Products per RelatedProductSelect checkbox
    Display nameProducts
    API IDproducts
    DescriptionAdd 4 related products here
    Field visibilityRead / Write
  4. Click Add to save.

Your Related Products component should look like this:

Related Products componentRelated Products component

#Product type components

The store sells four product types: clothing, shoes, accessories, and decor. Each type requires different fields. Rather than creating four separate Product models, you will use four components, one per product type, and nest them inside a modular Product Variant component. The content editor then presents only the fields relevant to the selected product type.

These four components use the enumerations created in Lesson 3.1.

#Clothing

  1. Click +Add next to Components.

  2. Provide the following information, and click Add Component to save:

    FieldInput
    Display NameClothing
    API IDClothing
    Plural API IDClothingItems
  3. Add the following fields:

    Enumeration - Size:

    FieldInput
    Display nameSize
    API IDAuto-completed. Leave as is.
    EnumerationClothes size
    Make field requiredSelect checkbox

    Enumeration - Color:

    FieldInput
    Display nameColor
    EnumerationWearable items color
    Make field requiredSelect checkbox

Your Clothing component should look like this:

Clothing componentClothing component

#Shoes

  1. Click +Add next to Components.

  2. Provide the following information, and click Add Component to save:

    FieldInput
    Display NameShoes
    API IDShoe
    Plural API IDShoes
  3. Add the following fields:

    Enumeration - Size:

    FieldInput
    Display nameSize
    EnumerationShoes size
    Make field requiredSelect checkbox

    Enumeration - Color:

    FieldInput
    Display nameColor
    EnumerationWearable items color
    Make field requiredSelect checkbox

Your Shoes component should look like this:

Shoes componentShoes component

#Accessories

  1. Click +Add next to Components.

  2. Provide the following information, and click Add Component to save:

    FieldInput
    Display NameAccessories
    API IDAccessory
    Plural API IDAccessories
  3. Add the following field:

    Enumeration - Color:

    FieldInput
    Display nameColor
    EnumerationWearable items color
    Make field requiredSelect checkbox

Your Accessories component should look like this:

Accessories componentAccessories component

#Decor

  1. Click +Add next to Components.

  2. Provide the following information, and click Add Component to save:

    FieldInput
    Display NameDecor
    API IDDecor
    Plural API IDDecorItems
  3. Add the following field:

    Enumeration - Color:

    FieldInput
    Display nameColor
    EnumerationDecor items color
    Make field requiredSelect checkbox

Your Decor component should look like this:

Decor componentDecor component

#Product Variant

The Product Variant component contains a modular component field that presents Clothing, Shoes, Accessories, or Decor based on the product type an editor selects. This is the component that makes a single Product model work for all four product types.

  1. Click +Add next to Components.

  2. Provide the following information, and click Add Component to save:

    FieldInput
    Display NameProduct Variant
    API IDProductVariant
    Plural API IDProductVariants
  3. Add the following field:

    Modular component - Product type:

    FieldInput
    Display nameProduct type
    API IDproductType
    DescriptionSelect the product type to reveal fields
    Select allowed componentsClothing, Shoes, Accessories, Decor
  4. Click Add to save.

Your Product Variant component should look like this:

Product Variant componentProduct Variant component

#Button

The Button component holds a text label and a URL. It is used inside the Call to Action component in the next step.

  1. Click +Add next to Components.

  2. Provide the following information, and click Add to save:

    FieldInput
    Display NameButton
    API IDButton
    Plural API IDButtons
  3. Add the following fields:

    Single line text - Text:

    FieldInput
    Display nameText
    Localize fieldSelect checkbox

    Slug - URL:

    FieldInput
    Display nameURL
    Match a specific patternSelect checkbox, then select URL from the dropdown
    Custom error messageInput value does not match the expected format.

Your Button component should look like this:

Button componentButton component

#Call to Action

The Call to Action component is used as a page section on Landing pages. It embeds the Button component created in the previous step.

  1. Click +Add next to Components.

  2. Provide the following information, and click Add Component to save:

    FieldInput
    Display NameCall to Action
    API IDCallToAction
    Plural API IDCallToActions
  3. Add the following fields:

    Single line text - Heading:

    FieldInput
    Display nameHeading
    Localize fieldSelect checkbox

    Rich Text - Body:

    FieldInput
    Display nameBody
    Localize fieldSelect checkbox

    Asset picker - Image:

    FieldInput
    Display nameImage

    Basic component - Button:

    FieldInput
    Display nameButton
    Select componentButton

Your Call to Action component should look like this:

CTA componentCTA component

#Product Grid

The Product Grid component is used as a page section on Landing pages. It displays a headline, a description, and a set of Product references.

  1. Click +Add next to Components.

  2. Provide the following information, and click Add Component to save:

    FieldInput
    Display NameProduct Grid
    API IDProductGrid
    Plural API IDProductGrids
  3. Add the following fields:

    Single line text - Headline:

    FieldInput
    Display nameHeadline
    Localize fieldSelect checkbox

    Rich Text - Description:

    FieldInput
    Display nameDescription

    Reference - Products:

    FieldInput
    Reference typeAllow only one model to be referenced
    Model to referenceProduct
    Reference directionsOne-way reference
    Allow multiple Products per ProductGridSelect checkbox
    Display nameProducts
    API IDproducts
    Field visibilityRead / Write

Your Product Grid component should look like this:

Product Grid componentProduct Grid component

The Link component is included in the cloned project. It already contains two fields: Display text and External URL. You need to add a Reference field to it that connects it to the Blog post, Landing page, and Product models. This reference field could not be included in the original clone because it references models that did not exist until lesson 1.2.

This is the same layered schema pattern seen in lesson 1.2. Models and components are built in layers because some connections can only be made after the things they connect exist.

  1. In the Schema editor, under the Components section, select the Link component from the left sidebar.

  2. From the right sidebar, add a Reference field with the following information:

    FieldInput
    Reference typeAllow multiple models to be referenced
    Model to referenceBlog post, Landing page, Product
    Reference directionsOne-way reference
    Relation cardinalityTo one
    Display namePage
    API IDpage
    Field visibilityRead / Write
  3. Click Add to save.

Your finished Link component should look like this:

Link componentLink component

#What's next

Lesson 4.2 - Add components to your models

Or, go to the Tutorial overview for the full lesson list.