Frequently Asked Questions

Getting Started & Implementation

What are the prerequisites for building a related content block in Hygraph?

To build a related content block in Hygraph, you need a Hygraph account and an existing project. You can create a new project, clone a basic project provided by Hygraph, clone the complete Page Sections Cookbook, or use your own existing project. For new users, the Getting Started Tutorial is recommended. Note: Plan limits may affect your ability to add recipes to your project.

How can I quickly start with a related content block component in Hygraph?

You can start by following the step-by-step guide to create the related content block component, or you can clone a prepared project from Hygraph that contains all the necessary schema elements. Options include cloning the basic project, the complete cookbook, or a project with only the basic models. These options allow you to skip manual schema creation and focus on configuration. For more, see the official recipe guide. Note: You may need to adjust the schema if using your own project.

How long does it take to implement Hygraph for a new project?

Implementation time varies by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Starter projects and structured onboarding can accelerate the process. Note: Complex integrations or custom workflows may require additional time. Source

Features & Capabilities

What is a related content block in Hygraph and what does it do?

A related content block in Hygraph is a reusable component that allows you to add a title, body, image, and references to other content entries (such as Author, Book, or Shop) within your content models. This enables you to display related content dynamically and maintain relationships between different types of content. Note: The related content block is customizable, but advanced use cases may require schema adjustments.

What schema elements are involved in creating a related content block?

To create a related content block, you define models (e.g., Author, Book, Shop), add fields (such as text, rich text, asset picker, location), and set up references between models. The related content block component itself includes fields for title, body, image, and a reference field that can link to multiple models. Note: Schema complexity increases with more models and references.

Does Hygraph support reusable components and references between content entries?

Yes, Hygraph supports reusable components and references. Components are predefined sets of fields that can be reused across models and content entries. References allow you to relate content entries, enabling dynamic linking and content reuse. For more, see the Components documentation and References documentation. Note: Overuse of references can increase schema complexity and query depth.

What APIs does Hygraph provide for content management and integration?

Hygraph offers several APIs: the GraphQL Content API for querying and manipulating content, the Management API for handling project structure, the Asset Upload API for uploading files, and the MCP Server API for AI assistant integration. Full details are in the API Reference documentation. Note: API rate limits and authentication requirements apply.

What integrations are available with Hygraph?

Hygraph integrates with a variety of platforms, including Digital Asset Management (DAM) systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting and deployment platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), and translation/localization tools (EasyTranslate). For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional configuration or third-party accounts.

What technical documentation is available for Hygraph users?

Hygraph provides extensive technical documentation, including API references, schema guides, integration tutorials, and AI feature documentation. Key resources include the API Reference, Components documentation, References documentation, and Getting Started guides. Note: Documentation is updated regularly; check for the latest versions.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international standards for information security and data protection. For more, see the Secure Features page. Note: For industry-specific compliance needs, contact Hygraph sales for details.

What security features are available in Hygraph?

Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies (custom origin policies, IP firewalls). All endpoints have SSL certificates. Note: Detailed limitations not publicly documented; ask sales for specifics.

Performance & Product Experience

How does Hygraph perform in terms of content delivery and API speed?

Hygraph's high-performance endpoints are optimized for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement. Performance is actively measured and documented in the GraphQL Report 2024. Note: Actual performance may vary based on project complexity and query structure.

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph for its intuitive interface, quick adaptability, and user-friendly setup. Both technical and non-technical users report that changes are reflected instantly on the front-end, and granular roles and permissions help prevent mistakes. For example, Sigurður G. (CTO) and Charissa K. (Senior CMS Specialist) highlight the platform's accessibility and clear setup. Note: Some advanced configurations may require technical expertise. Source

Use Cases & Business Impact

What problems does Hygraph solve for content teams and businesses?

Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy tech stacks, ensuring content consistency), financial challenges (lowering operational costs, accelerating speed-to-market, supporting scalability), and technical issues (simplifying schema evolution, integrating third-party systems, optimizing performance, and managing localization/assets). Note: Teams with highly specialized workflows may require custom development. Source

Who can benefit from using Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. It is used in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Note: Small teams with simple content needs may find traditional CMS platforms sufficient. Source

What business impact can customers expect from using Hygraph?

Customers can expect faster time-to-market (e.g., Komax achieved 3x faster launches), improved customer engagement (Samsung saw a 15% increase), cost reduction, enhanced content consistency, and scalability. Case studies also show a 20% increase in website monetization (AutoWeb) and successful multilingual scaling (Voi). Note: Results depend on implementation quality and organizational readiness. Source

What industries are represented in Hygraph's case studies?

Hygraph's case studies cover SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel and hospitality, food and beverage, eCommerce, agency, online gaming, events & conferences, government, consumer electronics, engineering, and construction. Note: Industry-specific requirements may require additional configuration. Source

Can you share specific customer success stories with Hygraph?

Yes. Samsung improved customer engagement by 15% with Hygraph. Komax achieved 3x faster time-to-market. AutoWeb increased website monetization by 20%. Voi scaled multilingual content across 12 countries and 10 languages. For more, see the Hygraph case studies page. Note: Outcomes may vary by use case and implementation.

Limitations & Considerations

What are the limitations or edge cases when using related content blocks in Hygraph?

While related content blocks are flexible, complex relationships or deeply nested references can increase schema complexity and may impact query performance. Advanced use cases may require custom schema adjustments or additional configuration. Note: Detailed limitations are not publicly documented; contact Hygraph support for guidance on advanced scenarios.

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#Related content block

#Overview

This guide shows how to build a related content block component containing a title, a body, an image, and a reference.

It will allow you to add related content blocks to your content entries.

Related content block componentRelated content block component

#Prerequisites

  • REQUIRED: You need to have a Hygraph account. If you don't have one, you can sign up here.
  • REQUIRED: You need to have a Hygraph project.
    • OPTION 1: Create a project. This is the way to go if you want to follow the entire tutorial for learning purposes.
    • OPTION 2: Clone the basic project. If you're already familiar with Hygraph and only want to follow the parts of the tutorial where you create the page sections, you can start here.
    • OPTION 3: Clone the entire cookbook. This is the way to go if you're curious about how the page sections are made but don't want to follow the step-by-step creation process. This project contains the entire Page Sections Cookbook so you can compare them, or look into what instances they contain.
    • OPTION 4: Use an existing project of yours. If you have a project already and want to add this page section to it, this is the way to go. In this case, you may need to adjust parts of the tutorial to your own project schema.

#Core concepts

In this guide, you'll work with a number of schema elements. Let's look into them:

  • References: References are relations between two or more content entries in your project. With references, you can reuse content entries by connecting them. Once the relation is configured, you can also use it to create related content from the content creation screen.

  • Component: a predefined set of fields that can be reused across models and content entries. You can think of a component as a flexible, reusable template: you define the fields that will be used inside a component once, and then fill them with different content every time you use it in a content entry.

  • Basic component field: a component is a special field type in your Hygraph schema that defines which components of which type can be used in a model. Component fields can be of basic or modular types. A basic component field can only have one component attached to it. You can limit the number of component instances to one, or allow multiple component instances to be added in the content entry.

#What you can do

This guide offers two paths:

  • Path 1: Use this guide to create a related content block component that you can use in your project.
  • Path 2: Clone one of the projects we created for you. You can clone a project that only contains the basic models so you can work on the page sections right away, or you can clone the project that contains the entire Page sections cookbook to compare the different section configurations without having to clone multiple projects.

#Clone project

#Clone the basic project

We have prepared a project that contains all the base schema elements you need to add to your page sections, in case you don't want to build them from scratch:

Clone this project

If you decide to clone this project, you can skip the base schema elements creation part of this tutorial, and start from this step.

#Clone the complete cookbook

We have prepared a project that contains the entire Page sections cookbook:

Clone this project

This cookbook contains all the recipes we have so far to create page sections, so you can compare the different banner configurations without having to clone multiple projects.

To find this particular recipe in the cookbook project, navigate to the schema and look for the "Related content block" component.

#Step-by-step guide

In this guide, we will create a related content block component. Before we can build this, we need to create other schema elements that will be a part of it.

We will divide this process in steps to make it more manageable:

  1. Create the referenced models: We will create 3 sample models - Author, Book, and Shop - to use in our internal links.
  2. Create the related content block component: We will create a related content block component that you can later add as component field to your models.

#1. Create the basic models

For this example, we'll go with the idea of an online bookshop that has real world subsidiaries, so we'll create 3 models:

  • Author
  • Book
  • Shop

#Author model

Author modelAuthor model

Let's start with the Author model. In the Schema builder, we'll click +Add next to Models, and use the following information:

FieldInput
Display NameAuthor
API IDAuthor
API ID PluralAuthors

We'll click Add model to save.

Our model has been created but it's empty. To create a simple model that will contain basic author information, we'll add the author name, bio, and image.

Let's start with the author name, as a Single line text field. We'll find it on the Add fields right sidebar, and click Add on the field card to add it.

We'll use the following information:

TabFieldInput
SettingsDisplay NameAuthor name
SettingsAPI IDauthorName
SettingsUse as title field checkboxLeave this checkbox selected

We'll click Add to save.

Next, we'll add a Rich text field, which will our author's bio. We'll select the Rich text field from the right sidebar and use the following information to create it:

TabFieldInput
SettingsDisplay NameAuthor bio
SettingsAPI IDauthorBio

We'll click Add to save.

Finally, we'll add an Asset picker field, which will be our author's image. We'll select the Asset picker field from the right sidebar and use the following information to create it:

TabFieldInput
SettingsDisplay NameAuthor image
SettingsAPI IDauthorImage

We'll click Add to save.

Now that we're done with our Author model, let's move on to the Book model.

#Book model

Book modelBook model

Our second model will be the Book model. In the Schema builder, we'll click +Add next to Models, and use the following information:

FieldInput
Display NameBook
API IDBook
API ID PluralBooks

We'll click Add model to save.

Our model has been created but it's empty. To create a simple model that will contain basic book information, we'll add the book name, description, cover image, and a relation to the author.

Let's start with the book name, as a Single line text field. We'll find it on the Add fields right sidebar, and click Add on the field card to add it.

We'll use the following information:

TabFieldInput
SettingsDisplay NameBook name
SettingsAPI IDbookName
SettingsUse as title field checkboxLeave this checkbox selected

We'll click Add to save.

Next, we'll add a Rich text field, which will our book description. We'll select the Rich text field from the right sidebar and use the following information to create it:

TabFieldInput
SettingsDisplay NameBook description
SettingsAPI IDbookDescription

We'll click Add to save.

Now let's add an Asset picker field, which will be our book cover image. We'll select the Asset picker field from the right sidebar and use the following information to create it:

TabFieldInput
SettingsDisplay NameBook cover
SettingsAPI IDbookCover

We'll click Add to save.

Finally, we want books and authors to be connected. A great way to do this is using a two-way reference in our Book model, that will create a relation with the Author model. This type of relation will also create a reverse field that we will later be able to see in our Author model, connecting back to our Book model.

We'll find the Reference field on the Add fields right sidebar, and click Add on the field card to add it.

We'll use the following information:

TabFieldInput
DefineReference typeSelect Allow only one model to be referenced
DefineModels to referenceUse the dropdown menu to select Author
DefineReference directionSelect Two-way reference
DefineAllow multiple... checkboxSelect Allow multiple Book per Author and Allow multiple Author per Book
Configure referenceDisplay NameAuthor
Configure referenceAPI IDAuthor
Configure reverse fieldDisplay NameBook
Configure reverse fieldAPI IDbook

We'll click Add to save.

Now that we're done with our Book model, let's move on to the Shop model.

#Shop model

Shop modelShop model

Our final model is the Shop model. In the Schema builder, we'll click +Add next to Models, and use the following information:

FieldInput
Display NameShop
API IDShop
API ID PluralShops

We'll click Add model to save.

Our model has been created but it's empty. To create a simple model that will contain basic shop information, we'll add the shop name, address, picture and location.

Let's start with the shop name, as a Single line text field. We'll find it on the Add fields right sidebar, and click Add on the field card to add it.

We'll use the following information:

TabFieldInput
SettingsDisplay NameShop name
SettingsAPI IDshopName
SettingsUse as title field checkboxLeave this checkbox selected

We'll click Add to save.

Next, we'll add another Single line text field for the shop address.

We'll use the following information:

TabFieldInput
SettingsDisplay NameShop address
SettingsAPI IDshopAddress

We'll click Add to save.

Finally, we'll add an Asset picker field, which will be our shop's image. We'll select the Asset picker field from the right sidebar and use the following information to create it:

TabFieldInput
SettingsDisplay NameShop picture
SettingsAPI IDshopPicture

We'll click Add to save.

Finally, we'll add a location field so Editors can show the shop location on a map. We'll select the Location field from the right sidebar and use the following information to create it:

TabFieldInput
SettingsDisplay NameLocation
SettingsAPI IDlocation

We'll click Add to save.

Now that we're done with our three models, let's create our links component!

Now that we have all the models that we need to relate to our related content block component, we'll go ahead and create it!

Related content block componentRelated content block component

We'll click + Add next to Components and add it using this information:

FieldInput
Display NameRelated content block
API IDRelatedContentBlock
API ID PluralRelatedContentBlocks

We'll click Add component to save, and then we'll start adding instances to it.

We want our block to have a title, a body, an image and we also want the possibility to relate existing content entries from the other models to it.

We'll start with the title. Let's add a Single line text field using the following information:

TabFieldInput
SettingsDisplay NameBlock title
SettingsAPI IDblockTitle
SettingsUse as title field checkboxSelect this checkbox

We'll click Add to save.

Next, we'll add a Rich text field, which will be our block body:

TabFieldInput
SettingsDisplay NameBlock body
SettingsAPI IDblockBody

We'll click Add to save.

Next, we'll add an Asset picker field, which will be our block's image. We'll select the Asset picker field from the right sidebar and use the following information to create it:

TabFieldInput
SettingsDisplay NameBlock image
SettingsAPI IDblockImage

We'll click Add to save.

Finally, we will add a Reference field from the right sidebar, so we can use it to relate content entries from other models.

We'll use the following information:

TabFieldInput
DefineReference typeSelect Allow multiple models to be referenced (Union Type)
DefineModels to referenceUse the dropdown menu to select Author, Book, and Shop
DefineReference directionSelect One-way reference
Configure referenceDisplay NameRelated content
Configure referenceAPI IDrelatedContent

We'll click Add to save.

This is how you create a simple content block component containing some basic information - title, body and image - and the possibility to reference content entries from other models in your schema.