What is Hygraph's Schema Builder and how does it work?
The Schema Builder in Hygraph is a low-code interface that allows you to define the structure of your content API. You can create content types, set up their relationships, add reusable components, and manage stages. The builder supports various field types such as text, assets, numbers, and maps, and enables you to connect content models for faster scaling. This makes it easy to build highly modular content and visualize relationships between models. Learn more about Schema Builder.
How does Hygraph's schema builder benefit developers and content teams?
Hygraph's no-code schema builder allows developers to build content models with flexibility and minimal onboarding. For content teams, it provides an intuitive, user-friendly interface that makes content creation and management seamless, even for non-technical users. This reduces reliance on developers and accelerates project delivery. Source
What are the main components of a learning platform schema in Hygraph?
A learning platform schema in Hygraph typically consists of three levels: Course (top-level), Module (mid-level), and Lesson (low-level). Courses contain modules, modules contain lessons, and lessons can include videos, rich text, and other interactive elements. This structure allows for scalable, flexible, and future-proof content modeling. Source
What types of fields can be used in Hygraph content models?
Hygraph content models support a variety of field types, including string fields (for titles), slug fields (for URLs), rich text fields (for formatted content), boolean fields (for features like locking modules), reference fields (to link models), and custom fields such as video URLs. This flexibility enables detailed and structured content modeling for complex use cases. Source
Does Hygraph support integrations with other platforms?
Yes, Hygraph offers a wide range of integrations, including hosting and deployment (Netlify, Vercel), eCommerce (BigCommerce, Shopify), localization (Lokalise, Crowdin), digital asset management (Cloudinary, AWS S3), personalization (Ninetailed), and AI (AltText.ai). For a full list, visit the Hygraph Integrations page.
Does Hygraph provide an API for content management?
Yes, Hygraph provides a powerful GraphQL API that allows you to fetch and manage content efficiently. You can learn more about it at the Hygraph API Reference.
Use Cases & Benefits
How can Hygraph be used to build a learning platform?
Hygraph enables you to model and manage educational content by structuring courses, modules, and lessons. You can create free and paid content, embed videos, and add interactive elements. The platform's flexibility allows educators to monetize their expertise and deliver high-quality educational experiences. For a step-by-step guide, see Building a learning platform: The schema.
Who can benefit from using Hygraph?
Hygraph is ideal for developers, IT decision-makers, content creators, project managers, agencies, and technology partners. It is especially beneficial for modern software companies, enterprises seeking to modernize their tech stack, and brands aiming to scale digital experiences across geographies. Source
What business impact can customers expect from using Hygraph?
Customers can expect significant business impacts such as time savings, faster speed-to-market, improved customer experience, and operational efficiency. For example, Komax achieved a 3X faster time to market, and Autoweb saw a 20% increase in website monetization using Hygraph. See more success stories.
What industries are represented in Hygraph's case studies?
Hygraph's case studies span industries such as food and beverage, consumer electronics, automotive, healthcare, travel and hospitality, media and publishing, eCommerce, SaaS, marketplace, education technology, and wellness and fitness. See all case studies.
Pain Points & Solutions
What problems does Hygraph solve for organizations?
Hygraph addresses operational pains (like reliance on developers for content updates and clunky user experiences), financial pains (high operational costs, slow speed-to-market, expensive maintenance), and technical pains (boilerplate code, overwhelming queries, cache problems). Its GraphQL-native architecture, content federation, and scalability help organizations modernize their tech stack and streamline workflows. Learn more.
How does Hygraph solve the pain points of different user personas?
For developers, Hygraph reduces boilerplate code and streamlines query management. For content creators and project managers, it offers an intuitive interface for independent content updates. For business stakeholders, it lowers operational costs, supports scalability, and accelerates speed-to-market. See persona-specific solutions.
What KPIs and metrics are associated with the pain points Hygraph solves?
Key metrics include time saved on content updates, system uptime, consistency in content across regions, user satisfaction scores, reduction in operational costs, time to market, maintenance costs, and scalability metrics. For more details, see the Hygraph blog on CMS KPIs.
Pricing & Plans
What is Hygraph's pricing model?
Hygraph offers a free forever Hobby plan, a Growth plan starting at $199/month, and custom Enterprise plans. For full details, visit the Hygraph pricing page.
Technical Requirements & Documentation
Where can I find technical documentation for Hygraph?
Comprehensive technical documentation is available at the Hygraph Documentation page, covering everything from getting started to advanced integrations.
How easy is it to get started with Hygraph?
Hygraph is designed for quick onboarding. Users can sign up for a free-forever account and access resources like documentation, video tutorials, and onboarding guides. Even non-technical users can start using it right away, as noted by customer feedback. Get started here.
How long does it take to implement Hygraph?
Implementation is fast and straightforward. For example, Top Villas launched a new project in just 2 months from the initial touchpoint. The platform's intuitive interface and comprehensive resources help accelerate deployment. See the Top Villas case study.
Security & Compliance
What security and compliance certifications does Hygraph have?
Hygraph is SOC 2 Type 2 compliant, ISO 27001 certified, and GDPR compliant. These certifications ensure enterprise-grade security and data protection. For more details, visit the Hygraph Security Features page.
How does Hygraph ensure data security and compliance?
Hygraph provides robust security features such as SSO integrations, audit logs, encryption at rest and in transit, and sandbox environments. These measures protect sensitive data and help organizations meet regulatory standards. Learn more about security.
Support & Implementation
What customer support options are available with Hygraph?
Hygraph offers 24/7 support via chat, email, and phone. Enterprise customers receive dedicated onboarding and expert guidance. All users have access to detailed documentation, video tutorials, and a community Slack channel. Contact Hygraph support.
What training and onboarding resources does Hygraph provide?
Hygraph provides onboarding sessions for enterprise customers, training resources such as video tutorials, documentation, webinars, and access to Customer Success Managers for expert guidance. Learn more about onboarding.
Customer Success & Proof
Who are some of Hygraph's customers?
Notable customers include Sennheiser, Holidaycheck, Ancestry, Samsung, Dr. Oetker, Epic Games, Bandai Namco, Gamescom, Leo Vegas, and Clayton Homes. See all customer stories.
Can you share specific 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 with a scalable platform, and Dr. Oetker enhanced their digital experience using MACH architecture. Read more success stories.
Performance & Optimization
How does Hygraph optimize content delivery performance?
Hygraph is designed for optimized content delivery, ensuring rapid distribution and responsiveness. This improves user experience, engagement, and search engine rankings by reducing bounce rates and increasing conversions. Learn more about performance.
In this article, we will be discussing how to create a comprehensive and effective model for a learning platform that allows educators to create courses.
Written by Bryan
on Mar 27, 2023
One of our main goals is to establish a platform that not only provides students with high-quality educational content, but also allows educators to monetize their expertise by offering premium courses behind a payment or login gate.
To achieve this, we will need to carefully plan and organize our content flow. This involves identifying the key topics and themes that will be covered in our courses and structuring them in a logical and coherent manner. We will also need to consider the different types of media that will be used to deliver the content, such as videos, text, and interactive exercises.
Once we have established a solid content flow, we can move on to creating the content model. This is where we will design the structure and format of the courses themselves. We will need to consider factors such as the length and depth of each course, the level of interactivity and engagement required, and the overall learning objectives. We will also need to ensure that our model is scalable and can accommodate a wide range of courses and topics.
Editor's note: This is the first article in an on-going series for creating and extending this learning platform.
In order to create an effective content model, it's important to first have a thorough understanding of our business goals. We want to not only educate our users, but also encourage them to purchase our courses. To accomplish this, we need to ensure that the educational flow is seamless and intuitive, with various opportunities for users to explore and engage with the content.
One way to achieve this is by providing users with a taste of the content through various means, such as free previews or sample lessons. In this case, we’re going to create the ability to give certain groups of lessons away for free and have users pay to unlock others.
Once we have a clear understanding of our business case and user needs, we can begin to map out the flow of content through the platform.
When it comes to modeling content for a learning platform, there are several approaches available. While a single document with a rich text field would be a simple solution, it would be less flexible when it comes to modifying and remixing content. On the other hand, a collection of lesson documents might seem more versatile, but it would present limitations when it comes to implementing our future payment functionality. In order to create a content model that can be adapted and modified with ease, we propose to develop three levels of content: a top-level course, a collection of lessons called a module, and finally the individual lessons.
The top-level content model will consist of courses, each with a unique identifier and a set of metadata that describes it. Each course will be composed of several modules, with each module containing a specific theme or topic. The mid-level content model will consist of a module that contains individual lessons. The module level is where we can implement our gating functionality to create a smooth editor experience. Each lesson will be structured in a consistent format to ensure a smooth learning experience across all subjects. The lesson content model will consist of a video and a rich text field, but can be extended in the future to create interactive components such as quizzes or supporting downloads like cheat sheets.
By creating these three levels of content, we can provide a flexible and scalable solution that can be easily modified and expanded upon as needed. Additionally, this approach will allow us to develop and implement our future payment functionality with minimal disruption to our content model. Overall, this approach will ensure that our learning platform is adaptable, scalable, and future-proof.
The course will be the main element and create the primary structure of the course, including a long-form description and introduction. The course should also have the ability to display and reorder modules.
String field: Title
The title field is a string field that should be marked as a "title" field for Hygraph. This will allow the title to display in the content table.
Slug field: Slug
Next, we need a slug based on the title. This will equate to the URL part in our application. The slug needs to be unique and use a "Slug template" of {title} to properly pull the title. Slugs should also be all lowercase.
Rich Text Field: Body
For the body of each course, we'll want rich text to add styled and structured content to the introduction of the course. This is the basic Rich Text field from Hygraph, but we want to enable embedding and allow for embedding assets to let editors add images to the body of a course.
Reference Field: Modules
Finally, the course needs a way to reference modules. You'll need to add the Module model in the next section before referencing — you can only reference to a model that already exists. Once the module model is set up, we'll use a Reference field. The reference field can allow references to a single model or multiple. In this case, we just want to reference the Module model and allow multiple modules per course. Once those options are selected, we then set up the field data — display name and id — and the way the field will appear on the referenced item (to allow for easier editing on both sides).
A module is a collection of lessons. The module is where the locking mechanism will be placed. If a course is fully paid, every module can be locked. However, if an educator wishes to give specific sections for free, only certain sections can be locked. The only new field type in this section is the "isLocked" boolean field.
Fields:
This is where the meat of the educational content lives. In this example, we're assuming an external video, such as a YouTube video, but the lesson could be any format.
Fields:
From here, we can start working toward implementing this with a frontend. In the next article of this series, we’ll take the API generated by Hygraph from this content model and implement a frontend with Next.js.
Blog Author
Bryan Robinson
Head of Developer Relations
Bryan is Hygraph's Head of Developer Relations. He has a strong passion for developer education and experience as well as decoupled architectures, frontend development, and clean design.
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.