Automattic / Automattic/wp-calypso
Improve Suspended Site Notification for Jetpack Sites
- Dominant language
- TypeScript
- Stars
- 12.6k
- Forks
- 2k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 552
Description
**Current Notification**
I tested suspending a Jetpack site of mine as part of some TOS guidelines being rolled out:
**Problems**
- The language is WP.com specific and doesn't make it clear what will actually happen to the site.
- The TOS page sends me here: https://en.wordpress.com/tos/ rather than to Jetpack TOS.
- It sends me [here](https://wordpress.com/error-report/?url=495@rewindddd.mystagingwebsite.com) to get help which I'm not sure will pull in Jetpack specific information (ie the wrong set of HEs might receive it).
cc @davidwatkis as an FYI
Contributor guide
Research direction
No file or test is named; start by locating the suspended-site notification in the TypeScript/React codebase and reviewing the attached screenshot. Compare the notification's wording, TOS destination, and help-reporting route with the three problems listed, and consider the work done when all three are appropriate for Jetpack sites.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100