How do I create an image gallery model in Hygraph with titles and descriptions for each image?
To create an image gallery model in Hygraph where each image has a title and description, you need to build a component called "Image with info". This component includes fields for image title (single line text), image (asset picker), and image description (multi line text). You then add this component to your gallery model, allowing multiple instances so you can add several images, each with its own metadata. For step-by-step instructions, see the official guide. Note: You must have a Hygraph account and project to follow this process.
Can I clone a pre-built image gallery project in Hygraph?
Yes, Hygraph offers a pre-built project containing the entire Image Galleries Cookbook. You can clone this project to compare different gallery configurations without creating multiple projects. Use this link to clone the project. Note: You must have a Hygraph account to clone projects.
What are the prerequisites for building an image gallery in Hygraph?
You need a Hygraph account and a project. You can create a new project, clone the cookbook project, or use an existing project. Plan limits may apply, so review plan limits before adding recipes to your project. Detailed onboarding resources are available in the Getting Started Tutorial.
Features & Capabilities
What are the key features of Hygraph for content modeling and image galleries?
Hygraph supports flexible schema modeling with reusable components, allowing you to add fields like image title, image asset, and description. You can configure components for single or multiple values, integrate remote sources, and establish relationships between models. Components act as templates for field configuration, enabling content reuse and customization. Note: For asset metadata, you can also add fields directly to the Asset System model. Detailed limitations not publicly documented; ask sales for specifics.
Does Hygraph support API access for image galleries and content?
Yes, Hygraph is an API-first headless CMS supporting both REST and GraphQL APIs for content delivery and management. This enables developers to integrate image galleries and other content with any frontend or application. For technical details, see API documentation. Note: API rate limits and advanced usage scenarios may require higher-tier plans; check documentation for specifics.
What integrations are available for Hygraph?
Hygraph offers integrations with Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. These integrations enable scalable search, analytics, workflow automation, personalized marketing, and product data management. For a full list, visit the Marketplace Apps page. Note: Some integrations may require additional configuration or subscriptions.
Implementation & Onboarding
How long does it take to implement Hygraph for an image gallery project?
Implementation timelines depend on project complexity. Simple image gallery setups can be completed in a few days using starter templates and structured onboarding. More complex projects may require additional time. Resources include pre-configured starter projects, onboarding calls, technical kickoffs, and extensive documentation. For details, see Getting Started guide. Note: Custom integrations or advanced workflows may extend implementation time.
What technical documentation is available for Hygraph users?
Hygraph provides comprehensive technical documentation, including getting started guides, advanced tutorials, and developer resources. These cover schema modeling, API usage, integrations, and best practices. Access documentation at Hygraph Docs. Note: Documentation is updated regularly; check for the latest guides and recipes.
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 complies with GDPR and CCPA regulations. 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 the security features page. Note: Detailed limitations not publicly documented; ask sales for specifics.
Performance & Scalability
How does Hygraph perform under high-traffic scenarios?
Hygraph delivers content via a high-performance global CDN, supports region-based hosting, and advanced caching (Smart Edge Cache). It has demonstrated scalability by supporting 3.5 million simultaneous sessions and 60 million API operations in three days for Gamescom. Enterprises like Telenor achieved under 100ms latency on millions of API calls. Note: Best fit for high-traffic, global use cases; teams needing specialized local hosting may want to confirm region support.
Use Cases & Benefits
Who can benefit from using Hygraph for image galleries and content management?
Hygraph is suited for marketing and content teams, product managers, developers, and enterprise IT teams. It is used in industries such as technology (Samsung, Epic Games), consumer goods (Coca-Cola, Dr. Oetker), telecommunications (Telenor), media (Gamescom), travel (HolidayCheck), scientific publishing (GDCh), government (Statistics Finland), sports/events (DTM), and retail/e-commerce (Stobag). Note: Teams requiring highly specialized workflows or legacy CMS compatibility may need to evaluate fit.
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). Hygraph enables operational efficiency, scalability, and enhanced customer experiences. For more, see Hygraph Case Studies. Note: Impact varies by implementation; detailed limitations not publicly documented.
Customer Proof & Success Stories
Can you share specific case studies or success stories of Hygraph customers?
Yes. Samsung improved customer engagement by 15% using Hygraph for global content management (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 from a single platform (case study). Telenor achieved under 100ms latency on millions of API calls (case study). HolidayCheck reduced developer bottlenecks (case study). Note: Results may vary; detailed limitations not publicly documented.
Limitations & Trade-Offs
Are there any limitations or scenarios where Hygraph may not be the best fit?
Hygraph is best suited for teams seeking modern, API-first content management with flexible schema modeling and global scalability. Teams needing highly specialized workflows, legacy CMS compatibility, or advanced local hosting may need to evaluate fit. Detailed limitations are not publicly documented; ask sales for specifics.
This guide shows how to build an image gallery model containing a basic component field that will allow you to add multiple images, each with its own title and description.
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 entire cookbook. This is the way to go if you're curious about how the galleries are made but don't want to follow the step-by-step creation process. This project contains the entire Image galleries Cookbook so you can compare them, or look into what instances they contain.
OPTION 3:Use an existing project of yours. If you have a project already and want to add this image gallery 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.
Take plan limits into consideration when adding a recipe to your own project.
In this guide, you'll work with a number of schema elements. Let's look into them:
Model: Your schema is the content structure of your project. You can define your schema by creating models and adding fields, reusable components, and sidebar widgets to them, as well as integrating remote sources and establishing relationships with other models.
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.
Path 1: Use this guide to create an image gallery model where all images have a title and description.
Path 2: Clone the project that we created for you. It contains the entire Image galleries cookbook to compare the different gallery configurations without having to clone multiple projects.
This cookbook contains all the recipes we have so far to create image galleries, so you can compare the different gallery configurations without having to clone multiple projects.
To find this particular recipe in the cookbook project, navigate to the schema and look for the "Gallery with info" model.
We will start by creating our image component. It should allow us to add an image along with a title and a description.
We'll click + Add next to Components and add it using this information:
Field
Input
Display Name
Image with info
API ID
ImageWithInfo
API ID Plural
ImageWithInfos
We'll click Add component to save, and then we'll start adding instances to it.
We'll start with a Single line text field, which will be our image component title. Let's add it by clicking Add on the Single line text field card on the right sidebar.
We'll use the following information:
Tab
Field
Input
Settings
Display Name
Image title
Settings
API ID
imageTitle
Settings
Description
Add your image title here
Settings
Use as title field checkbox
Select this checkbox
We'll click Add to save.
Next, we'll add an Asset picker field that will let us add images, using the following information:
Tab
Field
Input
Settings
Display Name
Image
Settings
API ID
image
Settings
Description
Select your image
We'll click Add to save. In this case we will not allow multiple values, because we want to add a single image per title & description.
Finally, we'll add a Multi line text field, for our image description. We'll select it from the right sidebar, and use this information:
Tab
Field
Input
Settings
Display Name
Image description
Settings
API ID
imageDescription
Settings
Description
Write a description here
We'll click Add to save.
Now that our component is ready, let's move on to model creation.
Pro Tip
Another way to add metadata to your images, is to add the fields directly to your Asset System model. This guide shows you how to do it.
In this tutorial, we choose to add this information as instances to a component because this way the images in your gallery can be reused with a different title & description each time.
You can think of components as field configuration templates, without content attached to them. Unlike with references, when using components, you need to add new content each time.
Both ways of adding metadata can be a good choice; when using this in the future, think about your use case to choose the one that works best for your project!
Now that we have a component that lets us add an image with title and description, let's create a gallery model.
In the Schema builder, we'll click +Add next to Models, and use the following information:
Field
Input
Display Name
Gallery with info
API ID
GalleryWithInfo
API ID Plural
GalleryWithInfos
We'll click Add model to save.
Our model has been created but it's empty. To create our image gallery model, we'll add the gallery title, and the component we created earlier.
Let's start with the title, 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:
Tab
Field
Input
Settings
Display Name
Gallery title
Settings
API ID
galleryTitle
Settings
Use as title field checkbox
Leave this checkbox selected
We'll click Add to save.
Next, we'll add our "image with info" component. We'll make sure the component allows multiple values, so that it lets us add multiple images with title and description to a content entry.
We'll find the Basic component field on the Add fields right sidebar, click Add to add it, and use the following information:
Tab
Field
Input
Settings
Display Name
Image
Settings
API ID
image
Settings
Description
Add your images
Settings
Field options
Select the Allow multiple values checkbox
Settings
Select component
Use the dropdown to select the "Image with info" component
We'll click Add to save.
This is how you create an image gallery model containing a title and a component that will allow you to add multiple instances of an image with a title and description.
This is one way of creating an image gallery using Hygraph. If you want to try out more gallery configurations, we have other image gallery types for you to look into!
This guide shows how to build an image gallery model containing a basic component field that will allow you to add multiple images, each with its own title and description.
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 entire cookbook. This is the way to go if you're curious about how the galleries are made but don't want to follow the step-by-step creation process. This project contains the entire Image galleries Cookbook so you can compare them, or look into what instances they contain.
OPTION 3:Use an existing project of yours. If you have a project already and want to add this image gallery 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.
Take plan limits into consideration when adding a recipe to your own project.
In this guide, you'll work with a number of schema elements. Let's look into them:
Model: Your schema is the content structure of your project. You can define your schema by creating models and adding fields, reusable components, and sidebar widgets to them, as well as integrating remote sources and establishing relationships with other models.
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.
Path 1: Use this guide to create an image gallery model where all images have a title and description.
Path 2: Clone the project that we created for you. It contains the entire Image galleries cookbook to compare the different gallery configurations without having to clone multiple projects.
This cookbook contains all the recipes we have so far to create image galleries, so you can compare the different gallery configurations without having to clone multiple projects.
To find this particular recipe in the cookbook project, navigate to the schema and look for the "Gallery with info" model.
We will start by creating our image component. It should allow us to add an image along with a title and a description.
We'll click + Add next to Components and add it using this information:
Field
Input
Display Name
Image with info
API ID
ImageWithInfo
API ID Plural
ImageWithInfos
We'll click Add component to save, and then we'll start adding instances to it.
We'll start with a Single line text field, which will be our image component title. Let's add it by clicking Add on the Single line text field card on the right sidebar.
We'll use the following information:
Tab
Field
Input
Settings
Display Name
Image title
Settings
API ID
imageTitle
Settings
Description
Add your image title here
Settings
Use as title field checkbox
Select this checkbox
We'll click Add to save.
Next, we'll add an Asset picker field that will let us add images, using the following information:
Tab
Field
Input
Settings
Display Name
Image
Settings
API ID
image
Settings
Description
Select your image
We'll click Add to save. In this case we will not allow multiple values, because we want to add a single image per title & description.
Finally, we'll add a Multi line text field, for our image description. We'll select it from the right sidebar, and use this information:
Tab
Field
Input
Settings
Display Name
Image description
Settings
API ID
imageDescription
Settings
Description
Write a description here
We'll click Add to save.
Now that our component is ready, let's move on to model creation.
Pro Tip
Another way to add metadata to your images, is to add the fields directly to your Asset System model. This guide shows you how to do it.
In this tutorial, we choose to add this information as instances to a component because this way the images in your gallery can be reused with a different title & description each time.
You can think of components as field configuration templates, without content attached to them. Unlike with references, when using components, you need to add new content each time.
Both ways of adding metadata can be a good choice; when using this in the future, think about your use case to choose the one that works best for your project!
Now that we have a component that lets us add an image with title and description, let's create a gallery model.
In the Schema builder, we'll click +Add next to Models, and use the following information:
Field
Input
Display Name
Gallery with info
API ID
GalleryWithInfo
API ID Plural
GalleryWithInfos
We'll click Add model to save.
Our model has been created but it's empty. To create our image gallery model, we'll add the gallery title, and the component we created earlier.
Let's start with the title, 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:
Tab
Field
Input
Settings
Display Name
Gallery title
Settings
API ID
galleryTitle
Settings
Use as title field checkbox
Leave this checkbox selected
We'll click Add to save.
Next, we'll add our "image with info" component. We'll make sure the component allows multiple values, so that it lets us add multiple images with title and description to a content entry.
We'll find the Basic component field on the Add fields right sidebar, click Add to add it, and use the following information:
Tab
Field
Input
Settings
Display Name
Image
Settings
API ID
image
Settings
Description
Add your images
Settings
Field options
Select the Allow multiple values checkbox
Settings
Select component
Use the dropdown to select the "Image with info" component
We'll click Add to save.
This is how you create an image gallery model containing a title and a component that will allow you to add multiple instances of an image with a title and description.
This is one way of creating an image gallery using Hygraph. If you want to try out more gallery configurations, we have other image gallery types for you to look into!