Design and build information that can accommodate any name.
names info design
I spent weeks, probably hundreds of hours, researching names, trying to find different patterns and different taxonomies before finding W3C and Wikipedia examples like Akan names, Indian names, and African-American names.
names info design
Part of the 26 cultures researched, as noted in Names taxonomy.
names info design
So, we’ve acknowledged that the current construct is US-centric, and the US has patterns of cultural fuckuperry.
names info design
Legacy Our legacy standard is first_name:text, which we’re already shifting conceptually to given:text. In the legacy construct, the field name – e.g., first_name or given – is the category.
names info design
Legacy Our legacy standard for interfaces between governed and ungoverned data fields is pretty strict. Text field goes to ungoverned data. Dropdowns, checkboxes, radios, toggles go to governed data.
names info design
Understanding the name structure doesn't mean we now know all the ways to refer to them based on context, (presumed) relationship, legal form, etc. Broaden the cultural context enough, and even the legal name shifts in expectation.