Open Benjen opened 3 years ago
Tied to GovCMS 9 version @ https://github.com/govCMS/GovCMS/issues/187
Hi @Benjen can you provide some information on where this is used on your products for some context? Trying to determine the scale of the issue/need on this one. Is part of form validation, or is part of data in content or a mix of things or something else?
** 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:
** 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.
** 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?
** Additional information