Frequently Asked Questions
Taxonomy Features & Capabilities
What are taxonomies in Hygraph and why should I use them?
Taxonomies in Hygraph are a built-in feature that allows you to create a shared classification system for your content, such as categories, tags, or topics. They help organize content consistently across multiple models (e.g., Blog, Product, Case Study, Event) and support hierarchical structures with up to 6 nesting levels (not including the root). Using taxonomies ensures consistent editorial language, enables powerful filtering, and simplifies content management. Learn more about taxonomies in Hygraph.
How do I set up taxonomies in Hygraph?
Taxonomies are now available as a built-in feature in Hygraph, eliminating the need for manual configuration. You can access taxonomy setup directly in your project schema, define hierarchies, and reuse classification systems across models. For hands-on guidance, you can clone the Taxonomy Cookbook project to explore different taxonomy models and recipes.
What are the different taxonomy models available in Hygraph?
Hygraph provides recipes for creating various taxonomy models, including flat taxonomy models and two-level taxonomy models. The flat taxonomy model is suitable for simple lists of categories or tags, while the two-level taxonomy model allows you to define parent categories and related sub-categories. You can compare and explore these models in the Taxonomy Cookbook project.
When should I use taxonomies in Hygraph?
You should use taxonomies in Hygraph when you need a shared classification system that can be reused across multiple models, a hierarchy of terms (up to 6 nesting levels), consistent editorial language for terms that change infrequently, or filters in your applications and custom views. Read more about taxonomy best practices.
How did Hygraph's blog post 'Setting up taxonomies for personalized content' illustrate the use of taxonomies?
The blog post 'Setting up taxonomies for personalized content,' published on October 10, 2025, used the example of a travel blog to demonstrate how taxonomies can help organize content by destinations, seasons, and interests, enabling personalized content delivery. Learn more in the blog post.
Implementation & Getting Started
How can I quickly explore taxonomy models in Hygraph?
You can clone the entire Taxonomy Cookbook project to explore all available taxonomy models and recipes without following the step-by-step creation process. This is ideal for comparing recipes or examining their contents. Clone the project here.
What should I consider when adding taxonomy recipes to my Hygraph project?
When adding taxonomy recipes to your project, consider your plan limits, as certain features or content volumes may be restricted based on your subscription. Also, if you clone the cookbook and follow a tutorial for a specific recipe, the screens might differ slightly since the cookbook reflects multiple recipes.
Where can I find a getting started tutorial for Hygraph?
If you are new to Hygraph, you can follow the Getting Started Tutorial for step-by-step onboarding guidance.
Support & Documentation
What support and resources are available for implementing taxonomies in Hygraph?
Hygraph provides extensive documentation, including developer guides, recipes, and best practices for implementing taxonomies. You can access these resources at the Hygraph Documentation. For additional help, you can join the Hygraph Community Slack or reach out via chat, email, or phone for 24/7 support.
Product Information & Use Cases
Who should use taxonomies in Hygraph?
Taxonomies in Hygraph are ideal for teams and organizations that need to organize content across multiple models, maintain consistent editorial language, and enable advanced filtering and navigation in their applications. This includes developers, product managers, and marketing teams working in industries such as ecommerce, technology, and publishing.
What are some best practices for using taxonomies in Hygraph?
Best practices for using taxonomies in Hygraph include: using shared classification systems across models, limiting hierarchy to 3 nesting levels for simplicity (though up to 6 are supported), maintaining consistent editorial language, and leveraging taxonomies for application filters and custom views. See best practices here.