/localization-provider-opti

Database driven localization provider for Optimizely (ex. Episerver) websites

Primary LanguageC#Apache License 2.0Apache-2.0

Quality Gate Status

Supporting Localization Provider

If you find this library useful, cup of coffee would be awesome! You can support further development of the library via Paypal.

Localization Provider v8.0 IS OUT!

Read more about v8.0 release here.

What is the LocalizationProvider project?

LocalizationProvider project is Optimizely localization provider on steroids.

Giving you the main following features:

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

Source Code Repos

The whole package of libraries is split into multiple git repos (with submodule linkage in between). Below is list of all related repositories:

Getting Started

Working with DbLocalizationProvider

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

Integrating with Optimizely

How to Contribute

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

Forking and cloning the repo is the first step you do. Keep in mind that the provider is split into couple of repositories to keep things 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

Other Versions

v7.0 is OUT

Please read more in this blog post!

Migrating from v5.x?

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

More Info