WFO Promo Component

[kmranjo]

Build ticket based on outcomes of #181

Goals

Provide a quick introduction to the WFO responsible for the forecast, with a quick path to contact the office or learn more about it.

Related user needs

1.1 - I want to know how NWS serves my priorities 1.2 - I want to know who creates forecasts and hazards, and how they create them 6.1 - As a partner, I want to know who and how I can reach out to someone when I need to

Dependencies

Need to settle on a method by which we associate a piece of content with a specific WFO (tagging? dropdown? other?)

Content

All content is authored in the CMS

• WFO shortcode (required, but may be auto populated, eng TBD)
• WFO name (required, but may be auto populated, eng TBD)
• URL to WFO page (required)
• WFO phone number (optional)
• Short intro text (required, 150 characters)
• URL to WFO Facebook page (optional)
• URL to WFO Twitter account (optional)
• URL to WFO YouTube account (optional)

WFO Name is an H2 Intro text is plain text only, no styling elements needed

Behavior

• Any optional fields not authored do not appear in the published component
• For social media links, the icon for the platform appears only if the URL for that platform is authored
• The component cannot be published if required fields are not authored
• Only one instance of the component can exist for each WFO
• Display conditions: For any location page, the system detects which WFO covers that location and populates the corresponding instance of this component

Acceptance Criteria

Site users should be able to

• Navigate to their location page via search or direct link
• View the component on the page
• Read the text (heading, WFO name, intro, phone number, social media promos)
• View the images (social media icons)
• Click the phone number to call from any call-capable device
• Click the WFO name to navigate to the WFO page
• Click any social media icon to navigate to the social account for that office
• Content creators should be able to

Open the WFO promo component tagged for their WFO

• Author content within the component
• Publish the component

Content admins should be able to

• Create a new WFO promo component
• Tag the component for a WFO (or select from menu)

Example captured in document

[greg-does-weather]

Holding for #660 because that introduces a WFO taxonomy we will use for this content.