Automattic / Automattic/wp-calypso

Replace matching blog address UI

Open
#95,071 1 comment 0 reactions 0 assignees View on GitHub
[Pri] Normal Enhancement Quality Sprint: Week 2
Dominant language
TypeScript
Stars
12.6k
Forks
2k
Avg merge
1d 18h
Merged PRs (30d)
531

Description

In [Improve "Change Username" Account Settings #94640](https://github.com/Automattic/wp-calypso/pull/94640), we are introducing several tweaks to the Change Username feature to simplify the interfaces.

There's one change we've decided to address in a separate PR related to the "Create a matching site" feature. Whenever a user changes their username, we give them the option to create a blog that matches their new username. The interface for this currently consists of a couple of radio buttons, which are not selected by default:

![image](https://github.com/user-attachments/assets/5ee226e7-1b10-4130-845b-ea0db32190ba)

The user can proceed without making any selection, resulting in only a username change with no site created. This UI is somewhat complex for its purpose, so I'd like to propose using a toggle instead:

![image](https://github.com/user-attachments/assets/df60fe2f-473b-4d3a-b3a8-c8b1377bc934)

Figma file: https://www.figma.com/design/wCm5Tzb7JBaG4WNowWbjES/Logical-Flows?node-id=5250-13523

Contributor guide

Open the contributing guide

Research direction

Start with the Change Username account settings flow described in the linked PR, then compare the current matching-site radio-button interface with the supplied Figma node. Replace that choice UI with the proposed toggle while preserving the username-change and optional site-creation outcomes. Done means the new interface matches the design and both paths remain available.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
design, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.