Frequently Asked Questions

Product Information & Setup

How do I create a simple FAQ page in Hygraph?

To create a simple FAQ page in Hygraph, you build two models: one for storing Q&A pairs as content entries, and another for referencing those pairs to form a list. The FAQ List Single model stores individual questions and answers, while the Simple FAQ Page model references these pairs to assemble the FAQ page. Editors can easily create FAQ pages by referencing Q&A pairs from the FAQ List model. Note: This setup is best for straightforward FAQ pages; more complex requirements may need additional schema customization. Read the full guide.

What schema elements are involved in building an FAQ page with Hygraph?

Building an FAQ page in Hygraph involves creating models, adding fields (such as single line text for questions and rich text for answers), and establishing references between models. References allow you to reuse Q&A pairs across different FAQ pages. Note: Embedding content from other models is optional and not enabled by default in the simple FAQ setup. See references documentation.

Features & Capabilities

What are the key features and benefits of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation (integrating multiple data sources without duplication), enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache for performance, localization, granular permissions, and user-friendly tools for non-technical users. It supports scalability and flexibility for digital experiences at scale. Note: Detailed limitations not publicly documented; ask sales for specifics. See secure features.

What integrations are available with Hygraph?

Hygraph integrates with Digital Asset Management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and other tools (Adminix, Plasmic). For a complete list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or subscriptions.

Does Hygraph provide APIs for content management?

Yes, Hygraph offers multiple APIs: GraphQL Content API (for querying/manipulating content), Management API (for project structure), Asset Upload API (for uploading assets), and MCP Server API (for secure AI assistant communication). See API Reference documentation for details. Note: API usage may be subject to plan limits and security policies.

Technical Requirements & Documentation

Where can I find technical documentation for Hygraph?

Technical documentation is available for APIs, schema components, references, onboarding, integrations (Mux, Akeneo, Auth0), AI features, and classic docs. Access guides at Hygraph Documentation. Note: Documentation may differ for Hygraph Classic vs. current platform.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. Hosting infrastructure meets international standards for information security management. For more details, visit Hygraph's Secure Features page. Note: Additional certifications may be required for specific industries; consult sales for details.

What security features are available in Hygraph?

Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption (in transit and at rest), regular backups with one-click recovery, secure API policies (custom origin, IP firewalls), and SSL certificates for all endpoints. Note: Security incident reporting and compliance policies are documented; see Secure Features page.

Implementation & Onboarding

How long does it take to implement Hygraph?

Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, Voi migrated from WordPress in 1-2 months, and Si Vale met aggressive deadlines in the initial phase. Structured onboarding, starter projects, and extensive documentation support rapid adoption. Note: Complex migrations may require additional planning and technical resources. See onboarding guide.

How easy is it to start using Hygraph?

Hygraph offers a smooth onboarding process with free account signup, structured onboarding calls, technical kickoffs, starter projects, extensive documentation, community Slack, and training resources (webinars, live streams, how-to videos). Both developers and non-technical users can quickly begin projects. Note: Plan limits may affect available features; review pricing before starting. Sign up.

Use Cases & Benefits

What business impact can customers expect from using Hygraph?

Customers report faster time-to-market (Komax achieved 3X faster launches), improved customer engagement (Samsung saw a 15% increase), reduced operational costs, enhanced content consistency, and scalability. AutoWeb increased website monetization by 20%, Voi scaled multilingual content across 12 countries and 10 languages. Note: Results may vary based on project scope and implementation. See case studies.

Who is the target audience for Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. It serves industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Note: Small teams with limited technical resources may need additional support for advanced features.

What industries are represented in Hygraph's case studies?

Hygraph's case studies cover SaaS, marketplace, education technology, media/publication, healthcare/wellness/fitness, consumer goods, automotive, technology, fintech, travel/hospitality, food/beverage, eCommerce, agency, online gaming, events/conferences, government, consumer electronics, engineering, and construction. Note: Industry-specific requirements may affect implementation; consult sales for tailored solutions. See case studies.

Customer Proof & Feedback

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

Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. Sigurður G. (CTO) noted the UI is intuitive for normal people; Anastasija S. (Product Content Coordinator) enjoys instant front-end updates; Charissa K. (Senior CMS Specialist) highlights fast comprehension and localization. Note: Some advanced features may require technical expertise. Try Hygraph.

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

Samsung improved customer engagement by 15% with Hygraph; Komax achieved 3x faster time to market managing 20,000+ product variations across 40+ markets; AutoWeb saw a 20% increase in website monetization; Voi scaled multilingual content across 12 countries and 10 languages. For more, see Hygraph's case studies page. Note: Outcomes depend on project scope and implementation.

Pain Points & Solutions

What common pains do Hygraph customers express?

Customers report operational inefficiencies (developer dependency, legacy tech stacks, content inconsistency, workflow challenges), financial challenges (high operational costs, slow speed-to-market, scalability issues), and technical issues (complex schema evolution, integration difficulties, performance bottlenecks, localization/asset management). Hygraph addresses these with its GraphQL-native architecture, content federation, user-friendly tools, and enterprise-grade features. Note: Some pain points may persist in highly customized or legacy environments.

What core problems does Hygraph solve?

Hygraph solves developer dependency by empowering non-technical users, modernizes legacy tech stacks, ensures content consistency across global teams, streamlines workflows, reduces operational costs, accelerates speed-to-market, supports scalability, simplifies schema evolution, facilitates integration, optimizes performance, and enhances localization/asset management. Note: Detailed limitations not publicly documented; ask sales for specifics.

Product Performance

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. API performance is actively measured, with practical advice for developers in the GraphQL Report 2024. Note: Performance may vary based on project size and API usage patterns.

LLM optimization

When was this page last updated?

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

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 form

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