Add Address module to GovCMS

[Benjen]

** What value does this module/package add to GovCMS?

GovCMS7 provides the Address Field module, which we use on our site. The Address module is the Drupal 8 successor of the Address Field module and includes a migration path from the Address Field module in Drupal 7 to the address field in Drupal 8/9.

Features include:

• Address field type and form element
• Country field type and form element
• Zone field type and form element
• Address formats for 200 countries
• Subdivisions (administrative areas, localities, dependent localities) for 40 countries
• Subdivision translations for all of the parent country's (i.e Canada, Switzerland) official languages.
• Country list with translations for over 200 locales, provided by CLDR

** Please provide a brief outline of what this module does.

Performs the same function as the Address Field module in GovCMS7.

** Who does this module benefit:
[ ] end users
[ * ] content editors
[ * ] site builders
[ ] themers
[ ] developers

** How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?

You could create an address paragraph type; however, it would not be possible to migrated content in GovCMS7 using this field across to the paragraph field without the use of a custom migration. You would also need to manually recreate things such as country names, etc. which are automatically populated when using the Address module.

** If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.

** What is the maintenance and support status of the module. Describe the issue queue activity.

• Latest version: 8.x-1.9 (3 November 2020).
• Bugs: 192 (28 open).
• Pending patches: 40
• Drupal 9 compatible.

** What permissions are needed to utilise the module (and are any new permissions provided by the module)?

This module does not introduce any new permissions.

** Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?

Not sure.

** Is the module designed to capture anonymous user data?

No

** Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.

Presumably since it uses the Field API.

** What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?

• 63,162 websites report using this module.
• Four maintainers.

** Additional information

[thisisalistairsaccount]

Tied to Drupal 8 issue log at govCMS/GovCMS8#617

[dpi]

A vote for Address module and info.

Its quite helpful generally to include the Address fields so address-looking data can be collected and stored in the backend neatly. It also saves a lot of time creating a bunch of fields and laying them out consistently.

The project has a solid backing, maintined by Centarro, of Drupal Commerce. It supports Drupal 8/9 and currently has 64k installs, it has had a Drupal 8 stable release for 4 years.

Address subfields:

• First name
• Middle name
• Last name
• Company
• Address line 1
• Address line 2
• Postal code
• Sorting code
• Dependent locality (e.g. Neighbourhood)
• Locality (e.g. City)
• Administrative area (e.g. State or Province)

Depending on context/configuration, some fields will not be hidden/visible.

The project alsos bundles two related fields

• Country: a maintained list of countries on planet earth.
• Zone: is effectively a Country -> State/territory selector with postcode limits.

Webform already includes integration with Address project, providing a new 'Advanced Address' field.

Including address makes it possible to add validation against a standard data set.

[dpi]

Field config

Field display