google / google/site-kit-wp

Revise wording on the congratulations screen after Site Kit is set up

Open
#7,089 0 comments 0 reactions 0 assignees View on GitHub
Language Type: Enhancement Type: Support
Dominant language
JavaScript
Stars
1.4k
Forks
383
Avg merge
4d 14h
Merged PRs (30d)
77

Description

In order to increase users awareness of possible permissions errors, revise the wording on the congratulations notices after Site Kit is setup. Revised wording could include a mention on what services are already connected, with an example below:

```
Congrats on completing the setup for Site Kit!

You can now view insights in Site Kit for all Google services that you have access to. This site’s connected services are:
- Search Console
- Google Analytics
- AdSense

Connect more services to see more stats. [Go to Settings](https://plastiskip.com/wp-admin/admin.php?page=googlesitekit-settings#/connect-more-services)

```

Below you'll see the current congratulations screen. Note that this is also the congratulations screen that appears if all modules are successfully connected, even though we're suggesting users connect more services.

![image](https://github.com/google/site-kit-wp/assets/41326532/328ce459-6cee-46eb-9bfe-db7abc32e216)

The above suggestion is one suggestion based on some support testing for secondary administrators setting up the plugin. More [insights here](https://app.asana.com/0/1185360131189553/1204563795499396/f).

---------------

_Do not alter or remove anything below. The following sections will be managed by moderators only._

## Acceptance criteria

*

## Implementation Brief

*

### Test Coverage

*

## QA Brief

*

## Changelog entry

*

Contributor guide

Open the contributing guide

Research direction

Start by locating the congratulations screen shown in the issue and inspect how setup completion and connected services are represented. Update the wording to explain available and connected services, include the Settings link, and verify the result for both partial and fully connected setups.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.