Global fields

Some data needs to be available everywhere in an application, such as a menu on every resource or a site name, slogan, or a publishable, 3rd-party API key. These types of data can be configured by adding global fields to your project. Global fields embed themselves on every resource and can be changed in one place and reflected everywhere.

For example, a developer could add a global text field to provide a site slogan to their front end. Another common use of global fields is to embed a main menu on every resource.

The advantage of a global field is that it reduces or eliminates any need for typically hard-coded content. For example, it makes it trivial to add new menu items or even to replace a logo, if the front end is configured to consume such a field.

Fields are per-resource type, so that each resource has the correct data for its model. There will be data that should be part of every page response, for example footer info or menus.

In these cases, global fields allow you to add any arbitrary data that will always be available.

Just like resource types, global fields have a schema and the name of a field can be edited.