Frequently Asked Questions

Product Information & Getting Started

What is Hygraph and how does it relate to React projects?

Hygraph is a GraphQL-native Headless CMS designed to help teams build better digital experiences. In React projects, Hygraph serves as a backend for managing and delivering content via APIs, enabling developers to fetch and display dynamic data efficiently. For example, in the cocktails app featured in the guide, Hygraph is used to store cocktail details and deliver them to the React frontend using GraphQL queries. (Learn more)

How do I get started with Hygraph for my React application?

To get started, sign up for a free developer account at Hygraph Signup. You can follow the Getting Started tutorial and use the API playground to experiment with queries. For React, you can create schemas in Hygraph, fetch data using GraphQL, and integrate it into your app as shown in the cocktails app example. No technical onboarding is required for non-developers, and developers benefit from structured onboarding and extensive documentation. (Source)

What resources or prerequisites do I need to use Hygraph with React?

You need a Hygraph account (free to create), basic knowledge of HTML, CSS, JavaScript, and React, and Node.js with npm or yarn installed. For frontend integration, a code editor and a hosting platform like Netlify may be useful. Hygraph provides comprehensive documentation and onboarding resources to help you get started. (Source)

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers Smart Edge Cache for fast content delivery, Content Federation to integrate data from multiple sources, advanced Rich Text formatting, Custom Roles for granular access control, Project Backups, and developer-friendly APIs. It supports seamless integration with eCommerce, localization, and other systems, and is SOC 2 Type 2, ISO 27001, and GDPR compliant. (Source)

Does Hygraph provide APIs for content management and integration?

Yes, Hygraph provides GraphQL Content API for querying and managing content, GraphQL Management API for schema changes, Public API for programmatic access, and supports both REST and GraphQL APIs for integration with external systems. (Documentation)

What integrations are available with Hygraph?

Hygraph integrates with digital asset management (Aprimo, AWS S3, Bynder, Cloudinary, Mux, Scaleflex Filerobot), hosting (Netlify, Vercel), eCommerce (BigCommerce, commercetools, Shopify), localization (Lokalise, Crowdin, EasyTranslate, Smartling), personalization (Ninetailed), AI (AltText.ai), and more. (Integrations Documentation)

How does Hygraph perform in terms of speed and scalability?

Hygraph leverages state-of-the-art caching and robust edge services for low latency and high read-throughput. It supports rapid content delivery, 7X higher content velocity, 125% traffic growth, and 120% more website clicks. Hygraph is used in 40+ global markets and by 100+ stakeholders. (Source)

Use Cases & Benefits

Who can benefit from using Hygraph?

Hygraph is designed for developers, IT decision-makers, content creators, project managers, agencies, and technology partners. It is valuable for modern software companies, enterprises, brands scaling across geographies, and organizations re-platforming from legacy solutions. (Source)

What business impact can I expect from using Hygraph?

Customers report up to 3X faster time-to-market (Komax), 20% increase in website monetization (AutoWeb), 15% higher customer engagement (Samsung), 7X higher content velocity, and 125% traffic growth. Hygraph supports content management across 40+ global markets and enables rapid scaling and improved operational efficiency. (Case Studies)

What industries are represented in Hygraph's customer case studies?

Industries include eCommerce (Si Vale, Vision Healthcare), Automotive (AutoWeb), Healthcare & Fitness (Fitfox, Vision Healthcare), Consumer Electronics (Samsung), Media & Publishing (Telenor), Food & Beverage (Dr. Oetker, K+S), Travel & Hospitality (HolidayCheck), Engineering (Komax Group), Government (Statistics Finland), and SaaS (Bellhop). (Source)

Can you share specific customer success stories using Hygraph?

Yes. Komax achieved 3X faster time-to-market and managed 20,000+ product variations in 40+ markets. Samsung saw a 15% increase in customer engagement. Dr. Oetker ensured global consistency with MACH architecture. HolidayCheck improved workflow efficiency by reducing developer bottlenecks. Sennheiser increased e-commerce conversions by 136.7% in 4 months. Stobag improved online revenue share from 15% to 70%. (Read more)

Ease of Use & Implementation

How easy is it to implement Hygraph and start using it?

Hygraph is recognized as the #1 easiest to implement headless CMS. For example, Top Villas launched a new project in just 2 months. Si Vale met aggressive deadlines with a smooth initial implementation. Non-technical users find the UI intuitive and logical, and developers can start immediately with the API playground. (Source)

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

Customers praise Hygraph's intuitive editor UI, logical workflows, and accessibility for non-technical users. The platform is described as super easy to set up and use, with streamlined collaboration between content editors and developers. Customization features are highly rated, and most reviews express positive sentiments about user-friendliness. (Source)

Pain Points & Problems Solved

What problems does Hygraph solve for businesses?

Hygraph eliminates operational inefficiencies by allowing non-technical users to update content, resolves legacy tech stack issues, and streamlines workflows. It reduces operational costs, accelerates speed-to-market, and simplifies integration. Technical challenges like evolving schemas, cache issues, and complex GraphQL endpoints are addressed, improving editorial autonomy and reducing engineering resource costs. (Source)

What pain points do customers commonly express before using Hygraph?

Customers often face bottlenecks due to developer dependency for content updates, outdated legacy systems, misalignment in global marketing teams, clunky user experiences, high operational costs, slow speed-to-market, limited integration, and technical issues with schemas and GraphQL endpoints. Hygraph addresses these challenges with its modern, flexible platform. (Source)

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure enhanced security, data protection, and adherence to global standards. (Source)

How does Hygraph ensure data security and compliance?

Hygraph provides granular permissions, audit logs, encryption at rest and in transit, SSO integrations, automatic backups, and dedicated hosting options. Enterprise-grade compliance features include custom SLAs, IT security reviews, and penetration testing. Security incidents can be reported, and a public security report is available. (Security Report)

Support & Implementation

What customer service and support options are available after purchasing Hygraph?

Hygraph offers 24/7 support via chat, email, and phone. Enterprise customers receive SLAs for critical issues (resolved in less than an hour), onboarding assistance, a dedicated Customer Success Manager, extensive documentation, a community Slack channel, Intercom chat, and training resources including webinars and live streams. (Source)

What training and technical support is available to help customers get started?

Hygraph provides onboarding support (introduction call, account provisioning, business/technical/content kickoffs), comprehensive documentation, regular technical training sessions, webinars, hands-on guidance, and consultation on content strategy, localization, and migrations. 24/7 technical support is available via chat, email, phone, and Slack. (Documentation)

How does Hygraph handle maintenance, upgrades, and troubleshooting?

Hygraph's cloud-based infrastructure handles all maintenance, server updates, security patches, and performance optimizations. Upgrades are automatic, and troubleshooting is supported by audit logs, monitoring, and performance reporting. Customers have access to 24/7 support and extensive documentation for troubleshooting. (Source)

Technical Documentation & Resources

Where can I find technical documentation for Hygraph?

Comprehensive technical documentation, API references, guides on content workflows, webhooks, and interactive API playgrounds are available at Hygraph Documentation. These resources support both technical and non-technical users in exploring and utilizing Hygraph effectively.

Customer Proof & Logos

Who are some of Hygraph's customers?

Hygraph is trusted by leading brands including Sennheiser, HolidayCheck, Ancestry, JDE, Dr. Oetker, Ashley Furniture, Lindex, Hairhouse, Komax, Shure, Stobag, Burrow, G2I, Epic Games, Bandai Namco, Gamescom, Leo Vegas, Codecentric, Voi, and Clayton Homes. (Case Studies)

Meet Hygraph AI Agents - Your Autonomous Teammates

A complete guide to routing in React

Learn how to perform routing in React using React router, as well as the various aspects of routing and how React router handles them.
Aagam Vadecha

Last updated by Aagam 

Jul 19, 2024

Originally written by Joel

A complete guide to routing in React

React is an open-source frontend JavaScript framework that allows developers to create websites and user interfaces using UI components and single-page applications. Routing is one of the most important features we always want to implement when developing these applications.

Routing redirects users to different pages based on their actions or requests. In React routing, you'll use an external library called React router, which can be challenging to configure if you need help understanding how it works.

In this article, we will show you how to perform routing in React using a React router. Learn the various routing aspects and how React router handles them, such as dynamic routing, programmatic navigation, no-matching routes, etc.

#Getting started

To fully comprehend and follow this guide, we would create an application that properly illustrates all aspects of navigation with appropriate use cases. We would create/use a cocktails app that retrieves data from Hygraph via GraphQL. This application, which can be accessed via this live link, uses all aspects of routing covered in this guide.

The Hygraph schema for a 'Cocktail' content model, showing the 'slug' field used for dynamic routing in React

Editor's Note

Note: This guide only covers routing; however, the aspect of creating a schema on Hygraph and how we consumed the data will not be covered; notwithstanding, here is a link to the source code, and I have also included a picture of what the schema looks like in this article.

Prerequisite

You should have the following to follow along with this guide and code:

  • A fundamental understanding of HTML, CSS, and JavaScript
  • Some experience or knowledge of React
  • Node and npm or yarn installed on your machine
  • Set up a React Application using Create React App

#Adding React router to our app

How to install React router

As previously stated, React makes use of an external library to handle routing; however, before we can implement routing with that library, we must first install it in our project, which is accomplished by running the following command in your terminal (within your project directory):

npm install react-router-dom

After successfully installing the package, we can set up and configure the React router for our project.

The Product Launch That Redefines Headless CMS

See how Hygraph uses AI to drive content speed and precision.

How to setup React router

To configure React router, navigate to the index.js file, which is the root file, and import BrowserRouter from the react-router-dom package that we installed, wrapping it around our App component as follows:

// index.js
import React from 'react';
import ReactDOM from 'react-dom/client';
import { BrowserRouter } from 'react-router-dom';
import App from './App';
const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(
<React.StrictMode>
<BrowserRouter>
<App />
</BrowserRouter>
</React.StrictMode>
);

#How to configure routes in React

We have now successfully installed and imported React router into our project; the next step is to use React router to implement routing. The first step is configuring all of our routes (all the pages/components we want to navigate).

We would first create those components, in our case, three pages: the Home page, the About Page, and the Products Page. This GitHub repository contains the content for these pages. Once those pages are properly configured, we can now set up and configure our routes in the App.js file, which serves as the foundation for our React application:

// App.js
import { Routes, Route } from 'react-router-dom';
import Home from './Pages/Home';
import About from './Pages/About';
import Products from './Pages/Products';
const App = () => {
return (
<>
<Routes>
<Route path="/" element={<Home />} />
<Route path="/products" element={<Products />} />
<Route path="/about" element={<About />} />
</Routes>
</>
);
};
export default App;

We can see in the above code that we imported Routes and Route components from react-router-dom and then used them to declare the routes we want. All Routes are wrapped in the Routes tag, and these Routes have two major properties:

  • path: As the name implies, this identifies the path we want users to take to reach the set component. When we set the path to /about, for example, when the user adds /about to the URL link, it navigates to that page.

  • element: This contains the component that we want the set path to load. This is simple to understand, but remember to import any components we are using here, or else an error will occur.

Editor's Note

We created a folder (Pages) to keep all page components separate from actual components.

When we go to our browser and try to navigate via the URL, it will load whatever content we have on such pages.

Adding a navigation bar

Let us now create a standard Navigation bar component that can be used to navigate inside our application.

First, create the Navbar component.

// component/NavBar.js
import { NavLink } from "react-router-dom";
const NavBar = () => {
return (
<nav>
<ul>
<li>
<NavLink to="/">Home</NavLink>
</li>
<li>
<NavLink to="/about">About</NavLink>
</li>
<li>
<NavLink to="/products">Products</NavLink>
</li>
</ul>
</nav>
);
};
export default NavBar;

The NavLink component from react-router-dom is a special component that helps you navigate different routes using the to prop. The NavLink component also knows whether the route is currently "active" and adds a default active class to the link. We can use this class in our CSS to define some styling for active links, as shown below:

// index.css
ul li a {
color: #000;
}
ul li a:hover {
color: #00a8ff;
}
ul li a.active {
color: #00a8ff;
}

Also, we can assign our custom classes instead of using the default active class. The NavLink component gives us access to properties like isActive, which can be used like this.

...
<li>
<NavLink
to="/"
className={({ isActive }) => {
return isActive ? "active-link" : "";
}}
>
Home
</NavLink>
</li>
...

Finally, let us use the Navbar component inside our App.

// App.js
import NavBar from "./Components/Navbar";
import { Routes, Route } from "react-router-dom";
const App = () => {
return (
<>
<NavBar />
<Routes>
...
</Routes>
</>
);
};
export default App;

How to fix No Routes Found Error

When routing, a situation may cause a user to access an unconfigured route or a route that does not exist; when this occurs, React does not display anything on the screen except a warning with the message "No routes matched location."

This can be fixed by configuring a new route to return a specific component when a user navigates to an unconfigured route as follows:

// App.js
import { Routes, Route } from 'react-router-dom';
import NoMatch from './Components/NoMatch';
const App = () => {
return (
<>
<Routes>
// ...
<Route path="*" element={<NoMatch />} />
</Routes>
</>
);
};
export default App;

In the preceding code, we created a route with the path * to get all non-configured paths and assign them to the attached component.

Editor's Note

We created a component called NoMatch.js, but you can name yours whatever you want to display 404, page not found, on the screen, so users know they are on the wrong page. We can also add a button that takes the user to another page or back, which leads us to programmatic navigation.

#How to navigate programmatically in React

Programmatic navigation is the process of navigating/redirecting a user as a result of an action on a route, such as a login or a signup action, order success, or when he clicks on a back button.

Let's first look at how we can redirect to a page when an action occurs, such as when a button is clicked. We accomplish this by adding an onClick event, but first, we must create the route in our App.js file. After that, we can import the useNavigate hook from the react-router-dom and use it to navigate programmatically as follows:

// Products.js
import { useNavigate } from 'react-router-dom';
const Products = () => {
const navigate = useNavigate();
return (
<div className="container">
<div className="title">
<h1>Order Product CockTails</h1>
</div>
<button className="btn" onClick={() => navigate('order-summary')}>
Place Order
</button>
</div>
);
};
export default Products;

Editor's Note

We already created a route with the path order-summary, so when this button is clicked, the user is automatically navigated to the orderSummary component attached to this route.
<button className="btn" onClick={() => navigate(-1)}>
Go Back
</button>

Ensure you already have the hook imported and instantiated as we did earlier else this won’t work.

#How to implement dynamic routing with React router

We created three files in our pages folder earlier to implement routing, one of which was the products component, which we will populate with Hygraph content. We created a schema in Hygraph to receive cocktail details, and this is how it looks:

your content model in hygraph

We then filled it in with cocktail specifics. We will now use GraphQL to retrieve these data so that we can consume them in our React project. This is how the products page appears:

// Products.js
import { useState, useEffect } from "react";
import { useNavigate } from "react-router-dom";
import { getAllCocktails } from "../api";
import ProductCard from "../Components/ProductCard";
const Products = () => {
const [products, setProducts] = useState([]);
const navigate = useNavigate();
useEffect(() => {
const fetchProducts = async () => {
const { cocktails } = await getAllCocktails();
setProducts(cocktails);
};
fetchProducts();
}, []);
return (
<div className="container">
<button className="btn" onClick={() => navigate(-1)}>
Go Back
</button>
<div className="title">
<h1>CockTails</h1>
</div>
<div className="cocktails-container">
{products.map((product) => (
<ProductCard product={product} />
))}
</div>
</div>
);
};
export default Products;
// components/ProductCard.js
import { Link } from "react-router-dom";
const ProductCard = ({ product }) => {
if (!product) {
return null;
}
return (
<div key={product.id} className="cocktail-card">
<img src={product.image.url} alt="" className="cocktail-img" />
<div className="cocktail-info">
<div className="content-text">
<h2 className="cocktail-name">{product.name}</h2>
<span className="info">{product.info}</span>
</div>
<Link to={`/products/${product.slug}`}>
<div className="btn">View Details</div>
</Link>
</div>
</div>
);
};
export default ProductCard;

Editor's Note

You can learn more about React and Hygraph here.

We fetched our content from Hygraph in the preceding code; if you already created your own schema, you can simply change the Endpoint URL and possibly the schema name if you gave it a different name.

Editor's Note

We added a button on each cocktail card so that a user can click it to view more details about each cocktail, but this would be done dynamically because we can create different components for each cocktail, which would be stressful if we had more than 5 different cocktails. Dynamic routing comes into play here.

We added a Link and used string interpolation to dynamically attach the slug of each product to the path, so we can get the slug and use it to get the data to show.

Let us now put dynamic routing into action.

The first step would be to create the component that we want to render dynamically, and for that we would create a ProductDetials.js file where we would dynamically fetch details of each product based on the slug passed through the URL, but for now we can just place dummy data into the component like this:

// ProductDetails.js
const ProductDetails = () => {
return (
<div className="container">
<h1>Products Details Page</h1>
</div>
);
};
export default ProductDetails;

We can now proceed to create a route to handle dynamic routing in our App.js file this way:

// App.js
import { Routes, Route } from 'react-router-dom';
// ...
import ProductDetails from './Pages/ProductDetails';
const App = () => {
return (
<>
<Routes>
// ...
<Route path="/products/:slug" element={<ProductDetails />} />
</Routes>
</>
);
};
export default App;

Editor's Note

We used slug, which can be anything, but this route will match any value and display the component as long as the pattern is the same, for example, http://localhost:3000/products/cocktail will show the ProductDetails component.

So far, we've dealt with the first part of dynamic routing. We must now obtain the parameter passed through the URL in order to dynamically query the data for the specific cocktail. This will be accomplished through the use of urlParams.

How to use URL params to handle dynamic routing

We will import the useParams hook into the ProductDetails component so that we can use it to get the URL parameter and then use that parameter to query our data from Hygraph via GraphQL.

// ProductDetails.js
import { useState, useEffect } from "react";
import { useNavigate, useParams } from "react-router-dom";
import { getProductBySlug } from "../api";
const ProductDetails = () => {
const [product, setProduct] = useState([]);
const navigate = useNavigate();
// Fetch slug from route parameters
const { slug } = useParams();
useEffect(() => {
const fetchProduct = async () => {
const { cocktail } = await getProductBySlug(slug);
setProduct(cocktail);
};
fetchProduct();
}, [slug]);
return (
<div className="container">
// ...Product Details template
</div>
);
};
export default ProductDetails;

At this point, we have successfully been able to get the URL param passed, let’s now make use of this slug to fetch data from Hygraph using GraphQL:

At this point, we have successfully implemented dynamic routing.

#How to implement lazy loading with React router

We've already seen how to create routes and implement routing with React router; now let's look at how to lazy load routes with React router.

Lazy loading is a technique in which components that are not required on the home page are not loaded until a user navigates to that page, allowing our application to load faster than having to wait for the entire app to load at once. This contributes to improved performance, which leads to a positive user experience.

To implement lazy loading, simply go to App.js and wrap our routes with the Suspense component, along with a fallback props that are rendered on the screen until the component loads:

// App.js
import { lazy, Suspense } from 'react';
import { Routes, Route } from 'react-router-dom';
import NavBar from './Components/NavBar';
const Home = lazy(() => import('./Pages/Home'));
const About = lazy(() => import('./Pages/About'));
const Products = lazy(() => import('./Pages/Products'));
const ProductDetails = lazy(() => import('./Pages/ProductDetails'));
const NoMatch = lazy(() => import('./Components/NoMatch'));
const App = () => {
return (
<>
<NavBar />
<Suspense fallback={<div className="container">Loading...</div>}>
<Routes>
<Route path="/" element={<Home />} />
<Route path="/about" element={<About />} />
<Route path="/products" element={<Products />} />
<Route path="/products/:slug" element={<ProductDetails />} />
<Route path="*" element={<NoMatch />} />
</Routes>
</Suspense>
</>
);
};
export default App;

Editor's Note

We wrapped the routes with the Suspense component, and it’s important for you to know that the fallback props can hold a component.

#Conclusion

We learned about routing and how to implement it in our React application in this guide. It is critical to understand that the React router is what allows us to perform single-page routing without reloading the application.

Try Hygraph for free

Build limitless solutions rapidly with our GraphQL-native API-first approach

Blog Authors

Share with others

Sign up for our newsletter!

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