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

Localized variants ("markets") #17

Open
stuartpb opened this issue Apr 12, 2015 · 1 comment
Open

Localized variants ("markets") #17

stuartpb opened this issue Apr 12, 2015 · 1 comment

Comments

@stuartpb
Copy link
Member

#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.

@stuartpb stuartpb changed the title Localized variants Localized variants ("markets") Apr 12, 2015
@stuartpb stuartpb added this to the future milestone Jun 9, 2015
@stuartpb
Copy link
Member Author

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant