I went through the UI and saw several problems:

1) The "Use addressbook" checkbox has no help text, which is a bit confusing.
2) The edit and delete profile user pages have no breadcrumbs.
3) The user pages have badly set titles:

  'title' => ucfirst($type) . ' Profiles',

This is hard to translate (a placeholder should be used for the type name). And if the type name has an underscore, it won't be converted. Generally, we are inventing our own label based on the type machine name, which isn't pretty.
4) We have inconsistent language, showing on checkout "Addresses on File", but then in the user pages (under the "addressbook" url) we talk about "profiles", not addresses. I'm thinking about hiding the "profile" terminology from users and just going with "address". Thoughts?
5) The delete profile page doesn't use confirm_form(). A nice trick would be to use entity_view() to show the information being deleted. Commerce only does this for products, but it would be a great solution here.

There's also the question of keeping the "Summary" page, which doesn't have much utility right now.

Comments

bojanz’s picture

Status: Active » Needs review
StatusFileSize
new53.42 KB
new47.65 KB
new71.69 KB
new20.14 KB
new39.72 KB
new60.06 KB
new5.4 KB

Here's a proposal that addresses the five points I mentioned.
Not sure about the "address" terminology because the profile can have a phone number field (for example), and that is shown separately on the add / edit form (outside the "address" fieldset). Still, at least it's consistent.

Posting as a patch instead of committing because I want us to agree on the final UI look before merging this code upstream.

78doog’s picture

I think the UI changes are very good and the use of english much clearer for customers. My only suggestion is that the phrase "Deleting this address cannot be undone" is a little daunting to users and they can re-add any address later if they like. I think "remove" is better than "delete" in general. I would change the button to "Remove Address" and also say underneath "You can always add it again later." Colloquial and encouraging...... hopefully. I'm sure someone will have a better idea though.

liupascal’s picture

These changes looks good to me - we definitely need a more "generic" approach and keep away any technical terms.
As for #2 comment, I think this is the core behavior to have this text, but I agree on your idea.

bojanz’s picture

Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.