#Glossary

#Basic concepts

Concept	Description
API Playground	The API Playground, located on the left sidebar of the Hygraph app, allows you to experiment with querying and mutating data.
Assets	The Asset model is included in every project by default. It is commonly used for images, but can also support any file type. Assets can be fetched, referenced, transformed, uploaded, updated, published, localized, deleted, and embedded.
Component	A component is a predefined set of fields that can be reused across models and content entries. You can think of a component as a flexible, reusable template where you define the fields once, and then fill them with different content every time you use it in a content entry.
Content modeling	The content model defines the schema of your content. It describes what kind of content you want to store, how it relates to other content, and how it can be edited within Hygraph.
Content views	Hygraph features default and custom content views. Default content views list all content entries created based on the respective models. Custom content views are filtered for specific content entries.
Enumeration	An enumeration (or enum for short) can be used to group values within a type. Enums are useful for filtering and defining certain content entries in your project.
Model	Models define the structure of your content. You build your schema by creating models and adding fields to them. Learn more in the quickstart guide.
Mutations	Operations that allow you to insert new data or modify existing data on the server side. See mutations for the full reference.
Preview URLs	Preview URLs are automatically generated links that allow you to preview content in your frontend before it is published. Configuring this feature adds a button to the content editor's right sidebar so editors can quickly access content previews.
Relations	References, often referred to as relations, allow you to connect one or more models together, and even reference multiple models as a single field type using GraphQL Union Types.
Remote sources	Remote sources are Hygraph's content federation feature. They allow you to add content from other systems and sources to the Hygraph API without migrating the content itself.
Schema editor	The schema editor is where you add fields, create relationships between models, and define the structure of your content. See the Studio walkthrough to learn more.
System fields	All default and custom models come with managed system fields. These fields reflect certain states of your content, such as when it was last updated or published.
Taxonomy	A taxonomy is a group of terms arranged in a hierarchical structure. Taxonomies are used to classify and logically connect content across multiple models. They are defined in the schema editor and support up to six levels of depth. Taxonomies are an enterprise feature.

#Content stages

This list offers a brief description of the two content stages every Hygraph project has by default.

Stage name	Description
Draft	The working stage for content. Unpublished entries exist only here. Published entries also have a `DRAFT` copy for edits before re-publishing. Saving without publishing does not affect the live published version.
Published	Published content. If the published button displays green, the content has been pushed live. If it displays blue, a new draft version has been saved and the published content is now outdated.

You can also create custom content stages for your project. See content stages to find out more.

#Fields

Field type	Description
Single line text	String type field widget. Used for adding headings and titles.
Multi line text	String type field widget. Used for adding longer text such as descriptions.
Markdown	String type field widget. A markdown editor.
Slug	String type field widget. Used for adding URL-friendly identifiers to your content.
Rich text	Text type field widget. A text editor with formatting.
Number	Integer type field widget. Used for adding numeric fields such as IDs or identifiers.
Float	Float type field widget. Used for numbers that include decimal values, such as ratings or prices.
Boolean	Boolean type field widget. A toggle that represents true/false.
Date	Date type field widget. A calendar date picker.
Date and time	Date and time type field widget. A calendar date picker that includes time.
JSON editor	JSON type field widget. Allows adding arbitrary JSON structures.
Cloudinary asset	JSON type field widget. Allows picking assets from Cloudinary.
Asset picker	Asset type field widget. Allows selecting assets from your project and supports any file type.
Color	Color type field widget. Supports HEX and RGBA.
Map	Location type field widget. Allows adding geo coordinates to your content.
Dropdown	Enumeration type field widget. Allows adding a dropdown list of values to your content.
Basic component	Component type field widget. Used for a single fixed component type and can be configured for one or multiple instances. See components to learn more.
Modular component	Modular component type field widget. Used for multiple component types. See components to learn more.
Reference	Relation type field widget. Used for content relationships.
REST	REST type field widget. Used to add external data via REST.
GraphQL	GraphQL type field widget. Used to add external data via GraphQL.

#Sidebar widgets

Widget name	Description
Entry information	System sidebar widget, added to your model by default. Offers basic entry information.
Localizations	System sidebar widget, added to your model by default. Allows viewing localized fields.
Preview	System sidebar widget. Allows previewing content changes by adding a preview link to your content.
Releases	System sidebar widget. Allows grouping entries into content releases for coordinated publishing. Scheduled publishing is configured via publish actions and is an Enterprise feature.
Stages	System sidebar widget, added to your model by default. Allows viewing in-app content stages.
Versions	System sidebar widget, added to your model by default. Allows viewing the version history of your content.

See system fields to learn more.

#Components

Concept	Description
Component	A component is a predefined set of fields that can be reused across models and content entries.
Component field	A special field type in your Hygraph schema that defines which components of which type can be used in a model. Component fields can be of basic or modular types.
Component instance	A specific occurrence of a component type, containing content, inside a content entry.
Nested components	Functionality that allows you to create components within a component.

See components to learn more.

#Variants

Concept	Description
Base entry	The main content entry that variants are built from. Updating a variant-enabled field in the base entry does not update the same field in its variants, and vice versa.
Segment	A named reference used to target a group of users based on shared characteristics or behaviors. Segments are managed externally and referenced in Hygraph to determine which variant of a content entry is delivered to a given audience.
Variant	A personalized version of a content entry tailored to a specific audience segment. Variants inherit the structure of the main entry but allow certain fields to be customized independently, enabling content teams to deliver targeted experiences without duplicating entries. Variants are an enterprise feature.

See variants to learn more.

#Glossary

#Basic concepts

Concept	Description
API Playground	The API Playground, located on the left sidebar of the Hygraph app, allows you to experiment with querying and mutating data.
Assets	The Asset model is included in every project by default. It is commonly used for images, but can also support any file type. Assets can be fetched, referenced, transformed, uploaded, updated, published, localized, deleted, and embedded.
Component	A component is a predefined set of fields that can be reused across models and content entries. You can think of a component as a flexible, reusable template where you define the fields once, and then fill them with different content every time you use it in a content entry.
Content modeling	The content model defines the schema of your content. It describes what kind of content you want to store, how it relates to other content, and how it can be edited within Hygraph.
Content views	Hygraph features default and custom content views. Default content views list all content entries created based on the respective models. Custom content views are filtered for specific content entries.
Enumeration	An enumeration (or enum for short) can be used to group values within a type. Enums are useful for filtering and defining certain content entries in your project.
Model	Models define the structure of your content. You build your schema by creating models and adding fields to them. Learn more in the quickstart guide.
Mutations	Operations that allow you to insert new data or modify existing data on the server side. See mutations for the full reference.
Preview URLs	Preview URLs are automatically generated links that allow you to preview content in your frontend before it is published. Configuring this feature adds a button to the content editor's right sidebar so editors can quickly access content previews.
Relations	References, often referred to as relations, allow you to connect one or more models together, and even reference multiple models as a single field type using GraphQL Union Types.
Remote sources	Remote sources are Hygraph's content federation feature. They allow you to add content from other systems and sources to the Hygraph API without migrating the content itself.
Schema editor	The schema editor is where you add fields, create relationships between models, and define the structure of your content. See the Studio walkthrough to learn more.
System fields	All default and custom models come with managed system fields. These fields reflect certain states of your content, such as when it was last updated or published.
Taxonomy	A taxonomy is a group of terms arranged in a hierarchical structure. Taxonomies are used to classify and logically connect content across multiple models. They are defined in the schema editor and support up to six levels of depth. Taxonomies are an enterprise feature.

#Content stages

This list offers a brief description of the two content stages every Hygraph project has by default.

Stage name	Description
Draft	The working stage for content. Unpublished entries exist only here. Published entries also have a `DRAFT` copy for edits before re-publishing. Saving without publishing does not affect the live published version.
Published	Published content. If the published button displays green, the content has been pushed live. If it displays blue, a new draft version has been saved and the published content is now outdated.

You can also create custom content stages for your project. See content stages to find out more.

#Fields

Field type	Description
Single line text	String type field widget. Used for adding headings and titles.
Multi line text	String type field widget. Used for adding longer text such as descriptions.
Markdown	String type field widget. A markdown editor.
Slug	String type field widget. Used for adding URL-friendly identifiers to your content.
Rich text	Text type field widget. A text editor with formatting.
Number	Integer type field widget. Used for adding numeric fields such as IDs or identifiers.
Float	Float type field widget. Used for numbers that include decimal values, such as ratings or prices.
Boolean	Boolean type field widget. A toggle that represents true/false.
Date	Date type field widget. A calendar date picker.
Date and time	Date and time type field widget. A calendar date picker that includes time.
JSON editor	JSON type field widget. Allows adding arbitrary JSON structures.
Cloudinary asset	JSON type field widget. Allows picking assets from Cloudinary.
Asset picker	Asset type field widget. Allows selecting assets from your project and supports any file type.
Color	Color type field widget. Supports HEX and RGBA.
Map	Location type field widget. Allows adding geo coordinates to your content.
Dropdown	Enumeration type field widget. Allows adding a dropdown list of values to your content.
Basic component	Component type field widget. Used for a single fixed component type and can be configured for one or multiple instances. See components to learn more.
Modular component	Modular component type field widget. Used for multiple component types. See components to learn more.
Reference	Relation type field widget. Used for content relationships.
REST	REST type field widget. Used to add external data via REST.
GraphQL	GraphQL type field widget. Used to add external data via GraphQL.

#Sidebar widgets

Widget name	Description
Entry information	System sidebar widget, added to your model by default. Offers basic entry information.
Localizations	System sidebar widget, added to your model by default. Allows viewing localized fields.
Preview	System sidebar widget. Allows previewing content changes by adding a preview link to your content.
Releases	System sidebar widget. Allows grouping entries into content releases for coordinated publishing. Scheduled publishing is configured via publish actions and is an Enterprise feature.
Stages	System sidebar widget, added to your model by default. Allows viewing in-app content stages.
Versions	System sidebar widget, added to your model by default. Allows viewing the version history of your content.

See system fields to learn more.

#Components

Concept	Description
Component	A component is a predefined set of fields that can be reused across models and content entries.
Component field	A special field type in your Hygraph schema that defines which components of which type can be used in a model. Component fields can be of basic or modular types.
Component instance	A specific occurrence of a component type, containing content, inside a content entry.
Nested components	Functionality that allows you to create components within a component.

See components to learn more.

#Variants

Concept	Description
Base entry	The main content entry that variants are built from. Updating a variant-enabled field in the base entry does not update the same field in its variants, and vice versa.
Segment	A named reference used to target a group of users based on shared characteristics or behaviors. Segments are managed externally and referenced in Hygraph to determine which variant of a content entry is delivered to a given audience.
Variant	A personalized version of a content entry tailored to a specific audience segment. Variants inherit the structure of the main entry but allow certain fields to be customized independently, enabling content teams to deliver targeted experiences without duplicating entries. Variants are an enterprise feature.

See variants to learn more.

#Glossary

#Basic concepts

Concept	Description
API Playground	The API Playground, located on the left sidebar of the Hygraph app, allows you to experiment with querying and mutating data.
Assets	The Asset model is included in every project by default. It is commonly used for images, but can also support any file type. Assets can be fetched, referenced, transformed, uploaded, updated, published, localized, deleted, and embedded.
Component	A component is a predefined set of fields that can be reused across models and content entries. You can think of a component as a flexible, reusable template where you define the fields once, and then fill them with different content every time you use it in a content entry.
Content modeling	The content model defines the schema of your content. It describes what kind of content you want to store, how it relates to other content, and how it can be edited within Hygraph.
Content views	Hygraph features default and custom content views. Default content views list all content entries created based on the respective models. Custom content views are filtered for specific content entries.
Enumeration	An enumeration (or enum for short) can be used to group values within a type. Enums are useful for filtering and defining certain content entries in your project.
Model	Models define the structure of your content. You build your schema by creating models and adding fields to them. Learn more in the quickstart guide.
Mutations	Operations that allow you to insert new data or modify existing data on the server side. See mutations for the full reference.
Preview URLs	Preview URLs are automatically generated links that allow you to preview content in your frontend before it is published. Configuring this feature adds a button to the content editor's right sidebar so editors can quickly access content previews.
Relations	References, often referred to as relations, allow you to connect one or more models together, and even reference multiple models as a single field type using GraphQL Union Types.
Remote sources	Remote sources are Hygraph's content federation feature. They allow you to add content from other systems and sources to the Hygraph API without migrating the content itself.
Schema editor	The schema editor is where you add fields, create relationships between models, and define the structure of your content. See the Studio walkthrough to learn more.
System fields	All default and custom models come with managed system fields. These fields reflect certain states of your content, such as when it was last updated or published.
Taxonomy	A taxonomy is a group of terms arranged in a hierarchical structure. Taxonomies are used to classify and logically connect content across multiple models. They are defined in the schema editor and support up to six levels of depth. Taxonomies are an enterprise feature.

#Content stages

This list offers a brief description of the two content stages every Hygraph project has by default.

Stage name	Description
Draft	The working stage for content. Unpublished entries exist only here. Published entries also have a `DRAFT` copy for edits before re-publishing. Saving without publishing does not affect the live published version.
Published	Published content. If the published button displays green, the content has been pushed live. If it displays blue, a new draft version has been saved and the published content is now outdated.

You can also create custom content stages for your project. See content stages to find out more.

#Fields

Field type	Description
Single line text	String type field widget. Used for adding headings and titles.
Multi line text	String type field widget. Used for adding longer text such as descriptions.
Markdown	String type field widget. A markdown editor.
Slug	String type field widget. Used for adding URL-friendly identifiers to your content.
Rich text	Text type field widget. A text editor with formatting.
Number	Integer type field widget. Used for adding numeric fields such as IDs or identifiers.
Float	Float type field widget. Used for numbers that include decimal values, such as ratings or prices.
Boolean	Boolean type field widget. A toggle that represents true/false.
Date	Date type field widget. A calendar date picker.
Date and time	Date and time type field widget. A calendar date picker that includes time.
JSON editor	JSON type field widget. Allows adding arbitrary JSON structures.
Cloudinary asset	JSON type field widget. Allows picking assets from Cloudinary.
Asset picker	Asset type field widget. Allows selecting assets from your project and supports any file type.
Color	Color type field widget. Supports HEX and RGBA.
Map	Location type field widget. Allows adding geo coordinates to your content.
Dropdown	Enumeration type field widget. Allows adding a dropdown list of values to your content.
Basic component	Component type field widget. Used for a single fixed component type and can be configured for one or multiple instances. See components to learn more.
Modular component	Modular component type field widget. Used for multiple component types. See components to learn more.
Reference	Relation type field widget. Used for content relationships.
REST	REST type field widget. Used to add external data via REST.
GraphQL	GraphQL type field widget. Used to add external data via GraphQL.

#Sidebar widgets

Widget name	Description
Entry information	System sidebar widget, added to your model by default. Offers basic entry information.
Localizations	System sidebar widget, added to your model by default. Allows viewing localized fields.
Preview	System sidebar widget. Allows previewing content changes by adding a preview link to your content.
Releases	System sidebar widget. Allows grouping entries into content releases for coordinated publishing. Scheduled publishing is configured via publish actions and is an Enterprise feature.
Stages	System sidebar widget, added to your model by default. Allows viewing in-app content stages.
Versions	System sidebar widget, added to your model by default. Allows viewing the version history of your content.

See system fields to learn more.

#Components

Concept	Description
Component	A component is a predefined set of fields that can be reused across models and content entries.
Component field	A special field type in your Hygraph schema that defines which components of which type can be used in a model. Component fields can be of basic or modular types.
Component instance	A specific occurrence of a component type, containing content, inside a content entry.
Nested components	Functionality that allows you to create components within a component.

See components to learn more.

#Variants

Concept	Description
Base entry	The main content entry that variants are built from. Updating a variant-enabled field in the base entry does not update the same field in its variants, and vice versa.
Segment	A named reference used to target a group of users based on shared characteristics or behaviors. Segments are managed externally and referenced in Hygraph to determine which variant of a content entry is delivered to a given audience.
Variant	A personalized version of a content entry tailored to a specific audience segment. Variants inherit the structure of the main entry but allow certain fields to be customized independently, enabling content teams to deliver targeted experiences without duplicating entries. Variants are an enterprise feature.

See variants to learn more.