Knowit.ContentTypeLocalizationProvider 1.0.2

Knowit.ContentTypeLocalizationProvider

Optimizely localization provider that provides automatically generated localization keys for content types (Pages, Blocks, Media etc.) which can be used to localize content types with Knowit.ResourceEditor.

Installation:

dotnet add package Knowit.ContentTypeLocalizationProvider --source https://www.myget.org/F/creuna-nuget/api/v3/index.json

After installation:

• Open Startup.cs
• Register ContentTypeLocalizationProvider services with extension method AddContentTypeLocalizationProvider
• Add name for registered localization providers passing it as parameter to methods AddEmbeddedLocalization/AddLocalizationProvider

example:

    public void ConfigureServices(IServiceCollection services)
    {
        if (_webHostingEnvironment.IsDevelopment())
        {
            AppDomain.CurrentDomain.SetData("DataDirectory", Path.Combine(_webHostingEnvironment.ContentRootPath, "App_Data"));

            services.Configure<SchedulerOptions>(options => options.Enabled = false);
        }

        services
            .AddCmsAspNetIdentity<ApplicationUser>()
            .AddCms()
            .AddAdminUserRegistration()
            ;

        services
            .AddContentTypeLocalizationProvider()
            .AddLocalizationProvider<ContentTypeLocalizationProvider>("ContentTypeLocalizationProvider");
    }

• Configure ContentTypeLocalizationProvider via code implementing configuratoin action

example:

    services.AddContentTypeLocalizationProvider(options =>
        {
            options.ContentCultureName = "en";
            options.ContentAssemblyNames = new List<string>
            {
                typeof(Startup).Assembly.GetName().Name!
            };
        });

or/and configure via 'appsettings.json' (configuration in appSettings.json has highest proirty over configuration in code)

example:

    "ContentTypeLocalizationProvider": {
        "ContentCulture": "en", // Content culture name. By default 'en' is used
        "ContentAssemblyNames": [
          "WebSiteName" // Assembly names containing content types. By default executing Web App assembly is used
        ]
        "TranslateContentGroups": "false", // Specifies if content groups should be translated; Default is 'true'
        "TranslateContentTypes": "false", // Specifies if content types should be translated; Default is 'true'
        "TranslateCategories": "false" // Specifies if categories should be translated; Default is 'true'
      }

• Update ResourceEditor configuration - add ContentTypeLocalizationProvider in 'DefaultResourceProviders' (not required): example:

    services.AddResourceEditor(options =>
    {
        options.DefaultResourceProviders = new List<string>
        {
            ...,
            "ContentTypeLocalizationProvider",
            ...
        };
        ...
    });

How to use

Content groups, content types and categories can be translated in Resource Editor