Skip to content
This repository was archived by the owner on Sep 11, 2025. It is now read-only.

Incident response use case /non-blocking feedback#5297

Merged
bretthayes merged 46 commits intomainfrom
tim/incident-response-use-case-non-blocking
May 11, 2022
Merged

Incident response use case /non-blocking feedback#5297
bretthayes merged 46 commits intomainfrom
tim/incident-response-use-case-non-blocking

Conversation

@zlonko
Copy link
Contributor

@zlonko zlonko commented Apr 26, 2022

This closes #5287. Here, we implement the remaining feedback from our Marketing stakeholders, re: copy updates, a changed icon, and logo treatment.

The QA doc can be found here.

Notes

  • Crosshairs icon changed to magnifying glass
  • Copy changes in CustomCarousel
  • Copy changes in blog descriptions
  • Reformat "What does it mean for you?" on this and other Use Case pages
  • Center and slightly enlarge Cloudflare logo in feature box

Testing

  • Open use-cases/incident-response
  • Check that the updates marked "Non-Blocking" in the QA doc are accurate
  • Test the static build

@zlonko zlonko added team/content-platform marketing-request Used by CPT to indicate requests from the Marketing Team labels Apr 26, 2022
@zlonko zlonko added this to the A - Sprint 3 milestone Apr 26, 2022
@zlonko zlonko self-assigned this Apr 26, 2022
@zlonko
Copy link
Contributor Author

zlonko commented Apr 26, 2022

@elzannewentzel This is almost ready for Engineering review. Two comments about the "Incident response is stressful and overwhelming" section are unresolved, so I left a follow-up reply in the doc.

Edit: All clear!

@elzannewentzel
Copy link
Contributor

@zlonko Thank you, agree with the plan 👍 I've asked Jenny to confirm blocking feedback for #5259

@zlonko zlonko mentioned this pull request Apr 28, 2022
@bretthayes bretthayes linked an issue Apr 28, 2022 that may be closed by this pull request
Base automatically changed from incident-response-use-case to main May 2, 2022 18:07
@zlonko
Copy link
Contributor Author

zlonko commented May 2, 2022

@elzannewentzel To keep things moving today, and because we are awaiting feedback on non-blocking feedback here, I went ahead and deployed #5259 with the intent to push this branch into main once it is ready.

Copy link
Contributor

@bretthayes bretthayes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like there's a merge conflict to fix. After that, I think this should be good to go.

@bretthayes bretthayes modified the milestones: A - Sprint 3, A - Sprint 4 May 10, 2022
@zlonko
Copy link
Contributor Author

zlonko commented May 10, 2022

Nice! I resolved the conflict. It looks about ready for your final take @bretthayes!

@bretthayes bretthayes merged commit e70a5fb into main May 11, 2022
@bretthayes bretthayes deleted the tim/incident-response-use-case-non-blocking branch May 11, 2022 19:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

marketing-request Used by CPT to indicate requests from the Marketing Team

Projects

No open projects
Status: Done

Development

Successfully merging this pull request may close these issues.

Non-blocking feedback for Incident Response Use Case Page

5 participants