Update "detach" language for navigation block and synced patterns flow

[annezazu]

Currently for both the Page List block in the Navigation block and Synced Patterns, we use the phrase "detach", which while technically accurate isn't terribly user friendly. This came up as part of the Hallway Hangout on improving accessibility in the Site Editor as it's both not clear to sighted and visually impaired users (not to mention the i18 impact).

Here's a video showing both experiences:

detach.language.mov

Let's throw out some new language options and get some copy help. For starters, I'd love to have these two flows use the same language but it may not make sense to. For example, for the navigation block, it might make more sense to just say "Confirm" rather than "Detach". For patterns, we could go back to the "convert to blocks" language.

[richtabor]

I'm not sure of a different verb that helps denote the breaking away of the synced set. It's worth noting that Figma uses detach as well. Notion uses "unsync". Know of others?

[annezazu]

I'm not aware of others but will start paying attention. ChatGPT offers unhook, unlink, release, untie (none I like). My mind goes to disconnect or separate. I agree though, it's tricky to get right but the current phrasing isn't immediately clear.

[getdave]

This page list is synced with the published pages on your site. Detach the page list to add, delete, or reorder pages yourself.

In the specific example of the Navigation block we could make the wording (shown above) more user friendly and less technical. It should describe what will happen rather than what is happening technically.

How about something like...

The page list displays your site's published pages. If you choose to edit the list, you will be able to independently adjust navigation items, but your navigation will no longer automatically update with changes to your site's pages.

Also cc'ing @alexstine for his opinion as he had specific comments about the wording in the referenced Hallway Hangout.

---

Question: if we go ahead with changes should the buttons be updated to be more of a "confirmation" (e.g. "Confirm", "Cancel"). Certainly "Detach" is not a good term here.

[richtabor]

Question: if we go ahead with changes should the buttons be updated to be more of a "confirmation" (e.g. "Confirm", "Cancel"). Certainly "Detach" is not a good term here.

The affirmation action should be relative to what invoked the modal. For example, the "Create pattern" control opens a modal titled "Create pattern" and the action is "Create".

Following this, the action should be "Edit".

[alexstine]

👍 Thanks.

[annezazu]

Reopening as synced patterns remains an issue.