Frequently Asked Questions

Getting Started & Implementation

What are the prerequisites for building a Reference FAQ Component in Hygraph?

To build a Reference FAQ Component in Hygraph, you need a Hygraph account and an existing project. If you don't have an account, you can sign up here. You can either create a new project to follow the tutorial or use an existing project and adapt the instructions to your schema. Note: Plan limits may affect your ability to add new models or components. For more, see the Hygraph pricing page. Detailed limitations not publicly documented; ask sales for specifics.

How long does it take to implement Hygraph and how easy is it to start?

Implementation time varies by project complexity. For simple use cases, you can get started in minutes using pre-configured starter projects or by cloning demo projects. Enterprise-level implementations may take longer but are streamlined with structured onboarding and technical support. Extensive documentation, onboarding guides, and community support are available to help you get started quickly. Note: Complex migrations or custom integrations may require additional time and technical resources. Learn more.

Features & Capabilities

What is a Reference FAQ Component in Hygraph and how does it work?

A Reference FAQ Component in Hygraph is a reusable component that allows you to create lists of question-and-answer pairs (Q&A) as individual content entries. These Q&A pairs are managed in a dedicated model (e.g., "FAQ List Single") and can be referenced in other models or components. This setup enables editors to easily assemble and reuse FAQ lists across different parts of a project. Note: Embedding content from other Q&A pairs or models is optional and not enabled by default in the simple setup. See the guide.

What schema elements are involved in building a Reference FAQ Component?

Building a Reference FAQ Component involves creating a model (e.g., "FAQ List Single") to store Q&A pairs, and a component (e.g., "Reference FAQ Component") that references these pairs. The model typically includes a required single-line text field for the question and a required rich text field for the answer. The component includes a section title and a reference field that links to multiple Q&A pairs. Note: Only one model can be referenced per reference field in this setup. Read more.

Can I reuse FAQ Q&A pairs across different models or components in Hygraph?

Yes, by using references, you can reuse Q&A pairs created in the "FAQ List Single" model across different models or components. This allows for efficient content management and consistency, as the same Q&A entries can be linked wherever needed. Note: If you need to embed content from other Q&A pairs or models, you may need to enable embedding or adjust your schema accordingly. Learn more about references.

What are the main features of Hygraph that support building and managing FAQ components?

Hygraph offers a GraphQL-native architecture, reusable components, reference fields for content relationships, and a marketer-friendly editorial UI. These features enable flexible schema modeling, efficient content reuse, and easy management of structured content like FAQs. Note: Advanced features such as content federation, localization, and versioning are available for more complex use cases. See all features.

Technical Documentation & Support

Where can I find technical documentation for building FAQ components in Hygraph?

Comprehensive technical documentation is available on the Hygraph Docs site. Key resources include the Reference FAQ Component guide, Components documentation, and References documentation. For onboarding and advanced guides, visit the Hygraph Documentation homepage. Note: Some advanced use cases may require direct support or community input.

Is there a way to get community support or suggest new FAQ recipes for Hygraph?

Yes, you can join the Hygraph Community on Slack at hygraph-community.slack.com to ask questions, get support, and suggest new recipe ideas. Note: Community support is best for general questions; for enterprise support, contact Hygraph directly.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant, ISO 27001 certified, and GDPR compliant. These certifications ensure adherence to rigorous security and data protection standards. For more details, visit the Secure Features page. Note: For additional security requirements, such as penetration testing or custom data centers, contact Hygraph sales.

What enterprise security features are available in Hygraph?

Hygraph provides enterprise-grade security features including granular permissions, audit logs, encryption at rest and in transit, automatic backups and one-click recovery (on enterprise plans), and governance tools like multi-tenant architecture. Penetration testing is available as an add-on for enterprise customers. Note: Some features are only available on enterprise plans; check with Hygraph for details. Learn more.

Integrations & APIs

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management (DAM) tools like Cloudinary, Bynder, Filestack, Scaleflex Filerobot, and Aprimo; localization tools like DeepL and EasyTranslate; hosting and deployment platforms like Netlify and Vercel; video management with Mux; marketing tools such as Klaviyo, Segment, and Google Analytics; and commerce/search platforms like Shopify, BigCommerce, commercetools, and Algolia. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional configuration or subscriptions.

Does Hygraph provide APIs for content management and delivery?

Yes, Hygraph provides a GraphQL-native Content API for delivering content to any frontend or application, a Management API for programmatic schema and user management, and an API Playground for testing API calls. These APIs support efficient content delivery and integration with modern tech stacks. Note: API usage may be subject to plan limits and rate restrictions. Learn more.

Use Cases & Benefits

Who can benefit from using Hygraph for FAQ management?

Hygraph is suitable for marketing and content teams, developers, product managers, and enterprise IT teams who need to manage structured content like FAQs across multiple channels, brands, or regions. Its reference-based approach enables efficient content reuse and consistency. Note: Teams with highly custom or legacy requirements may need to adapt their workflows or consult Hygraph support. See customer stories.

What are the main business benefits of using Hygraph for content and FAQ management?

Key benefits include faster time-to-market, cost savings through content reuse and automation, improved content consistency, enhanced customer engagement, and scalability for global operations. Case studies show results such as Komax achieving a 3X faster time-to-market and Samsung improving customer engagement by 15%. Note: ROI depends on implementation scope and organizational readiness. Read case studies.

Pain Points & Limitations

What common challenges does Hygraph address for FAQ and content management?

Hygraph addresses challenges such as dependency on developers for content updates, content inconsistency across channels, workflow inefficiencies, and integration difficulties with legacy systems. Its reference-based model and user-friendly UI empower non-technical users and streamline content operations. Note: Highly specialized workflows or legacy migrations may require additional customization. See documentation.

Are there any limitations to using the Reference FAQ Component approach in Hygraph?

The Reference FAQ Component is ideal for modular, reusable FAQ lists, but may require schema adjustments for highly custom workflows or advanced embedding needs. Only one model can be referenced per reference field in this setup, and embedding is not enabled by default. For more complex requirements, consider consulting Hygraph documentation or support. See alternative approaches.

LLM optimization

When was this page last updated?

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

Hygraph
Docs

#Reference FAQ component

#Overview

This guide shows how to create an FAQ component to create lists of pre-defined Q&A pairs. This component can be used in any model in your project.

You'll create a model that contains the data for the Q&A pairs and a component that lets you create a list of questions and answers, adding this information through a reference field.

Reference FAQ ComponentReference FAQ Component

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 models or components to create the FAQ list. It is also a great option if you need to show different sets of Q&A pairs throughout your website, as it allows you to take the resulting component, and add it to any model in your project.

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 Reference FAQ Component. 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 Reference FAQ Component. 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.
  • 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.
  • 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 or components later on. In the next step, we will create the Reference FAQ Component, which will contain a reference field that connects this model. This will allow editors to quickly set up lists of Q&A pairs.

#3. Create the Reference FAQ Component

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

FieldInput
Display nameReference FAQ Component
API IDReferenceFaqComponent
API ID PluralReferenceFaqComponents

Click Add component to save.

This component will contain only two fields: a Single line text field for the FAQ section title, and a Reference field to add lists of Q&A 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 nameFAQ Section title
SettingsAPI IDfaqSectionTitle
SettingsDescriptionWrite a section title here
SettingsUse as title fieldLeave this checkbox selected

Click Add to save.

Next, you will create a reference field that will allow editors to add Q&A pairs 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
ConfigureDescriptionLink a Q&A pair or create a new one

Click Add to save.

Your component is ready! This is how you build an FAQ component that uses references to link Q&A pairs.

#Resulting content form

If you were to use this component in a model, the component section of the resulting content form should look like this:

Resulting content form

Editors will be able to easily link existing Q&A pairs from the FAQ List model.