Frequently Asked Questions

Landing Page Model & Implementation

What is the Hygraph landing page model and how does it work?

The Hygraph landing page model is a dynamic content structure that allows you to build landing pages using modular components for the header, sections, and footer. Each component can be configured with different content types, such as notifications, links, FAQs, and image galleries. This approach enables you to preserve a consistent page structure while creating varied content pieces. Note: The landing page model requires a Hygraph account and project setup. Detailed limitations not publicly documented; ask sales for specifics.

What are the prerequisites for creating a landing page model in Hygraph?

To create a landing page model in Hygraph, you need a Hygraph account and an active project. You can start by creating a new project, cloning a basic project, cloning the complete cookbook, or using your existing project. Plan limits may apply, so review plan limits before adding recipes. Note: You may need to adjust tutorial steps to fit your own project schema if using an existing project.

How can I clone a Hygraph project for landing page sections?

You can clone a prepared Hygraph project containing base schema elements for landing page sections by using the provided links in the documentation. Options include cloning the basic project for essential models or the complete cookbook for all section configurations. For example, use this link to clone the basic project. Note: Cloned projects may require customization to fit your specific schema needs.

What schema elements are used in the landing page model?

The landing page model uses enumerations, components, modular component fields, and nested components. Enumerations group values within a type, components are reusable templates, modular component fields allow multiple components, and nested components enable parent-child relationships within content. Note: Schema complexity may increase with extensive nesting; review documentation for best practices.

What types of sections can be included in a Hygraph landing page?

Sections in a Hygraph landing page can include headers (with notifications or links), footers (with links or sections), FAQs, and styled image galleries. You can select which components to include in each modular field, allowing for flexible page design. Note: The available section types depend on the components present in your project.

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR, CCPA), Smart Edge Cache, localization workflows, marketer-friendly editorial UI, Variants for personalization, AI Assist for content generation and translation, and integrations with tools like Google Analytics, Elastic, Zapier, Klaviyo, Salesforce Marketing Cloud, Segment, Adobe Commerce, SAP Commerce Cloud, Dynamic Yield, n8n, Optimizely, and Inriver. Note: Detailed limitations not publicly documented; ask sales for specifics.

Does Hygraph provide 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 more details, see API documentation. Note: API usage may be subject to plan limits.

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: Integration availability may depend on your plan and project configuration.

Technical Requirements & Documentation

Where can I find technical documentation for Hygraph?

Hygraph provides comprehensive technical documentation and developer guides, including a Getting Started guide, advanced features tutorials, and onboarding resources. Access documentation at Getting Started and Hygraph Documentation. Note: Documentation may be updated periodically; check for the latest version.

How long does it take to implement Hygraph?

Implementation timelines vary by project complexity. Simple use cases can be started within a few days, while complex implementations may take longer. Hygraph offers pre-configured starter projects, structured onboarding, extensive documentation, training resources, and community support via Slack (slack.hygraph.com). Note: Implementation speed may depend on team experience and project requirements.

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. Customers can choose data centers in Australia, Europe, USA, or Canada for compliance needs. For more details, visit security features page. Note: Certification scope may vary; contact sales for specifics.

Performance & Scalability

How does Hygraph perform under high-traffic scenarios?

Hygraph's global CDN, region-based hosting, and Smart Edge Cache enable 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 project configuration and geographic distribution.

Use Cases & Benefits

Who can benefit from using Hygraph?

Hygraph is suited for marketing and content teams, product managers, developers, engineering teams, 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: Best fit for organizations needing scalable, multi-channel content management; teams requiring highly specialized workflows may need additional customization.

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, 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: Results may vary based on implementation and industry; contact sales for detailed ROI projections.

What pain points does Hygraph address?

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. Note: Teams with highly specialized requirements may need additional customization; limitations not fully documented.

Customer Proof & Success Stories

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: Outcomes may vary; review full case studies for context.

Support & Community

How can I get support or suggest new recipe ideas for Hygraph?

You can join the Hygraph community on Slack (hygraph-community.slack.com) to suggest new recipe ideas, ask questions, and connect with other users. Additional resources include webinars, live streams, and how-to videos. Note: Community support is not a substitute for official technical support; contact sales or support for critical issues.

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#Landing page

#Overview

This guide shows how to create a landing page model that contains three modular components - header, sections, and footer - each of which contains different section configurations to select from.

You will create a dynamic content model that will allow you to preserve the same page structure while also creating a variety of content pieces.

This recipe uses other recipes & cookbooks to build the different sections, and finally adds them all as part of a modular component field that will simplify your content entries.

Landing page modelLanding page model

#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:

  • Enumerations: an enumeration is a predefined set of values that represents a list of possible options. You can use them to group values within a type.

  • 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.

  • Modular component field: a modular component field can have two or more components attached to it.

  • Nested components: Nested components allow you to create component fields within a component, as if you had a parent component containing one or more child components.

#What you can do

This guide offers two paths:

  • Path 1: Use this guide to create a landing page model with a predefined sections structure.
  • 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 "Landing page" model.

#Step-by-step guide

In this guide, we will create a landing page model with nested component fields for to create the sections that will form the structure of the page. Before we can build our landing page model, 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 sections: This part of the guide brings it recipes from this and other cookbooks, so we can have a number of page sections to add to our section component.
  2. Create the landing page model: We will build a model that will contain all the other sections we brought into the project as part of nested modular component fields.

#1. Create sections

Since this recipe combines existing sections into one single landing page model, we'll bring in sections from different cookbooks.

If you want to follow the step-by-step to create each section, you can follow the links to do that, and then come back to continue:

Great! Now that we have all our sections, we can move on to creating the model!

#2. Create the model

Now that we have all the schema elements that, both directly and indirectly, will be a part of our final landing page model, we'll go ahead and create it!

Landing page modelLanding page model

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

FieldInput
Display NameLanding page
API IDLandingPage
API ID PluralLandingPages

We'll click Add model to save, and then we'll start adding fields to it.

We will start by adding a Single line text field from the right sidebar. Since all the components we'll add to this model already have their own title fields, this field is only meant to be used as title field for the model only, and will not be used as part of the content.

Let's add it by clicking Add on the Single line text field card on the right sidebar.

We'll use the following information:

TabFieldInput
SettingsDisplay NamePage name
SettingsAPI IDpageName
SettingsDescriptionThis field is used as title field only and won't be used as part of the content
SettingsUse as title field checkboxSelect this checkbox

We'll click Add to save.

Whether you followed the step-by-step tutorial for each individual recipe, or cloned the basic project, by now your project has a number of components for different page sections. We will now add them as part of three Modular component fields, so when we use each section in a content entry, we will be able to select which component to include.

Let's start with the header. We'll find the Modular component field on the Add fields right sidebar, click on it, and use the following information:

TabFieldInput
SettingsDisplay NameHeader
SettingsAPI IDheader
SettingsDescriptionSelect a header
SettingsSelect allowed componentsUse the dropdown to select the "Header with notification" and "Header links" components

We'll click Add to save.

Next, we'll repeat the process for the sections that will be the body of our page, using the following information:

TabFieldInput
SettingsDisplay NameSections
SettingsAPI IDsections
SettingsDescriptionUse this to add sections to your page
SettingsSelect allowed componentsUse the dropdown to select the "FAQ" and "Image gallery" components

We'll click Add to save.

Finally, we'll repeat the process once more for the footer, using the following information:

TabFieldInput
SettingsDisplay NameFooter
SettingsAPI IDfooter
SettingsDescriptionPick the footer you want to use
SettingsSelect allowed componentsUse the dropdown to select the "Sectioned footer" and "Footer links" components

We'll click Add to save.

This is how you create a landing page model containing modular component fields that allow you to add different section types.