What are some unique content modeling cases in which you would find Global Fields particularly useful?


Userlevel 3

What are some unique content modeling cases in which you would find Global Fields particularly useful?


63 replies

To me SEO is one of the best examples, however, I see it as it might be used for something that should be on many content types like Newsletter Subscription.

Badge

On our Stack, we want to show certain content just to specific customers. That can occur on every Content Type, so I used Global Fields to always use the same structure that we need so it’s easier to identify the conditions in the frontend.

 

Without Global Fields, it would be a bit of a hassle to recreate the condition structure over and over again for each page.

Global fields could be very useful in implementing Alerts on pages and content

Badge

Reusable configurations like creating carousel configuration, SEO data that used across multiple content types, components, color that design theme are also the good configurations example for this. 

Badge

What are some unique content modeling cases in which you would find Global Fields particularly useful?

It is helpful for common features like SEO fields. Meta data like titles, keywords, and descriptions are very helpful for SEO. It can be viewed as a variable that can be used globally in any content type and that, when updated, will update anywhere it is used.

Badge

Global Fields can be particularly useful for configurations and settings to be used on every page of website such as SEO, Newsletter Signup Popups.

It can also be used in form of modular blocks to be used as common components across all pages such header, navbar menus, footer, sidebars.

Badge

A Global field is a reusable field (consisting of a group of fields) that you can define once and reuse in any content type within your stack. This field saves the time and effort of adding the same set of fields (and their settings) in multiple content types of a stack.

This field possesses certain properties that you can change any time as per your needs. The properties that can be modified are “Select Global Field,” “Display Name,” “Unique ID,” “Instruction Value,” “Help Text,” “Multiple,” and “Non-localizable.”

Global Field Use cases


Let's understand how we can use Global fields in our content type through the help of some real world examples.

Global field can be used for the following most common use cases:

  • SEO field as a global field
  • Address/ Site Description field as a global field
  • Taxonomy group field as a global field
  • Website Banner

 

Badge

Global fields are very useful as we can add those fields on everypage / perticular page or on which region of page we want to use , we can use global fields.

Badge

Reusable fields you will need on multiple different locations, so that you can ensure these input fields are the same on multiple content types.

Badge

One useful example of global fields is in things like SEO, creating a taxonomy to be used within content types to categorize the content.

Badge

A Global Field is a reusable field that you can define once and reuse in any content type within your stack. This field saves the time and effort of adding the same set of fields (and their settings) in multiple content types of a stack.

 

for example

this SEO field will be automatically populated with the Meta Title and Meta Description subfields.

for creating menus and submenus

Badge

What are some unique content modeling cases in which you would find Global Fields particularly useful?

If pass related metadata, it could increase the frequency founding your website in search results

Badge

A Global field is a reusable field, so they are very useful when we need them in more than one location. We can define one and reuse it in any content type.

An example is SEO field will be automatically populated with the Meta Title and Meta Description subfields.

Other examples are:

  • Address/ Site Description field as a global field
  • Taxonomy group field as a global field
  • Website Banner

Reply