Local Resources

[colinmurphy01]

User stories

• 4.5 – I want to understand the actions or steps I could take to save my life or property at my location

Acceptance Criteria

Public users can...

• Navigate to a location page within the target county and see any hazard products if they apply
• View local resources adjacent to the hazard products
• Click any link within a local resource and be directed to the new page If link is a phone number, call on an enabled device
• If link is to a non-government site see the link as such using the uswds launch icon that is associated with usa-link--external

Content creators can...

• Create a new local resource
• Author the content
• Link the resource to a specific hazard type
• Link the resource to a specific location (county for MVP)
• Publish the resource
• View any resources authored for a given county

Implementation details

There is a many-to-many relationship between content items, hazard types, and counties. An content item can apply to multiple hazard types and counties. Similarly hazard types and counties will be associated with multiple content items.

• Design brief
• Annotations for authoring
• Annotations for content table
• Reference examples: All hazards, Specific hazards

[colinmurphy01]

This will definitely need to be broken into multiple:

• Hosting and rendering the content
• Incorporating counties into our db and correlating content to counties

[colinmurphy01]

@klsheets can identify shape files of CWAs across all WFOs.

[colinmurphy01]

@greg-does-weather I'd like to consider this for this upcoming sprint so that we're continuing to build some public facing components each sprint.

[greg-does-weather]

We can make it aspirational, but I don't know if it can be done next sprint or not. We don't have the technical infrastructure to support this ticket yet. Specifically, we have not yet introduced counties into our database. There has been some prototyping work around it and we're going to start figuring out how to get it deployed this week.

The county data we've prototyped currently has no relationship with WFOs, but that part shouldn't be a significant time sink. And there will be admin UI customization requirements because we'll be creating an entirely custom field (county) that is not content-managed, and Drupal does not provide a native way of display non-content-managed fields.

I wasn't prepared to start breaking this ticket down yet because I didn't think we were ready to pick it up, but if you want to pull it forward, I can create the associated tickets now.

[colinmurphy01]

Parts of work

• Load CWA file
• Admin interface
  • Blocked: Need users, associated with WFOs
  • Populate counties in CMS based on WFO
• Content component

[colinmurphy01]

There's an initial draft for the blocked component of this in #650.

We would need to to also determine if workbench is a sufficient tool for this.

[colinmurphy01]

Next biggest step here is to figure out how we want to bring in county data into the Drupal authoring experience and then associate content with the content