e3.v6 wfo attribution

[janelx]

Goal

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

Supported user stories

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

CMS needs the ability to map a geographic location to a specific WFO based on coverage area

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

• Display conditions: For any location page, the system detects which WFO covers that location and populates the corresponding instance of this component
• 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

Example in document here

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)

---

Review: design, function and flow:

• [ ] POs - org alignment and vision review
• [ ] Eng - feasibility and right-size
• [ ] UX - what and how to test

[colinmurphy01]

Prioritized for Sprint 3.3.

This will be included in #248 based on MVP WFO recommendation from #165:

[janelx]

@colinmurphy01 I think we might need an additional user story as this one doesn't really match the attribution one. BUT updated weather story covers attribution. Here is what I was thinking the value of showing this on the page, if we don't have something from the from trust and authority exercise

Value:

• Show NWS has physical offices with specialist monitoring weather for their state
• More inviting to the public and increase access to public participation
• Prepare for future state where people can learn more, or if link is included
  • Access point to learning more public education events
• Sense of place, reinforce forecaster's familiarity of how weather affects the location

[colinmurphy01]

Closing this as it's being stubbed in Greg's work implementing the point location page #248.

The refinements noted above will be considered in #461

[colinmurphy01]

Re-opening this ticket. We have a placeholder in beta, however this hasn't been designed or implemented into the CMS.

[kmranjo]

Updated to reflect latest recommendations based on content models and user feedback. I believe next steps are:

• [ ] Design review to get alignment on approach
• [ ] Eng review to flag the technical dependency
• [ ] Update and add visual designs to the ticket (this would make it ready for eng?)
• [ ] Build

[colinmurphy01]

Should this be added to today's co-work agenda, or wait till Igor's back?

[kmranjo]

It's pretty basic so we could maybe chat about it briefly during cowork and then he could look at it when he's back? It does still need his alignment, but I don't expect any surprises with this one.

[kmranjo]

@colinmurphy01 So for this one since we have alignment does it go straight to eng with a build ticket? And am I right you don't want to repurpose this ticket for the build, but I should make a new one with all this info in it but tagged for eng? Sorry, still getting a feel for the ticket progression.

[colinmurphy01]

Yes please do that to just get in the habit of closing tickets and opening eng tickets as the last step.

Since it's EOD, you can do that Monday AM.

[kmranjo]

Opened #597 for next steps, moving this one to done