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?


24 replies

Badge +1

Reusable fields you will need on multiple different locations, so that you can ensure these input fields are in sync over multiple content types. The example used in the exercise itself (SEO) was quite on point as an example. Other things I can think of are:

  • Set of booleans for configuration of a page; for example:
    • Should an external chatbot plugin be enabled on this page
    • Should an external feedback plugin be enabled on this page
  • Metadata (other than SEO); for example Google Analytics or any other analytics tool

There probably are enough other examples, which I can't think of now. But I presume that anytime you notice you reuse something over different locations, in multiple content types, it should ring a bell and you should consider using Global Fields.

Userlevel 1
Badge +1

Particularly efficient for configurations to be done on all the pages such as show extra information or features shown on all the pages.

Userlevel 1
Badge +1

One useful example of global fields is to create a taxonomy to be used within content types to categorize the content.

A more clear example is to create a field that can be reused by different content types, and can be updated (e.g.: adding fields) from a single place.

Badge +1

Particularly efficient for configurations to be done on all the pages such as show extra information or features shown on all the pages.

thank you

Badge +1

The behavior of a global field is similar to having a global variable in an application which can be useful. Multiple content types sharing the same global fields with a central place to maintain it. Any updates of the global field is reflected on all content types automatically.

Badge +1

The example given on the course portrays Global Fields appropriately. The meta data like keywords, description along with boolean fields can help a lot in the Search Engine Optimization. It can be understood as a variable which can be used globally in any content type and when updated, the changes will be reflected wherever it is used.

Badge +1

Using Global Fields to hold metadata can help with the success of the content. This is useful for if the creator would like to help the site show up on more search results.

Badge +1

The Global Fields are useful for the search engine. You can define some specific fields that will be used by the search engine and then you will be able to search entries of different content types by using the same search box.

Badge +1

The Global Fields are useful for managing the metadata used by the client to categorize their content into brands or product offerings by market segment.

This categorization can be used to maintain the corporate branding of content, the content naming conventions and vocabulary used on the website across multiple regions.

Badge +1

The Global Fields are useful to use in case of repetitive fields across multiple content models. The SEO example was really useful. You could also use it to enable and disable general features per page. 

Badge +1

The use of Global fields will increase the SEO - making it easier for a higher ranking for your website. Also, one of the simplest examples where I found global fields extremely helpful was when there was an office/ global contact number - so since the field was marked as a global field, we only had to change it at one place which changed the content on all referenced pages. Otherwise, we would have to manually go to each page field and change which is a lot of manual work, plus can increase the chances of a mistake.

whenever content structures need to be reused in content models

Badge

Hi to everyone, regarding below question I would like express like opinion if we are using global fields it is help to us to hold metadatawith the success of the content. This is so useful for content maker in order to show up you website or store in first place in SEO, because search robots fine meta words by this Global Fields

Badge

Global fields function like group fields in that they can contain nested fields, and result in an equivalent JSON structure. Multiple content types can share global field definitions. For example, if every type of page on a website contains a consistent collection of fields for metadata, then the content types for those page entries can share a global field that defines those fields.

Badge +1

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.

Badge +1

Configurations are one of the use cases of Global Fields. Set of fields reused across multiple Content Types needs to be created in Global Fields.

Badge

As others have stated, another good use for global fields is configuration and options, such as whether a page should show in a menu, or for holding other types of data which can then be used to define global UI elements

It is a very useful feature for adding SEO fields or maybe some standard components. NPS survey or something like that could be used as a global field.

Badge +1

The meta data like keywords, description can help a lot in the Search Engine Optimization. It can be understood as a variable which can be used globally in any content type and when updated, the changes will be reflected wherever it is used.

Badge

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

It is useful for common features like SEO fields, role restriction (when you need to restrict the content for some type of users).

Badge

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

As stated by the others, Global fields could be really useful for repetitive/common fields across many content types. Global fields can also be useful as configurations and/or options.

Configurations are one of the use cases of Global Fields. Set of fields reused across multiple Content Types needs to be created in Global Fields.

I agree with you, storing config in one place is very helpful, especially when expanding and upgrading.

Badge

The Global field is just a reusable set of fields that can be created once and used across multiple content types. The value for this field needs to be created separately for each entry. Sample use case - Suppose, we want to use a group of address fields across several content types. In this case, creating an “Address” Global field makes sense. It would comprise fields such as “House No,” “Apartment Name,” “Street Name,” “City,” and “Postal Code.

Global fields could be useful, besides things like SEO, to be used for some configuration common to all your content models.

Reply