What changes have been made to content duplication in Hygraph?
Recent improvements to content duplication in Hygraph include: changed behavior for duplicating relational fields to avoid breaking changes, easier access to the duplication button, clearer visual cues when an entry is duplicated, warnings to prevent accidental loss of duplicated content, and fixes for several small bugs. Note: Users must now re-reference entries for certain relational fields after duplication to avoid broken content. Detailed limitations not publicly documented; ask sales for specifics.
How does Hygraph handle relational fields during content duplication?
When duplicating content entries with one-to-many or one-way relational fields, Hygraph now detaches referenced entries from the duplicated entry to prevent breaking changes. Users will need to reference these entries again after duplication. This approach ensures that duplicated entries do not cause content inconsistencies. Note: This may require additional steps for users managing complex relational content. Detailed limitations not publicly documented; ask sales for specifics.
Where can I find the content duplication button in the new Hygraph interface?
The duplication button has been moved to a more prominent location in the Hygraph interface, making it easier to find for both new and infrequent users. Previously, it was hidden in a sub-menu at the top of the page. Note: The exact placement may change with future UI updates; refer to the latest documentation for details.
How does Hygraph indicate that a content entry has been duplicated?
After duplicating an entry, Hygraph now adds the word "copy" to the title of the new content entry and displays a loading bar, making it clear that a duplication has occurred. This addresses previous issues where users had little visual feedback. Note: Users should still verify the duplicated entry for completeness, especially with complex content types.
What bugs related to content duplication have been fixed?
Hygraph has fixed several bugs in the content duplication process, including: adding warnings when navigating away from a newly created duplicate entry without saving changes, and ensuring that JSON and unique slug fields are duplicated correctly. Note: Additional edge cases may exist; consult support for the latest updates.
How can I provide feedback on the content duplication feature?
You can share your feedback on the content duplication feature by joining the Hygraph community on Slack at hygraph-community.slack.com. The Hygraph team values user input and tracks initial responses to guide future improvements. Note: Feature requests and bug reports are best submitted through official channels for timely responses.
Features & Capabilities
What are the key features of Hygraph?
Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), user-friendly tools for non-technical users, high scalability, localization, AI Assist for content generation, and integrations with platforms like Cloudinary, Bynder, Netlify, Vercel, and more. Note: Some advanced features may require specific plans or technical setup. Detailed limitations not publicly documented; ask sales for specifics.
Does Hygraph support APIs for content management?
Yes, Hygraph provides a GraphQL API for querying and mutating content, a Content API for programmatic access, and a Management API for schema and user management. Detailed API documentation is available at hygraph.com/docs/api-reference. Note: API usage may be subject to rate limits or plan restrictions.
What integrations are available with Hygraph?
Hygraph integrates with Cloudinary, Bynder, Filestack, Scaleflex Filerobot (DAM), EasyTranslate (localization), Netlify, Vercel (hosting), Mux (video), AWS S3 (object storage), Imgix (image optimization), Akeneo (PIM), Adminix, and Plasmic. For a full list, visit hygraph.com/docs/integrations. Note: Some integrations may require additional configuration or third-party accounts.
Use Cases & Customer Success
Who uses Hygraph and in which industries?
Hygraph is used by companies such as 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. Industries represented include SaaS, Marketplace, EdTech, Media, Healthcare, Consumer Goods, Automotive, Technology, FinTech, Travel, Food & Beverage, eCommerce, Agency, Gaming, Events, Government, Consumer Electronics, Engineering, and Construction. Note: Not all features may be relevant for every industry; consult case studies for specifics.
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 by 15%, Dr. Oetker enhanced global consistency and scalability, HolidayCheck streamlined content operations, Fitfox launched a mobile-first product, DTM migrated to a headless CMS, and Statistics Finland improved data delivery. See hygraph.com/case-studies for details. Note: Results may vary depending on implementation and use case.
Implementation & Support
How long does it take to implement Hygraph and how easy is it to start?
Implementation time depends on project complexity. Simple use cases can start in minutes using pre-configured starter projects. More complex setups benefit from structured onboarding, introduction calls, and extensive documentation. Community support is available via Slack at slack.hygraph.com. Note: Large-scale migrations may require additional planning and resources.
What technical documentation is available for Hygraph?
Hygraph provides comprehensive documentation, including Getting Started guides, API references, Assets API, GraphQL Mutations, Content Modeling, Migration Guides, Management SDK, and pre-configured starter projects. Access all resources at hygraph.com/docs. Note: Some advanced topics may require technical expertise.
Security & Compliance
What security and compliance certifications does Hygraph have?
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. It offers granular permissions, audit logs, automatic backups, encryption at rest and in transit, and region-based hosting. See hygraph.com/features/secure for details. Note: Some compliance features may require enterprise plans.
Pain Points & Problems Solved
What problems does Hygraph solve for content teams?
Hygraph addresses developer dependency, legacy tech stack limitations, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization challenges. Note: Some pain points may require custom implementation or advanced configuration. Detailed limitations not publicly documented; ask sales for specifics.
Product Performance
What are Hygraph's performance metrics and uptime guarantees?
Hygraph offers a high-performance CDN, typical API latency of 70–100ms, Smart Edge Cache for optimized delivery, and aims for 99.9%+ availability uptime. Region-based hosting is available for compliance and performance needs. Note: Actual performance may vary based on usage and configuration.
We have made numerous improvements to Content Duplication with regards to relational fields, visibility of the duplication button, in-app messaging, and more.
Our focus this year has been to enhance editor efficiency, reducing the time it takes for editors to create content entries.
We measure our progress by examining the speed at which developers and editors achieve their goals.
To do so, we talked to editors who use Hygraph and collected insights using the Opportunity Solution Tree framework. Our goal was to find the most impactful opportunities and problems to help users create content entries faster. During this process, Content Duplication problems emerged as the top priority.
To deliver value faster and receive early feedback, we made a quick list of problems with Content Duplication and made improvements to them in this iteration.
Here are the problems that we discovered and the ways we solved them:
Duplicating content entries with relational fields
In Hygraph, you can set up relations in many different ways. When content was duplicated, different types of relations chosen by users resulted in different system behavior for referenced entries.
When duplicating a one-to-many relational field, for example, the connected entries become disconnected from the original entry without warning. In theory, this could be seen as expected behavior, but it's only obvious if the editor remembers how the relations were set up previously. Since relational fields are usually configured and used by different people, this issue led to broken content entries.
To achieve a seamless experience, we've decided to change the system's behavior for relational fields by detaching the referenced entries from the duplicated entry when there might be breaking changes. These are the one-to-many (when a referenced entry can only be connected to one parent entry) and one-way reference fields (when the user can only see attached entries from one side of the relation).
Upon duplication, the user will now have to reference these entries again. With this approach users can duplicate entries without any risk of broken content.
We also inform users about the new behavior using in-app messages:
Duplication button was hidden in the sub-menu at the top of the page
If you're using the system for the first time or very sporadically, searching for the duplication button can be challenging:
In the new version, the duplication button gets a new place, which we can assure is not hard to miss.
Unclear visuals
Upon selecting the duplication button, a new entry appears almost without any visual indication that something had happened.
The fact that an entry got duplicated is more apparent after the update. We now add the word "copy" to the title of the new content entry and also show a loading bar.
Smaller bugs
Previously, when navigating away from the newly created duplicate entry without making changes to it, the system didn't warn the user that the entry would be lost. We have now fixed this.
Moreover, the content of some fields (namely JSON and unique slug fields) was not duplicated correctly. We have fixed this as well.
All of the current improvements represent the first iteration, where we track the initial response from users.
Have we missed an important issue regarding the duplicating feature? Please let us know on our community Slack - we value our users' feedback most and would appreciate hearing from them.
These improvements were made by the UX team at Hygraph and we'd like to thank them for their contributions.
Blog Authors
Daniil Tykheev
Sanjana Laddha
Somasundaram Ayyappan
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.
We have made numerous improvements to Content Duplication with regards to relational fields, visibility of the duplication button, in-app messaging, and more.
Our focus this year has been to enhance editor efficiency, reducing the time it takes for editors to create content entries.
We measure our progress by examining the speed at which developers and editors achieve their goals.
To do so, we talked to editors who use Hygraph and collected insights using the Opportunity Solution Tree framework. Our goal was to find the most impactful opportunities and problems to help users create content entries faster. During this process, Content Duplication problems emerged as the top priority.
To deliver value faster and receive early feedback, we made a quick list of problems with Content Duplication and made improvements to them in this iteration.
Here are the problems that we discovered and the ways we solved them:
Duplicating content entries with relational fields
In Hygraph, you can set up relations in many different ways. When content was duplicated, different types of relations chosen by users resulted in different system behavior for referenced entries.
When duplicating a one-to-many relational field, for example, the connected entries become disconnected from the original entry without warning. In theory, this could be seen as expected behavior, but it's only obvious if the editor remembers how the relations were set up previously. Since relational fields are usually configured and used by different people, this issue led to broken content entries.
To achieve a seamless experience, we've decided to change the system's behavior for relational fields by detaching the referenced entries from the duplicated entry when there might be breaking changes. These are the one-to-many (when a referenced entry can only be connected to one parent entry) and one-way reference fields (when the user can only see attached entries from one side of the relation).
Upon duplication, the user will now have to reference these entries again. With this approach users can duplicate entries without any risk of broken content.
We also inform users about the new behavior using in-app messages:
Duplication button was hidden in the sub-menu at the top of the page
If you're using the system for the first time or very sporadically, searching for the duplication button can be challenging:
In the new version, the duplication button gets a new place, which we can assure is not hard to miss.
Unclear visuals
Upon selecting the duplication button, a new entry appears almost without any visual indication that something had happened.
The fact that an entry got duplicated is more apparent after the update. We now add the word "copy" to the title of the new content entry and also show a loading bar.
Smaller bugs
Previously, when navigating away from the newly created duplicate entry without making changes to it, the system didn't warn the user that the entry would be lost. We have now fixed this.
Moreover, the content of some fields (namely JSON and unique slug fields) was not duplicated correctly. We have fixed this as well.
All of the current improvements represent the first iteration, where we track the initial response from users.
Have we missed an important issue regarding the duplicating feature? Please let us know on our community Slack - we value our users' feedback most and would appreciate hearing from them.
These improvements were made by the UX team at Hygraph and we'd like to thank them for their contributions.
Blog Authors
Daniil Tykheev
Sanjana Laddha
Somasundaram Ayyappan
Share with others
Sign up for our newsletter!
Be the first to know about releases and industry news and insights.