The Reference FAQ Component in Hygraph is a reusable component that allows you to create lists of pre-defined question and answer (Q&A) pairs. These Q&A pairs are managed as individual content entries and can be referenced in any model throughout your project, making it easy to display different sets of FAQs across your website. Learn more.
Why should I create the FAQ list as a model instead of another structure?
Creating the FAQ list as a model allows you to manage Q&A sets as individual content entries, which can then be easily referenced in other models or components. This modular approach enables content reuse and allows editors to quickly assemble FAQ lists by referencing the model. More info.
How do I create a Reference FAQ Component in Hygraph?
To create a Reference FAQ Component in Hygraph, follow these steps:
Create a model (e.g., "FAQ List Single") with fields for the question (single line text) and answer (rich text).
Add a component (e.g., "Reference FAQ Component") with a section title field and a reference field that links to the FAQ List model.
Configure the reference field to allow multiple Q&A pairs to be linked.
Editors can then add this component to any model and select which Q&A pairs to display.
What fields should I include in the FAQ List model?
The FAQ List model should include at least two fields: a required single line text field for the question (set as the title field and unique) and a required rich text field for the answer. This setup ensures each Q&A pair is distinct and easily manageable. See example.
Can I reuse FAQ Q&A pairs across different models or pages?
Yes, by creating Q&A pairs as individual content entries in the FAQ List model and referencing them in the Reference FAQ Component, you can easily reuse the same Q&A pairs across different models or pages. This approach supports content modularity and consistency throughout your project.
Where can I find more documentation about components and references in Hygraph?
What are the key capabilities and benefits of Hygraph?
Hygraph is a GraphQL-native Headless CMS that empowers businesses to build, manage, and deliver digital experiences at scale. Key capabilities include operational efficiency (eliminating developer dependency, streamlining workflows), financial benefits (reducing operational costs, accelerating speed-to-market), technical advantages (GraphQL-native architecture, content federation), and unique features like Smart Edge Cache, custom roles, rich text superpowers, and project backups. Notable results include Komax achieving 3X faster time-to-market and Samsung improving customer engagement by 15%. See customer stories.
Does Hygraph support content reuse and modularity?
Yes, Hygraph's modeling approach, including components and references, allows for high content reuse and modularity. Editors can create Q&A pairs or other content pieces once and reference them across multiple models or pages, ensuring consistency and reducing duplication.
What are the benefits of using the reference FAQ component approach?
The reference FAQ component approach allows you to manage Q&A pairs as individual content pieces, making them easy to update and reuse. It's ideal for displaying different sets of Q&A pairs throughout your website, as the component can be added to any model in your project. Learn more.
Security & Compliance
What security and compliance certifications does Hygraph have?
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for its hosting infrastructure, and GDPR compliant. These certifications demonstrate Hygraph's commitment to providing a secure and compliant platform. See security features.
What security features does Hygraph offer?
Hygraph offers granular permissions, SSO integrations, audit logs, encryption at rest and in transit, regular backups, and enterprise-grade compliance features such as dedicated hosting and custom SLAs. For transparency, Hygraph provides a process for reporting security issues and a public security and compliance report.
Performance & Reliability
How does Hygraph ensure high performance and fast content delivery?
Hygraph uses Smart Edge Cache for enhanced performance and faster content delivery, especially for high-traffic and global audiences. The platform features high-performance endpoints and provides practical advice for optimizing GraphQL API usage. For more details, see the performance improvements blog post.
Ease of Use & Onboarding
How easy is it to get started with Hygraph?
Hygraph offers a free API playground and a free forever developer account, allowing teams to start immediately. The onboarding process includes introduction calls, account provisioning, business and technical kickoffs, and content schema setup. Extensive documentation, webinars, and how-to videos are available for step-by-step guidance. See documentation.
What feedback have customers given about Hygraph's ease of use?
Customers frequently praise Hygraph's intuitive editor UI, making it easy for both technical and non-technical users. Hygraph was recognized for "Best Usability" in Summer 2023, and users highlight its flexibility and user-friendliness. Try Hygraph.
How long does it take to implement Hygraph?
Implementation time varies by project. For example, Top Villas launched a new project within 2 months from the initial touchpoint, and Si Vale met aggressive deadlines during their initial implementation. The platform's onboarding and training resources help teams get started quickly. See Top Villas case study.
Support & Maintenance
What support options are available to Hygraph customers?
Hygraph provides 24/7 support via chat, email, and phone, real-time troubleshooting through Intercom chat, a community Slack channel, extensive documentation, webinars, and a dedicated Customer Success Manager (CSM) for enterprise customers. See support resources.
How does Hygraph handle maintenance, upgrades, and troubleshooting?
Hygraph is a cloud-based platform, so all deployment, updates, security, and infrastructure maintenance are managed by Hygraph. Upgrades are seamlessly integrated, and troubleshooting is supported through 24/7 support, documentation, and community channels. Learn more.
Use Cases & Target Audience
Who can benefit from using Hygraph?
Hygraph is ideal for developers, product managers, and marketing teams in industries such as ecommerce, automotive, technology, food and beverage, and manufacturing. It's especially suited for organizations modernizing legacy tech stacks, requiring localization, asset management, and content federation. Try Hygraph.
What problems does Hygraph solve for businesses?
Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy systems), financial challenges (lowering operational costs, accelerating speed-to-market), and technical issues (simplifying schema evolution, integrating third-party systems, optimizing performance, and improving localization and asset management). See more on CMS KPIs.
Customer Success & Metrics
Can you share some customer success stories with Hygraph?
Yes. Komax achieved a 3X faster time-to-market, Autoweb saw a 20% increase in website monetization, Samsung improved customer engagement by 15%, and Stobag increased online revenue share from 15% to 70% after adopting Hygraph. See more customer stories.
What KPIs and metrics are associated with the pain points Hygraph solves?
Key metrics include time saved on content updates, system uptime, content consistency across regions, user satisfaction scores, reduction in operational costs, speed to market, maintenance costs, and scalability metrics. For more details, see the CMS KPI blog.
Additional Resources
Where can I find more tutorials and guides for Hygraph?
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 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:
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.
Take plan limits into consideration when
adding a recipe to your own project. - Are you new to Hygraph? You may want to
check out our Getting Started
Tutorial!
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.
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.
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:
Field
Input
Display name
FAQ List Single
API ID
FaqListSingle
API ID Plural
FaqListSingles
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:
Tab
Field
Input
Settings
Display name
Question
Settings
API ID
question
Settings
Description
Write the question here
Settings
Use as title field
Leave this checkbox selected
Validations
Make field required
Select this checkbox
Validations
Set field as unique
Select 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:
Tab
Field
Input
Settings
Display name
Answer
Settings
API ID
answer
Settings
Description
Write the answer here
Validations
Make field required
Select this checkbox
Click Add to save.
In this case, we're not enabling embedding because we don't need to insert content from other Q&A pairs or even from other models in our simple setup. Consider enabling embedding if your content can benefit from it.
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.
To create the component, navigate to the Schema builder and click +Add next to Components. Use the following information:
Field
Input
Display name
Reference FAQ Component
API ID
ReferenceFaqComponent
API ID Plural
ReferenceFaqComponents
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:
Tab
Field
Input
Settings
Display name
FAQ Section title
Settings
API ID
faqSectionTitle
Settings
Description
Write a section title here
Settings
Use as title field
Leave 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:
Tab
Field
Input
Define
Allow only one model to be referenced
Select this radio button.
Define
Model to reference
use the dropdown to select FAQ List Single
Define
Reference direction
Use the radio button to select One-way reference
Define
Relation cardinality
One to Many
Define
Allow multiple (…)
Select this checkbox
Configure
Display name
Q&A Pair
Configure
API ID
qAPair
Configure
Description
Link 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.
Pro Tip
You could also add the same set of fields to a model rather than a component to create FAQ landing pages. We explore this idea in our Simple FAQ Page recipe.