Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add how to request a full name #404

Closed
kelliedesigner opened this issue Nov 7, 2018 · 4 comments

Comments

Projects
None yet
2 participants
@kelliedesigner
Copy link
Contributor

commented Nov 7, 2018

As a consumer
I want to know how best to request a full name
So that my product is consistent with other ones

Based on feedback, there is confusion about whether 'Full name' can be separated into two Single Line Text Controls of 'First name' and 'Last name'.

This ticket is to add guidance either in Single Line Text Control or in Patterns.

@kelliedesigner

This comment has been minimized.

Copy link
Contributor Author

commented Nov 7, 2018

My response to feedback:

‘Full name’ is the optimum solution to be used when:
building something from the ground up
you don’t have back-end or legacy constraints
there is no user need to separate the name

The reason full name is best practice for users is that it caters to all variations and cultures.

Some people don’t have a last name (ie Burmese), have several last names (ie Portuguese), or their last name and first name is switched (ie Chinese).

However, when the optimal solution cannot be implemented, it is absolutely fine to go with two fields of ‘First name’ and ‘Last name’, such as when:
you’re working on an already existing site
you have to interface with legacy back-end systems that already separate the two
there is a need to have the name separated (for example you will be sending out emails that say ‘Dear [FIRST NAME]’

@kelliedesigner

This comment has been minimized.

Copy link
Contributor Author

commented Dec 3, 2018

On discussion, it was decided to go into Patterns as guidance without an example implementation

@kelliedesigner

This comment has been minimized.

Copy link
Contributor Author

commented Dec 3, 2018

On discussion it was decided to add this to Patterns as guidance without example implementation

@jeddy3 jeddy3 added type: story and removed type: bug labels Dec 4, 2018

@jeddy3 jeddy3 changed the title Fix guidance on Single Line Text Control when being used for Full name Add how to request a full name Dec 4, 2018

@kelliedesigner

This comment has been minimized.

Copy link
Contributor Author

commented Dec 11, 2018

Names

Use this pattern when asking for names. You should:

  • only ask for names when absolutely needed
  • support all characters users may need to enter
  • avoid asking for title

Where possible use a single name field to accommodates the broadest range of name types.

If your product needs to reliably extract first name and last name, use multiple name fields.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.