Where and how do we store Geo/Locale configuration?

[DipanshuHandoo]

Since we will be using localization, English copy and several other things where we need a locale list. Where and how do we are storing that configuration?

[vhargrave]

The locales that are being used for your project are defined in the scripts/scripts.js file. Here's an example from milo, and another example of a project using milo (bacom).
Once those entries are set by the project developer, authors can then create that locale folder structure and pages in sharepoint.

[DipanshuHandoo]

@vhargrave : why don't we save this as Excel/JSON in SharePoint instead of coding it statically in JS? We will have 1 less dependency if we save it in SharePoint itself.

[vhargrave]

@DipanshuHandoo That would be another request which costs us site speed. Additionally we're configuring extra things for each locale , which is probably not too interesting for authors, but necessary from a developer standpoint. I think we're trying to keep dev configuration in the code, and author configuration in sharepoint.

[honstar]

Ideally, we should be standardizing the list of locales across milo and consumer projects. It looks like both milo and bacom are exact replicas already when it comes to the list of locales.

[auniverseaway]

Ideally, we should be standardizing the list of locales across milo and consumer projects.

Milo supports more lang / locale variations than Dexter ever did. Many sites are either lang only (blog, business blog) have a subset of content (stock), have no locales (ABP Docs, Clio), or are our traditional sites (bacom, milo, acrobat). Standardization is not really possible without having other downsides.

[vhargrave]

agree