开源软件名称（OpenSource Name）：

开源软件地址(OpenSource Url)：

开源编程语言(OpenSource Language)：

开源软件介绍(OpenSource Introduction)：

DbLocalizationProvider for Optimizely CMS and Commerce (ex. Episerver)

v7.0 is FINALLY OUT!

Please read more in this blog post!

Supporting LocalizationProvider

If you find this library useful, cup of coffee at late night while library is being hacked around would be awesome! You can support further development via Paypal.

What is the LocalizationProvider project?

LocalizationProvider project is Optimizely localization provider on steriods.

Giving you main following features:

• Database driven localization provider for Optimizely websites projects
• Easy resource registrations via code (code-first apporoach)
• Supports hierarchical resource organization (with help of child classes)
• Administration UI for editors to change or add new translations for required languages

Getting Started

• Getting Started

Migrating from v5.x?

Please visit blog post to get more information about new features added in v6 and also how to migrate.

Working with DbLocalizationProvider

• For more info about generic localization provider features read more here

Integrating with Optimizely

• Working with Resources (Optimizely)
• Optimizely Frontend Localization
• Optimizely Xml File Migration

How to Contribute

It's super cool if you read this section and are interesed how to help the library. Forking and playing around sample application is the fastest way to understand how localization provider is working and how to get started.

Forking and cloning repo is first step you do. Keep in mind that provider is split into couple repositories to keep thigns separated. Additional repos are pulled in as submodules. If you Git client does not support automatic checkout of the submodules, just execute this command at the root of the checkout directory:

git clone --recurse-submodules git@github.com:valdisiljuconoks/localization-provider-epi.git

NB! As Optimizely repository contains 2 level (lib/netcore and lib/netcore/lib/localization-provider) submodules --recursive-submodules sometimes fails to detect 2nd level module. Then you can just step into netcore submodule folder and execute pull command there:

git submodule foreach git pull origin master

More Info (Some blog posts)

• Part 1: Resources and Models
• Part 2: Configuration and Extensions
• Part 3: Import and Export
• Part 4: Resource Refactoring and Migrations