Open stuartpb opened 9 years ago
So, the thing to note here is that name
is usually not different between localizations, which is why it isn't considered "freeform" like the other #12 fields.
There are some sites, in the minority, where it is, which is what this issue is about: how those sites should be modeled.
A good starting point would be identifying which sites work this way, and in what other aspects they tend to differ. If it's usually just the name, there'll probably be something like a "localnames" field (until some stroke of brilliance occurs in some far-future schema that moves localnames
into an elegant structure of more complex localizations that's justified by some large contingent of sites and a real application need).
12 proposes a "markets" array, where "market" here means "a locale where aspects of a site operate differently". (The slightly-less-general example is giving alternate versions of a site's name.)
This is generally handled by new profiles, really. If localization is not part of the domain, it's kind of out of scope?
I think names should maybe just be special-cased.