Is your feature request related to a problem? Please describe.
As an author, I want to be able to add contact information to methods on how-to pages so that I don't have to change how-to pages if the contact information changes.
Describe the solution you'd like
In addition to free text area for method, author is able to add a contact to a method and the contact information shown will be related to the method. (If phone is selected as method, then only the phone contact information will be shown.)
Contact information appears as shown in Mayflower.
Additional context
From HHS:
I've recently been made aware that some of our programs will be moving their physical offices a year from now. This will require us to update a lot of contact information.
The great thing about Drupal and our commitment to structured data is that we can easily update the contact information items and it will reflect across the site. However, this also brings up another concern. There are many times we have put contact information in rich text editors, especially on How to pages.
For each of our drop-downs on How to pages, we have wrote in the phone numbers, fax numbers, and mailing addresses in the rich text fields, in addition to having the contact item linked on them.
I know that for these pages, we will have to edit them manually. I was wondering if for the future, EOTSS could think about adding more functionality to how-to pages that could help alleviate this.
For example: if I were creating a drop-down for a mailing address, there could be a field underneath the rich text (but still within the "by mail" drop down) that could optionally link to and auto-populate from the contact information item on the How-to page. If that makes any sense.
I just worry that, in the long-term, the benefit of structured data in contact information items aren't realized due to still having to manually edit many if not most pages when these changes happen.
Is your feature request related to a problem? Please describe. As an author, I want to be able to add contact information to methods on how-to pages so that I don't have to change how-to pages if the contact information changes.
Describe the solution you'd like In addition to free text area for method, author is able to add a contact to a method and the contact information shown will be related to the method. (If phone is selected as method, then only the phone contact information will be shown.) Contact information appears as shown in Mayflower.
Additional context From HHS:
I've recently been made aware that some of our programs will be moving their physical offices a year from now. This will require us to update a lot of contact information.
The great thing about Drupal and our commitment to structured data is that we can easily update the contact information items and it will reflect across the site. However, this also brings up another concern. There are many times we have put contact information in rich text editors, especially on How to pages.
For each of our drop-downs on How to pages, we have wrote in the phone numbers, fax numbers, and mailing addresses in the rich text fields, in addition to having the contact item linked on them.
Examples (open the drop-downs):
https://edit.mass.gov/how-to/register-as-a-temporary-nursing-service-agency https://edit.mass.gov/how-to/apply-for-an-ambulance-service-license https://edit.mass.gov/how-to/apply-for-an-initial-emt-advanced-emt-or-paramedic-certification
I know that for these pages, we will have to edit them manually. I was wondering if for the future, EOTSS could think about adding more functionality to how-to pages that could help alleviate this.
For example: if I were creating a drop-down for a mailing address, there could be a field underneath the rich text (but still within the "by mail" drop down) that could optionally link to and auto-populate from the contact information item on the How-to page. If that makes any sense.
I just worry that, in the long-term, the benefit of structured data in contact information items aren't realized due to still having to manually edit many if not most pages when these changes happen.
Reference JIRA DP-4538