Frequently Asked Questions

Getting Started & Project Setup

What are the prerequisites for creating a simple FAQ page in Hygraph?

To create a simple FAQ page in Hygraph, you need a Hygraph account and an active project. If you don't have an account, you can sign up here. You can either create a new project or use an existing one, adjusting the tutorial steps to fit your schema as needed.

How do I create a FAQ list model in Hygraph?

To create a FAQ list model, navigate to the Schema builder and click +Add next to Models. Set the display name to "FAQ List Single" and configure fields for the question (single line text, required, unique) and answer (rich text, required). This allows you to store Q&A pairs as content entries.

How do I create a FAQ page model in Hygraph?

To create a FAQ page model, use the Schema builder to add a new model with a single line text field for the page title and a reference field to link Q&A pairs from the FAQ List Single model. This setup enables editors to build FAQ pages by referencing existing Q&A pairs.

Can I use components instead of models for FAQ lists in Hygraph?

Yes, you can add the same set of fields to a component rather than a model to reuse as a template for an FAQ list block. This approach is explored in the Reference FAQ Component recipe.

What does the resulting content form look like after following the FAQ page tutorial?

After following the tutorial, your content form will allow editors to easily create FAQ pages by referencing Q&A pairs from the FAQ List model. The form includes fields for the page title and a reference field to select multiple Q&A pairs.

Where can I find documentation on references in Hygraph?

You can find detailed documentation on references in Hygraph at the References documentation page.

Can I clone the entire FAQ cookbook project?

Yes, you can clone the entire FAQ cookbook project if you want to explore how FAQ recipes are built without following the step-by-step process. This project contains all FAQ recipes for comparison and review.

What are the core schema concepts used in building a FAQ page in Hygraph?

The core schema concepts include models (content structure), references (relations between entries), fields (single line text for questions, rich text for answers), and the ability to reuse content entries by connecting them through reference fields.

How can I add Q&A pairs to a FAQ page in Hygraph?

You can add Q&A pairs to a FAQ page by creating them as content entries in the FAQ List Single model and then referencing them in the FAQ Page model using the reference field. This allows for easy reuse and organization of Q&A pairs.

Is embedding content from other models necessary for a simple FAQ page?

Embedding content from other models is not necessary for a simple FAQ page setup. However, you may enable embedding if your content can benefit from it, such as inserting content from other Q&A pairs or models.

What is the recommended way to manage FAQ content in Hygraph?

The recommended way is to create Q&A pairs as individual content entries in a dedicated model and reference them in a FAQ Page model. This approach allows for easy reuse, organization, and updating of FAQ content.

Can I use an existing Hygraph project to add a FAQ page model?

Yes, you can use an existing Hygraph project to add a FAQ page model. You may need to adjust parts of the tutorial to fit your current project schema.

How do I ensure unique titles for FAQ Page entries?

When creating the FAQ Page model, set the page title field as required and unique in the field validations. This ensures each FAQ Page entry has a distinct title for easy identification.

What is the purpose of the reference field in the FAQ Page model?

The reference field in the FAQ Page model allows editors to select and link multiple Q&A pairs from the FAQ List Single model, enabling the creation of comprehensive FAQ pages using existing content entries.

How do I add validations to fields in Hygraph models?

When adding fields in Hygraph models, you can set validations such as "Make field required" and "Set field as unique" in the field settings. This ensures data integrity and proper content management.

Can I allow multiple Q&A pairs to be referenced in a FAQ Page?

Yes, when configuring the reference field in the FAQ Page model, select the option to allow multiple references. This enables editors to add several Q&A pairs to a single FAQ Page.

What is the difference between one-way and two-way references in Hygraph?

One-way references allow a model to reference another model without reciprocal linkage, while two-way references create a bidirectional relationship. For FAQ pages, one-way references are typically used to link Q&A pairs to the FAQ Page.

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

You can join the Hygraph community on Slack at hygraph-community.slack.com to get help, share feedback, and suggest new recipe ideas.

Where can I find more tutorials and guides for Hygraph?

You can find more tutorials and guides in the Hygraph documentation at hygraph.com/docs, including developer guides, API reference, and code examples.

Pricing & Plans

What pricing plans does Hygraph offer?

Hygraph offers three main pricing plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan is designed for different team sizes and project needs. For details, visit the Hygraph pricing page.

What features are included in the Hobby plan?

The Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload size, live preview, and commenting/assignment workflow. Sign up here.

What features are included in the Growth plan?

The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload size, remote source connection, 14-day version retention, and email support desk. Get started here.

What features are included in the Enterprise plan?

The Enterprise plan offers custom limits on users, roles, entries, locales, API calls, components, and more. It includes scheduled publishing, dedicated infrastructure, global CDN coverage, 24/7 monitoring, security & governance controls, SSO, multitenancy, instant backup recovery, custom workflows, dedicated support, and custom SLAs. Try for 30 days or request a demo.

Features & Capabilities

What are the key capabilities and benefits of Hygraph?

Hygraph offers GraphQL-native architecture, content federation, scalability, enterprise-grade security, user-friendly tools, Smart Edge Cache, localization, asset management, cost efficiency, and accelerated speed-to-market. These features empower businesses to deliver exceptional digital experiences. See case studies.

Does Hygraph support integrations with other platforms?

Yes, Hygraph supports integrations with Digital Asset Management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), Adminix, Plasmic, custom SDK/API integrations, and marketplace apps for headless commerce and PIMs. See documentation.

What APIs does Hygraph provide?

Hygraph provides Content API (read/write), High Performance Content API (low latency, high throughput), MCP Server API (AI assistant integration), Asset Upload API, and Management API. See API Reference.

Where can I find technical documentation for Hygraph?

Technical documentation for Hygraph is available at hygraph.com/docs, including API reference, schema components, references, webhooks, and AI integrations.

How does Hygraph perform in terms of speed and reliability?

Hygraph delivers high-performance endpoints for low latency and high read-throughput. Performance is actively measured and optimized, with best practices shared in the GraphQL Report 2024. Read more.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure robust security and data protection. See secure features.

What enterprise-grade security features does Hygraph offer?

Hygraph offers granular permissions, audit logs, SSO integrations, encryption at rest and in transit, regular backups, dedicated hosting options, and a customer reporting process for incidents. Learn more.

Use Cases & Benefits

Who is the target audience for Hygraph?

Hygraph is designed for developers, product managers, content creators, marketing professionals, and solutions architects in enterprises, agencies, eCommerce, media, technology, healthcare, and global brands. See case studies.

What industries use Hygraph?

Industries represented in Hygraph's case studies include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. See more.

What business impact can customers expect from using Hygraph?

Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved 3x faster time-to-market and Samsung improved engagement by 15%. See case studies.

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

Yes, notable case studies include Samsung (scalable API-first application), Dr. Oetker (MACH architecture), Komax (3x faster time-to-market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced bottlenecks), and Lindex Group (global content delivery). See all case studies.

Who are some of Hygraph's customers?

Hygraph's customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. See more.

Pain Points & Solutions

What core problems does Hygraph solve?

Hygraph solves operational inefficiencies (eliminates developer dependency, modernizes legacy stacks, ensures content consistency), financial challenges (reduces costs, accelerates speed-to-market, supports scalability), and technical issues (simplifies schema evolution, robust integrations, performance optimization, localization, and asset management). See case studies.

What pain points do Hygraph customers commonly express?

Customers often face developer dependency, legacy tech stack challenges, 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. Hygraph addresses these with its architecture and features. See case studies.

How does Hygraph differentiate itself in solving these pain points?

Hygraph differentiates itself with a user-friendly interface, GraphQL-native architecture, content federation, cost efficiency, accelerated speed-to-market, robust APIs, Smart Edge Cache, and enhanced localization/asset management. It stands out as the first GraphQL-native Headless CMS, offering flexibility and scalability. See more.

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

Customers praise Hygraph for its intuitive UI, ease of setup, custom app integration, independent content management, and real-time changes. For example, Anastasija S. noted, "Every change I make to Hygraph I can instantly see on the front-end." Some users find it time-consuming for less technical users. See more.

Implementation & Support

How long does it take to implement Hygraph?

Implementation time varies by project. For example, Top Villas launched in just 2 months, and Si Vale met aggressive deadlines smoothly. Hygraph supports quick rollouts with efficient onboarding and training resources. See Top Villas case study.

How easy is it to start using Hygraph?

Hygraph offers a free API playground, free forever developer account, structured onboarding (introduction, provisioning, kickoff calls), training resources (webinars, videos), extensive documentation, and a community Slack channel for support. See documentation.

Competition & Comparison

How does Hygraph compare to traditional CMS platforms?

Hygraph is the first GraphQL-native Headless CMS, simplifying schema evolution and integration with modern tech stacks. It offers content federation, user-friendly tools, enterprise-grade features, and proven ROI, setting it apart from traditional CMS platforms that rely on REST APIs. See case studies.

Why choose Hygraph over alternatives in the market?

Hygraph offers unique advantages: GraphQL-native architecture, content federation, enterprise-grade features, user-friendly tools, scalability, proven ROI (Komax 3x faster time-to-market, Samsung 15% engagement increase), and market recognition (ranked 2nd out of 102 Headless CMSs in G2 Summer 2025). See more.

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs

#Simple FAQ page

#Overview

This guide shows how to create an FAQ model that lets you add pre-created Q&A pairs to form a list.

You'll create two models: one model to store the Q&A pairs, and a model that will let you add Q&A pairs through reference fields to form a list.

Simple FAQ pageSimple FAQ page

This recipe is a great option if you prefer to work on Q&A pairs as individual content pieces that you can easily add to another model to create the FAQ list.

This mock image shows what a frontend using this setup could look like:

Mock imageMock image

#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. Look into the following section to learn more about your options.

#What you can do

Use this guide to create a Simple FAQ Page model. You have two options:

  • OPTION 1: Create a project. This is the way to go if you want to follow the entire tutorial for learning purposes.
  • OPTION 2: Use an existing project of yours. This is the way to go if you already have a project and want to add this model. In this case, you may need to adjust parts of the tutorial to your own project schema.

#Not in the mood to start building?

Clone the entire cookbook

This is the way to go if you're curious about how we built the FAQ recipes but don't want to follow the step-by-step creation process. This project contains the entire FAQ Cookbook so you can compare recipes or look into what instances they contain.

#Core concepts

In this guide, you'll work with different schema elements to create a Simple FAQ Page model. Let's look into them:

  • Model: Your schema is the content structure of your project. You can define your schema by creating models, adding fields, reusable components, and sidebar widgets, integrating remote sources, and establishing relationships with other models.
  • 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 create related content directly from the content form.

#Step-by-step guide

This video follows the same step-by-step tutorial offered in this document.

#1. Create the FAQ list model

This model will let you create Q&A pairs as content entries.

To create the model, navigate to the Schema builder and click +Add next to Models. Use the following information:

FieldInput
Display nameFAQ List Single
API IDFaqListSingle
API ID PluralFaqListSingles

Click Add Model to save.

Now that the model has been created, you can start adding fields to it.

We will add a Single line text field to use as question, and a Rich Text field for the answer.

Let's start with the question. Add a Single line text field from the right sidebar, and use the following information:

TabFieldInput
SettingsDisplay nameQuestion
SettingsAPI IDquestion
SettingsDescriptionWrite the question here
SettingsUse as title fieldLeave this checkbox selected
ValidationsMake field requiredSelect this checkbox
ValidationsSet field as uniqueSelect this checkbox

Click Add to save.

Next, you want include a rich text field for the answer, which will also allow some formatting. Add a Rich text field from the right sidebar, using the following information:

TabFieldInput
SettingsDisplay nameAnswer
SettingsAPI IDanswer
SettingsDescriptionWrite the answer here
ValidationsMake field requiredSelect this checkbox

Click Add to save.

We chose to create the FAQ list as a model because in a use case like this, we want to create question & answer sets as content entries that can be easily referenced in other models later on. In the next step, we will create the Simple FAQ Page Model with a reference field that connects this model, which will allow editors to quickly set up FAQ landing pages using existing data.

#3. Create the FAQ page model

To create the FAQ Page model, navigate to the Schema builder and click +Add next to Models. Use the following information:

FieldInput
Display nameSimple FAQ Page
API IDSimpleFaqPage
API ID PluralSimpleFaqPages

Click Add Model to save.

This model will contain only two fields: a Single line text field for the page title, and a Reference field to add Q&A pairs from the model you created in the previous step.

Let's start with the title. Add a Single line text field from the right sidebar, and use the following information:

TabFieldInput
SettingsDisplay namePage title
SettingsAPI IDpageTitle
SettingsDescriptionWrite a page title here
SettingsUse as title fieldLeave this checkbox selected
ValidationsMake field requiredSelect this checkbox
ValidationsSet field as uniqueSelect this checkbox

Click Add to save.

This configuration ensures that all FAQ Page entries contain a unique title that will allow easy identification in the content form.

Next, you will create a reference field that will allow editors to add content entries from the model you created in the previous step.

Add a Reference field from the right sidebar, using the following information:

TabFieldInput
DefineAllow only one model to be referencedSelect this radio button.
DefineModel to referenceuse the dropdown to select FAQ List Single
DefineReference directionUse the radio button to select One-way reference
DefineRelation cardinalityOne to Many
DefineAllow multiple (…)Select this checkbox
ConfigureDisplay nameQ&A Pair
ConfigureAPI IDqAPair
ConfigureDescriptionSelect Q&A pairs

Click Add to save.

Your model is ready! This is how you build a Simple FAQ Page model that lets you easily add Q&A pairs through a reference field.

#Resulting content form

If you followed this tutorial, your resulting content form should look like this:

Resulting content formResulting content form

Editors will be able to easily create FAQ pages by referencing Q&A pairs from the FAQ List model.