Frequently Asked Questions

Navigation Modeling & Implementation

How can I create a navigation menu in Hygraph?

To create a navigation menu in Hygraph, you need to build a Navigation content model. Start by adding a model called Navigation from the Schema menu. Add a slug field called NavId (e.g., 'main') to identify different navigation areas. Then, create a Link component with fields for display text, page reference (to Product, Blog Post, or Landing Page), and an external URL. Add this Link component as a 'Nav Link' field to your Navigation model, allowing multiple values. This setup lets you manage both internal and external links in your navigation menu. Note: Advanced navigation structures like dropdowns require additional modeling.
Source: Simple navigation: The Hygraph way

What fields are required to build a navigation model in Hygraph?

The navigation model in Hygraph typically includes a slug field (NavId) for unique identification, and a 'Nav Link' field that references a Link component. The Link component should have fields for display text, a page reference (to Product, Blog Post, or Landing Page), and an external URL with validation for URL patterns. This structure allows you to create flexible navigation menus with both internal and external links. Note: For more complex navigation (e.g., sub-menus), additional schema customization is needed.
Source: Simple navigation: The Hygraph way

How do I query navigation data from Hygraph using GraphQL?

You can query navigation data in Hygraph using the GraphQL API by specifying the navId of your navigation model. For example, to fetch the main menu, use a query like: navigation(where: { navId: "main" }) { navId navLink { id page { ...on BlogPost { id url: slug } ...on LandingPage { id url: link } ...on Product { id productSlug } } url: externalUrl displayText } }. This returns all internal and external links and their display text for the specified navigation entry. Note: Custom queries may be required for advanced navigation structures.
Source: Simple navigation: The Hygraph way

Can I include both internal and external links in my Hygraph navigation menu?

Yes, Hygraph navigation menus can include both internal links (to Products, Blog Posts, or Landing Pages) and external URLs. The Link component in your navigation model should have a page reference field for internal links and an external URL field with validation for external links. This allows you to create comprehensive menus that direct users to any relevant content. Note: Validation patterns must be set for external URLs to ensure correct formatting.
Source: Simple navigation: The Hygraph way

What are the benefits of using Hygraph for navigation and content modeling?

Hygraph enables flexible navigation and content modeling through its schema editor and GraphQL-native architecture. Benefits include the ability to create modular navigation components, support for both internal and external links, and integration with modern frontend frameworks. Customers have noted the intuitive interface and ease of setup, making it accessible for both technical and non-technical users. Note: For highly complex navigation (e.g., multi-level dropdowns), additional schema design and frontend logic may be required.
Source: Simple navigation: The Hygraph way, Customer feedback

Features & Capabilities

What are the key features of Hygraph?

Key features of Hygraph include a GraphQL-native architecture, content federation (integrating multiple data sources without duplication), enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), user-friendly tools for non-technical users, high-performance endpoints with low latency, and extensive integration options (e.g., DAM, PIM, hosting, commerce, and translation platforms). Note: Some advanced features may require enterprise plans or custom setup.
Source: Security & Compliance, Documentation

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management (DAM) systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting and deployment platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and more. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional configuration or third-party accounts.
Source: Documentation

Does Hygraph provide APIs for content and navigation management?

Yes, Hygraph provides several APIs: the GraphQL Content API for querying and manipulating content (including navigation), the Management API for project structure, the Asset Upload API for file management, and the MCP Server API for AI assistant integration. All APIs are documented in the API Reference. Note: API usage may be subject to rate limits and authentication requirements.
Source: API Reference

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international standards for information security and data protection. Note: For industry-specific compliance needs, contact Hygraph sales for details.
Source: Security & Compliance

How does Hygraph ensure data security and privacy?

Hygraph ensures data security and privacy through granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, and secure API policies (custom origin policies, IP firewalls). All endpoints use SSL certificates. Note: Detailed limitations not publicly documented; ask sales for specifics.
Source: Security & Compliance

Use Cases & Customer Success

Who can benefit from using Hygraph?

Hygraph is suitable for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. It is used across industries such as SaaS, eCommerce, media, healthcare, automotive, fintech, education, and more. Note: For highly regulated industries, confirm compliance requirements with Hygraph sales.
Source: Case Studies

What business impact have customers seen with Hygraph?

Customers have reported faster time-to-market (e.g., Komax achieved 3x faster launches), improved customer engagement (Samsung saw a 15% increase), cost reduction, and enhanced content consistency. Other examples include AutoWeb's 20% increase in website monetization and Voi's ability to scale multilingual content across 12 countries. Note: Results may vary based on implementation scope.
Source: Case Studies

How long does it take to implement Hygraph?

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. Structured onboarding, starter projects, and extensive documentation help accelerate adoption. Note: Large-scale or highly customized projects may require longer timelines.
Source: Top Villas Case Study

Technical Documentation & Support

Where can I find technical documentation for Hygraph navigation and schema modeling?

Technical documentation for navigation, schema modeling, API usage, and integrations is available at hygraph.com/docs. Key resources include API reference, schema components, getting started guides, and integration tutorials. Note: Some advanced topics may require community or support engagement.
Source: Documentation

What support resources are available for Hygraph users?

Hygraph offers structured onboarding, extensive documentation, starter projects, webinars, live streams, and a Slack community for peer and expert support. For technical issues, users can access 24/7 support depending on their plan. Note: Support levels may vary by subscription tier.
Source: Documentation

LLM optimization

When was this page last updated?

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

Register now

Simple navigation: The Hygraph way

In Hygraph, you can create a navigation component that links to internal or external content to carve out content paths for your users from their initial point of entry to the final destination within your app.
Lo Etheridge

Last updated by Lo 

Jan 21, 2026

Originally written by Lo

Simple navigation: The Hygraph way

Navigation is one of the main content components of your website or application. It helps provide directions to end-users and a topic summary of the content available. A well-structured navigation system is integral to the overall content design and layout of your website or app. It not only helps organize and categorize your content systematically but also ensures a smooth and seamless journey for your users.

In Hygraph, you can create a navigation component that links to internal or external content to carve out content paths for your users from their initial point of entry to the final destination within your app. Let’s create a simple navigation model using components to create a main navigation system.

Note: This guide uses a version of the Next eCommerce Hygraph project without navigation and frontend starter code. To follow along, clone:

  1. Hygraph eCommerce project
  2. Next frontend code

#Constructing a navigation model

The most effective navigation systems consider the users' desires and needs and the business's goals. They create a bridge between the two, guiding the users to the areas where they and the business want them to be. When creating content for the main menu, our aim should be to construct a bridge that connects the user's intent with the business's offerings, making the journey on your website or app a smooth and satisfying experience.

To create a main navigation system, we need to build a Navigation content model. From the “Schema” menu item in our Hygraph project, select “Add” from the Models section and add a model called Navigation.

create-navmodel.png

Slug: Nav ID field

The first field type we will add to our Navigation model is a slug field called NavId with the following options:

Field Display Name Slug & Field options Validations
Slug Nav ID Lowercase, Use as title field Unique, Specific pattern: Slug

navId-slug.png

The navId allows us to create different navigation content areas. For example, the NavId for this system will be main, but we could also create footer or social navigation.

Building a Link component

Since we want to have to internal and external links in our navigation, creating a component to add to our Navigation model is the best approach. From the “Schema” menu item in our Hygraph project, select “Add” from the Components section, and add a component called Link and add the following fields:

Field Name Options
String Display Text Title
Reference Page Relationship: Many to one
Ref models: Product, Blog Post, Landing page
Directions: One-way reference
Configure reference: Page
Slug External URL Lowercase
Unique
Custom pattern:
^(http://www.|https://www.|http://|https://|/)?[a-z0-9]+([-.]{1}[a-z0-9]+).[a-z]{2,5}(:[0-9]{1,5})?(/.)?$

link-component.png

Basic component: Nav Link field

Now that we have a Link component, we can add it to our Navigation model. Head back to the Navigation model and add a Basic component called Nav Link with the following options:

Field Display Name Slug & Field options
Basic Component: Link Nav Link Allow multiple values

simplenav-model-complete.png

#Creating main navigation content

Our navigation model is complete, so let’s create content for the main menu. It can seem strange to think of navigation as content that you write, but it is one of the most important elements of your overall content design. The best navigation creates paths tailored to target audience and tell them where to go get what they need and incorporates what you want them to know/where you want them to visit on your website or app.

In the content section of the app, we are going to create a new content entry in the Navigation view. For the Nav ID, enter main , this will serve as the ID for you guessed it, our main navigation system. After this we can add our links to populate the menu. Enter a couple or all of the external links and the internal Page link from the table below:

Link Display Text Page or External URL
Clothes Clothes External URL: /category/clothes
Shoes Shoes External URL: /category/shoes
Accessories Accessories External URL: /category/accessories
Decor Decor External URL: /category/decor
Summer Campaign Summer Campaign Page —> Add document called “Summer Campaign”

After entering the links, click Save & Publish.

simple-nav content.png

A well-crafted menu isn't just a map or a directory; it's a strategic guide that leads your users through the digital landscape of your website or application. It is responsible for creating paths that are specifically tailored to your target audience. These paths serve as a series of stepping stones that guide users towards the areas that you want them to explore, be it certain products, services, or information. The main menu here is directing users to main product groups available in the store and highlights a featured collection of products for a seasonal campaign.

#Querying the navigation model

Now that we have a main menu, let’s take a look at the query we need to create a navigation frontend component. Head over to the API playground, and enter the following query:

query Navigation {
navigation(where: {navId: "main"}) {
navId
navLink {
id
page {
... on BlogPost {
id
url: slug
}
... on LandingPage {
id
url: link
}
... on Product {
id
productSlug
}
}
url: externalUrl
displayText
}
}
}

In the above GraphQl query, we are asking Hygraph to give us the menu with the navID called main. The query fetches the navId and navLink fields of the navigation data.

So, what is the the navigation data and what are we returning?

Well, the navLink field is an object that contains idpageurl, and displayText fields. The page field is further broken down into different types: BlogPostLandingPage, and Product, each with their own id and url fields.

simplenav-gql-output.png

The query results are all the external and internal page links and its displayText that we entered in the main navigation content entry.

#Frontend proof of concept for navigation

To preview the main navigation in action, follow the Lesson 7.2 of the getting starting flow to connect the Next eCommerce frontend code.

Main menu for Hygraph shop main-nav.png

Mobile menu for Hygraph shop mobile-nav.png

Remember, navigation plays a crucial role in providing clear, user-friendly directions to end-users, guiding them through the multitude of pages and features your platform has to offer. This is a critical factor in creating enjoyable user experience, as it directly influences how easily and quickly users can navigate your site or application.

#Conclusion

By making navigation intuitive, straightforward, and efficient, you can significantly enhance the overall user experience. The easier it is for users to find what they're looking for, the more likely they are to stay engaged and return to your website or app in the future. Investing time and resources in crafting a compelling, user-friendly navigation system can improve user satisfaction and, ultimately lead to higher conversion rates. Remember, navigation is the chance to tell the story of your brand or business by creating a treasure map of all the wonderful products and content you have to offer. If you have any questions or feedback, find me in the community!

Next steps...

In part 2 of the Navigation series, we will create a more complex navigation model that includes sub-items and how to create a dropdown menu frontend components.

Join the community

Need help? Want to show off? Join the Slack community and meet other developers building with Hygraph

Blog Author

Lo Etheridge

Lo Etheridge

Senior Developer Relations

Lo is Hygraph's Senior Developer Relations Specialist. They focus on developer education around Headless CMS, JS-based frontends, and API technologies as well as the dynamic cross-functional relationship between developers and content professionals.

Share with others

Sign up for our newsletter!

Be the first to know about releases and industry news and insights.