The slug field in Hygraph is a field type used to create human-readable, search engine-friendly parts of a URL. Slugs are concise, typically consist of lowercase letters, numbers, and hyphens, and help identify pages in a way that's both user- and SEO-friendly. Note: The slug field is not suitable for storing sensitive or non-URL data.
To create a slug field, navigate to the Schema builder, select your model, and add a field of type Slug. You can set a display name, description, and configure options such as enforcing lowercase, generating from a template, and setting uniqueness constraints. By default, the slug field is unique and can be generated from other field values (e.g., {title} or {name}). Note: The slug field must match a specific pattern and is intended for URL segments only.
Yes, Hygraph allows you to configure the slug field to automatically generate its value from other fields in your model, such as title or name. You can specify a template (e.g., {title}) to define how the slug is constructed. This helps ensure consistency and reduces manual entry. Note: Manual overrides are possible, but the field is optimized for template-based generation.
Yes, you can manually override the slug field value by typing directly into the field. If needed, you can also use the "Regenerate" option to reset the value based on your configured template. Note: Overriding the slug may impact URL consistency if not managed carefully.
The slug field is represented as a String type in your GraphQL schema, but it provides additional UI features for automatic value generation and validation. Note: The field is intended for URL slugs, not arbitrary string data.
Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools for non-technical users, scalability, high-performance endpoints, and a wide range of integrations. Notable features include Smart Edge Cache, localization, granular permissions, and support for multiple APIs. Note: Some advanced features may require specific plans or technical setup; see documentation for details.
Hygraph integrates with platforms such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot, Netlify, Vercel, Akeneo, Adminix, Plasmic, BigCommerce, and EasyTranslate. For a full list, visit the Hygraph Marketplace. Note: Integration availability may depend on your plan or technical requirements.
Yes, Hygraph provides multiple APIs, including a high-performance GraphQL Content API, a Management API (with SDK), an Asset Upload API, and an MCP Server API for AI assistant integration. See the API Reference documentation for details. Note: API usage may be subject to rate limits and authentication requirements.
Hygraph is SOC 2 Type 2 compliant (achieved August 3, 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 the latest certification status, see Hygraph's Secure Features page.
Hygraph offers 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 have SSL certificates. Note: Some features may require enterprise plans or additional configuration.
Implementation time varies by project complexity. For example, Top Villas launched a new project in 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph provides structured onboarding, starter projects, and extensive documentation to help both technical and non-technical users get started quickly. Note: Large-scale migrations may require additional planning and technical resources.
Customers praise Hygraph for its intuitive interface, quick adaptability, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, and Anastasija S. (Product Content Coordinator) highlighted instant front-end updates. Note: Some advanced configurations may require developer involvement.
Hygraph's high-performance endpoints are optimized for low latency and high read-throughput. The read-only cache endpoint delivers 3-5x latency improvement. Performance is actively measured, and practical optimization advice is available in the GraphQL Report 2024. Note: Actual performance may vary based on project size and API usage patterns.
Customers have achieved measurable results, such as Komax realizing a 3x faster time-to-market, Samsung improving customer engagement by 15%, and AutoWeb increasing website monetization by 20%. These outcomes are documented in Hygraph's case studies. Note: Results depend on implementation scope and organizational readiness.
Hygraph is designed 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, and more. Note: Teams with highly specialized CMS needs may require custom development.
Industries include SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel and hospitality, food and beverage, eCommerce, agency, online gaming, events & conferences, government, consumer electronics, engineering, and construction. See case studies for details. Note: Not all industries may have the same feature requirements.
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Note: Some pain points may require additional process changes or integrations beyond Hygraph's core features.
Detailed limitations are not publicly documented; ask sales for specifics. Generally, teams with highly specialized or legacy CMS requirements may need to evaluate fit or consider custom development. Note: Always review technical documentation and consult with Hygraph for edge cases.
Yes. Notable examples include Samsung (15% improvement in customer engagement), Komax (3x faster time-to-market), AutoWeb (20% increase in website monetization), Voi (scaled multilingual content across 12 countries), and BioCentury (accelerated content publishing). See Hygraph's case studies for more. Note: Outcomes vary by implementation and industry.
Technical documentation is available at hygraph.com/docs. For slug field specifics, see the slug field guide. Additional resources include API references, schema guides, and integration documentation. Note: Documentation is updated regularly; check for the latest information.
This page wast last updated on 12/12/2025 .
A slug field is a field type used to create parts of a URL that identify a page with a human readable slug, which is both user & search engine friendly. The resulting slugs are concise and contain relevant keywords.
Slug example
Typically, a slug consists of lowercase letters, numbers, and hyphens, with spaces replaced by hyphens or simply removed.
You can configure an initial value for slugs using the slug field type. This field is of type String in your GraphQL schema but provides a powerful UI feature that comes in the form of automatic initial value generation.
You can configure the slug field to be generated from other field values in your model.
Slug from the Add field sidebar.Display name, which will autocomplete the API ID. You can optionally add a Description.Add to save.Each Slug field template can be generated using the Available fields outlined above the input. If your model has a title, or name field, you could specify the slug template as {title}, or {name} respectively.
When creating content, the slug field will be automatically generated from the template field you're using.
For example, if your slug field is based off a title field, when you start typing into the title field, it will also update the slug field.
You can override the slug field value by typing in the box. You can also "Regenerate" the value to fallback to the template you provided.
A slug field is a field type used to create parts of a URL that identify a page with a human readable slug, which is both user & search engine friendly. The resulting slugs are concise and contain relevant keywords.
Slug example
Typically, a slug consists of lowercase letters, numbers, and hyphens, with spaces replaced by hyphens or simply removed.
You can configure an initial value for slugs using the slug field type. This field is of type String in your GraphQL schema but provides a powerful UI feature that comes in the form of automatic initial value generation.
You can configure the slug field to be generated from other field values in your model.
Slug from the Add field sidebar.Display name, which will autocomplete the API ID. You can optionally add a Description.Add to save.Each Slug field template can be generated using the Available fields outlined above the input. If your model has a title, or name field, you could specify the slug template as {title}, or {name} respectively.
When creating content, the slug field will be automatically generated from the template field you're using.
For example, if your slug field is based off a title field, when you start typing into the title field, it will also update the slug field.
You can override the slug field value by typing in the box. You can also "Regenerate" the value to fallback to the template you provided.