Articles

Drupal 8 comes with three built-in field formatters for image fields: Image, Image URL, and Responsive Image (the latter requires enabling the core responsive_image module). A wide array of contributed modules provide additional field formatters for image fields. These are roughly categorized below.

Drupal 8 core comes with two field formatters for integer fields: Default and Unformatted. The following contributed module provides an additional field formatter for integer fields:

• Time Formatter

Drupal 8 comes with two field formatters for link fields: “Link” and “Separate link text and URL”. The following contributed modules provide additional field formatter options for link fields:

The core Telephone module comes with one field formatter: Telephone Link.

Below is a list of contributed modules that provide additional formatting options for telephone fields:

• Phone Link
• Telephone Formatter

Drupal 8 comes with three field formatters for text fields: Default, Trimmed, and Summary or Trimmed.

The following modules provide additional Field Formatter plugins for text fields:

Fields with plain text or string types have only one field formatter in core: the default. It simply displays the unaltered string, potentially linked to its parent entity.

Below is a list of contributed modules that provide additional field formatting options for text fields:

In Drupal, configuration refers to the set of administrative settings that define how the site functions, rather than the content of the site itself.

Configuration typically includes things like the site name, content types and their fields, taxonomy vocabularies, views, and so on.

Drupal stores site configuration data in a consistent manner—from the list of enabled modules to content types, taxonomy vocabularies, fields, and views.

Making configuration changes directly on a live site is not recommended. The configuration system is designed to make it easy to use the current configuration, test changes locally, export them to files, and then deploy them in a production environment. Your site’s configuration can be stored as part of your codebase and integrated into version control.

Here’s a simple example demonstrating how a site name can be configured in one environment and deployed in another. This example involves manually uploading and downloading .tar.gz configuration files, but it’s also possible to keep your site’s sync directory under version control and synchronize that way.

1. Install Drupal 8. We’ll refer to this as the “Production” site.

This page assumes you’re familiar with using Drush and have the latest version installed.

The following example demonstrates how to export changes from development sites to production sites. The reverse is also possible.

1. Install Drupal 8. We'll refer to this site as "Live".