What are the prerequisites for building a multi-purpose page section component in Hygraph?
To build a multi-purpose page section component in Hygraph, you need a Hygraph account and an existing project. You can create a new project, clone a basic or complete cookbook project provided by Hygraph, or use your own existing project. For new users, the Getting Started Tutorial is recommended. Note: You may need to adjust the tutorial steps to fit your own project schema if using an existing project. Plan limits may also apply—see plan limits for details.
How can I quickly start using the multi-purpose section component in my Hygraph project?
You can start quickly by cloning one of Hygraph's prepared projects: the basic project (containing all base schema elements) or the complete cookbook (containing all page section recipes). These can be found at the links provided in the documentation. Alternatively, you can follow the step-by-step guide to build the component from scratch. Note: If you use your own project, you may need to adapt the schema to fit your requirements.
How long does it take to implement Hygraph for a new project?
Implementation time varies by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Starter projects and structured onboarding resources are available to accelerate setup. Note: Complex migrations or highly customized schemas may require additional time. Source
Features & Capabilities
What is the multi-purpose page section component in Hygraph?
The multi-purpose page section component is a modular, reusable schema element that allows you to add different section types (such as headers, footers, image galleries, and FAQs) to your content entries. It leverages modular component fields and enumerations to enable flexible page layouts. Note: The component structure must be defined in your schema before use. Source
What schema elements are used in the multi-purpose section component?
The component uses enumerations (predefined value lists), reusable components (templates with fields), modular component fields (allowing multiple components), and nested components (components within components). This structure enables flexible and scalable content modeling. Note: Overly complex nesting can increase schema management overhead. Source
What types of sections can be included in the multi-purpose section component?
You can include headers with notifications, header links, footer links, sectioned footers, FAQs, and styled image galleries. The allowed components are selected when configuring the modular component field. Note: The available section types depend on the components defined in your project schema. Source
How does the modular component field work in Hygraph?
The modular component field allows you to attach multiple components to a single field, enabling flexible content structures. You can select which components are allowed and whether multiple values are permitted. This approach supports dynamic page layouts and reusable content blocks. Note: Excessive use of modular fields can complicate content management for non-technical users. Source
Technical Documentation & Support
Where can I find technical documentation for schema components and enumerations?
Hygraph provides detailed documentation for schema components at Components Documentation and for enumerations at Enumerations Documentation. These resources cover setup, usage, and best practices. Note: Documentation may be updated; check for the latest guides before implementation.
What support resources are available for implementing page section components?
Support resources include the Hygraph community on Slack (slack.hygraph.com), structured onboarding, starter projects, and comprehensive documentation. Training resources such as webinars and how-to videos are also available. Note: For advanced troubleshooting, direct support may require a paid plan.
Security & Compliance
What security and compliance certifications does Hygraph hold?
Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications ensure adherence to international standards for information security and data privacy. Note: For the latest certification status, visit Hygraph's Secure Features page.
Use Cases & Benefits
Who can benefit from using the multi-purpose section component in Hygraph?
Developers, content creators, product managers, and marketing professionals can benefit from the multi-purpose section component. It enables flexible content modeling, reduces developer dependency, and supports scalable digital experiences. Note: Teams with highly specialized content needs may require custom schema adjustments.
What are the main benefits of using modular and reusable components in Hygraph?
Modular and reusable components allow for faster content updates, consistent page layouts, and reduced schema duplication. They support scalable content management and enable non-technical users to manage content efficiently. Note: Overuse of modularity can make content structures harder to navigate for some users.
Limitations & Considerations
What limitations should I consider when using the multi-purpose section component?
Limitations include plan limits on the number of components or entries, the need to adapt schema for existing projects, and potential complexity when nesting components deeply. Detailed limitations are not publicly documented; ask Hygraph sales or support for specifics relevant to your use case. Source
Performance & Integrations
How does Hygraph ensure high performance for content delivery?
Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. A read-only cache endpoint provides 3-5x latency improvement. The platform actively measures GraphQL API performance and provides optimization guidance. Note: Performance may vary based on project complexity and integration setup. Source
What integrations are available for use with Hygraph components?
Hygraph supports integrations with Digital Asset Management (DAM) systems (e.g., Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), and translation/localization tools (EasyTranslate). For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional configuration or paid plans.
This guide shows how to build a multi-purpose page section component that you can use to add a number of different section types to your content.
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.
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.
Take plan limits into consideration when adding a recipe to your own project.
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.
Path 1: Use this guide to create a multi-purpose section component that you can use in your project.
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.
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:
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 "Section" component.
In this guide, we will create a multi-purpose section component with a nested component field for links. Before we can build this, 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:
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.
Create the section component: We will build a section component that will contain all the other sections we brought into the project as part of a nested modular component field.
If you're already familiar with the creation of models & other schema elements, and only want to follow the parts of the tutorial related to the multi-purpose page section component, you can clone a project that we've prepared for you. It contains all the schema elements that you will use in step 2!
Now that we have all the schema elements that, both directly and indirectly, will be a part of our final multi-purpose section component, we'll go ahead and create it!
Multi-purpose section component
We'll click + Add next to Components and add it using this information:
Field
Input
Display Name
Section
API ID
Section
API ID Plural
Sections
We'll click Add component to save, and then we'll start adding instances to it.
We will start by adding a Single line text field from the right sidebar. Since all the sections we'll add to this component already have their own title fields, this field is only meant to be used as title field for the component 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:
Tab
Field
Input
Settings
Display Name
Section name
Settings
API ID
sectionName
Settings
Description
This field is used as title field only and won't be used as part of the content
Settings
Use as title field checkbox
Select 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 a Modular component field, so when we use it in a content entry, we will be able to select which component to include.
We'll find the Modular component field on the Add fields right sidebar, click on it, and use the following information:
Tab
Field
Input
Settings
Display Name
Blocks
Settings
API ID
blocks
Settings
Allow multiple values checkbox
Select this checkbox
Settings
Select allowed components
Use the dropdown to select the "Header with notification", "Header links", "Footer links", "Sectioned footer", "FAQ", and "Image gallery" components
We'll click Add to save.
Finally, since we already have a theme enumeration created in our project, we will add it as an enumeration field that will let us select a section theme when we use this component in a content entry:
We'll find the Enumeration field on the Add fields sidebar, and click Add on the field card.
We'll use the following information:
Tab
Field
Input
Settings
Display Name
Section theme
Settings
API ID
sectionTheme
Settings
Enumeration
Select "Theme" from the dropdown menu
We'll click Add to save.
This is how you create a multi-purpose page section component containing a number of different section types. Creating the section as a component, allows you to reuse the structure in different models in your project as if it were a template!
This is one way of creating a multi-purpose section using Hygraph. If you want to try out more section configurations, we have other page section types for you to look into!
This guide shows how to build a multi-purpose page section component that you can use to add a number of different section types to your content.
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.
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.
Take plan limits into consideration when adding a recipe to your own project.
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.
Path 1: Use this guide to create a multi-purpose section component that you can use in your project.
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.
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:
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 "Section" component.
In this guide, we will create a multi-purpose section component with a nested component field for links. Before we can build this, 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:
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.
Create the section component: We will build a section component that will contain all the other sections we brought into the project as part of a nested modular component field.
If you're already familiar with the creation of models & other schema elements, and only want to follow the parts of the tutorial related to the multi-purpose page section component, you can clone a project that we've prepared for you. It contains all the schema elements that you will use in step 2!
Now that we have all the schema elements that, both directly and indirectly, will be a part of our final multi-purpose section component, we'll go ahead and create it!
Multi-purpose section component
We'll click + Add next to Components and add it using this information:
Field
Input
Display Name
Section
API ID
Section
API ID Plural
Sections
We'll click Add component to save, and then we'll start adding instances to it.
We will start by adding a Single line text field from the right sidebar. Since all the sections we'll add to this component already have their own title fields, this field is only meant to be used as title field for the component 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:
Tab
Field
Input
Settings
Display Name
Section name
Settings
API ID
sectionName
Settings
Description
This field is used as title field only and won't be used as part of the content
Settings
Use as title field checkbox
Select 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 a Modular component field, so when we use it in a content entry, we will be able to select which component to include.
We'll find the Modular component field on the Add fields right sidebar, click on it, and use the following information:
Tab
Field
Input
Settings
Display Name
Blocks
Settings
API ID
blocks
Settings
Allow multiple values checkbox
Select this checkbox
Settings
Select allowed components
Use the dropdown to select the "Header with notification", "Header links", "Footer links", "Sectioned footer", "FAQ", and "Image gallery" components
We'll click Add to save.
Finally, since we already have a theme enumeration created in our project, we will add it as an enumeration field that will let us select a section theme when we use this component in a content entry:
We'll find the Enumeration field on the Add fields sidebar, and click Add on the field card.
We'll use the following information:
Tab
Field
Input
Settings
Display Name
Section theme
Settings
API ID
sectionTheme
Settings
Enumeration
Select "Theme" from the dropdown menu
We'll click Add to save.
This is how you create a multi-purpose page section component containing a number of different section types. Creating the section as a component, allows you to reuse the structure in different models in your project as if it were a template!
This is one way of creating a multi-purpose section using Hygraph. If you want to try out more section configurations, we have other page section types for you to look into!