Fab

@tvdeyen do I close this or leave it open? It provides full imprint / impressum via the store resource. I extended the structured data model on schema as well.

> Yeah, I'm with @mamhoff. There ware services out there that handle name as a unified field, which is preferable due to... reality. @jarednorman I know it's from a technical...

> I am imagining a `firstname` attribute and use the current `name` attribute as either the full name or last name. ok, that's not stupid as we can reuse most...

Ok, so here's probably the easiest way to do it then: - we do not reintroduce last name - we use name as last name - we reintroduce first name...

@tvdeyen I don't want to argue about naming schemes, buuuuuuuuuuuttttt: > Oh, and maybe we should call the field "given_name"? 🤔 Microsoft: first_name Google: first_name Shopify: first_name BigCommerce: first_name >...

@jarednorman @tvdeyen @kennyadsl we would appreciate if you three find a consensus to work one.

> For the Spree::Config UI, I'm not in favor of that for a couple of reasons: > > * we have a lot of similar configs, why is this the...

> I do think this should be configuration option to be set by store operators in code. Switching this option will lead to inconsistencies in address storing and display, and...

On my eternal journey to get crucified here :D So the current setup in this PR does not force the use of First_name last_name as name is only overwritten if...

@tvdeyen @kennyadsl @jarednorman Could one of you please write down clear direction where this heading? I know this is again being perceived as one of my crusades, but there's no...