Schema Builder

The ability to add a custom slug field within the content model is a powerful UI tool that adds immediate value to the content. A Content Editor can configure the slug field to be generated from other field values in your model using other field items like Title, or can create a custom field. Both help create a clean URL, or friendly URL, that lacks in inconsistencies or confusion for that content item. 

The Rich Text or WYSIWYG is the component within the Hygraph Content Editor that is an advanced String field that returns your content in four different formats: raw, html, markdown, and text. Within the Rich Text component, your content creators can create, edit, and manipulate content and preview their content piece. 

For time-sensitive information or to identify when a piece was published, add a date field into the content model. The date field adheres to tISO 8601 standard, meaning a date such as October 7, 1989 will be represented as 1989-10-07 when queried. 

For use cases such as internal management systems or e-commerce where numerical values are important, developers are able to add Float Fields to content models which allow content editors to add floating point numbers, or fractional values, to content items. The numerical values often help describe things that require precision, such as distance, weight, volume, etc.

Boolean is a default field value that allows content editors to mark if something is true or false. Use case for this field value can vary greatly depending on the content type, but some of the most common examples are to mark if an item is on sale, is part of a bundle, if a post will or won't accept comments, if a banner or post should be featured, and beyond. 

The Integer Field is another numerical Field Type which allows Content Creators to add whole numbers as an item within their content piece. These numbers typically are used to reference numerical values correlating to things like price, stock quantities, or weight. 

Date and Time Field is best used to mark time-sensitive content items. Some examples of when this would be useful is for aggregating or creating content that involved important updates like news and/or weather. As is also the case for the Date only field, it adheres to tlSO 8601 standard when queried. 

This native field is designed to support JSON, or JavaScript Object Notation, that is most commonly used to store large amounts of data from other systems. This is useful when trying to connect third-party fields in to your content models...

Upload a multitude of different assets to any content piece by adding an Asset field to your model. From video, gif, to static images, Assets are an invaluable way to bring content to life. Adding Assets to content pieces is easy with our intuitive uploader, and content view which allows Content Editors and Managers to see what assets are already available, edit, and publish.

Color is an important element of any content piece and brand. We gives users the ability to set color schemes for branding and promotions is inherent within the Hygraph Schema, and users are able to add HEX, RGBA, and css color values to any content model. 

Highlight where content takes place, the availability of items in different locations, and more with the ability to add location within a content model. The Location field, or Map, returns latitude, longitude, and distance Float values. 

References, which are often referred to as relations, are a powerful Field Type that allows content creators to connect one or more models together. This is extremely beneficial for teams that need to group content or share content.

For example, relations work well when attaching authors to different blog posts, connecting content items to a campaign, or attaching mandatory legal content to particular content items. There are different types of reference types including One- and Two-Way relations and Union Type. 

This Field Type is a String field type which gives the Content Creators and Editors the opportunity to add single-line items like a title to the content model or content piece. In the Schema, the Single Line Text can be identified as a title, translated and can have multiple values. It can also come with particular validations including making it required, force the input to be unique, limit the character count, match a specific pattern, or restrict a specific pattern. 

This field is one of the several String field types allowed in the Schema that enables Content Creators to add longer text blocks within a content model. In the Schema, the Multi-Line Text can be identified as a title, translated and can have multiple values. It can also come with particular validations including making it required, force the input to be unique, limit the character count, match a specific pattern, or restrict a specific pattern. 

One-Way References can be used when the content model has only one relation or one direction that the information needs to be served from or connected to.

An example of One-Way Reference could include something like placing a legal footer at the bottom of particular content pieces. The information of the footer can be shared to that content piece, but the content it's attached to does not need to be shared with the footer model. In these cases, One-Way References can help reduce clutter within your Hygraph project and help improve performance.

Two-Way References, or bidirectional relations, means content information is shared in two directions. This references is useful for cases where both sides of the references are relevant, and need to be queryable. An example of this would be connecting a blog post to an author. For this example, the user can ask two questions: what blog posts has the author written, and sharing the author information within the blog post itself. 

Using this Reference, create relations or link multiple models together. This is beneficial when a user creates content from any one of the connected content models and then has the ability to query from the data of each of those different models. This can then render different components in the frontend.  

API Extensions, or Remote fields, are custom resolver entry points for your schema and the first feature in a series of Content Federation utilities. This attribute is a custom resolver entry point for your Schema and allows data to be sourced from an external third-party web service and accept field values from other Hygraph fields as arguments.

Remote Fields empower teams to enrich their Hygraph projects with data from external services easily and programmatically. 

Give developers more flexibility and control when working with fields by allowing them to dictate which fields should be hidden from view of the content creator, or allow fields to be displayed with important or relevant information without giving business users the ability to edit that particular field. 

Field Validations setup within the Schema allows for different visibility options via the Advanced tab during field creation. This gives developers more flexibility and control over the content design and helps the Content Creators they support by dictating what each field requires so content is never missed or input incorrectly.