Episerver is now known as Optimizely. For the consistency, the documentation and Smartling interface refers to this software as Episerver.
Episerver is a Content Management System (CMS), which provides an online platform for e-commerce and digital marketing through its Digital Experience Platform.
Episerver is built with .NET technology, which has two branches that are incompatible with each other: Framework and Core. Framework works on Windows only. Core works on Linux, MacOS, and Windows. There are Smartling Connectors for both branches:
Once you have installed the correct package for the branch you are working with, you can proceed to configure the connector before translating your content.
How the Episerver Connector Works
Smartling’s Episerver Connector automatically ingests your localizable Episerver content into Smartling, allowing you to authorize this content for translation from within the Smartling platform. Translations are automatically sent back to Episerver once complete. It also provides dynamic context for your content so that translators can see how each string will fit into your translated sites.
Ensure Content is Localizable
Content for translation must be contained with a localizable property in Episerver. If a content type does not have the unique value per language setting enabled, the connector cannot ingest the content for translation. This results in missing components on translated sites. To ensure components are not missing, you can set up a fallback language for each language in Episerver. This will insert the component in the selected fallback language, so it is not missing in the translated site.
Smartling’s Episerver Connector currently ingests four content types from within the Episerver platform;
- Episerver Projects content
- Episerver Blocks content
- Episerver CMS content
- Episerver Commerce content
Episerver Asset List
You will find Episerver content listed in the Episerver tab of your Smartling project. You can view the Asset Name, the Smartling translation status, the Episerver workflow status, the Asset Type, and the Last-Modified timestamp. Use the Episerver Content filter to toggle between content types. Episerver Projects is the default content filter selection.
Each of the content types listed is managed separately from within the Smartling platform, allowing greater control over the translation management of each. Every time you toggle between each of the Episerver content types within the Smartling platform, Smartling will check the Item within Episerver for new content. This will then be displayed in Smartling, according to the nesting structure in Episerver, ready to authorize for translation.
You can sort the asset list by Episerver structure (default) or asset name descending/ascending.
Search & Filter for Episerver Content
The asset filters are divided into two parts - Episerver Filters, containing options configured from within your Episerver account, and Smartling Filters, containing options configured from within your Smartling account. The filters are dynamic and change to the relevant filter depending on the Episerver Content chosen.
When you want to view or action assets within your Episerver Projects, simply filter the Episerver Content to Episerver Projects and choose a project from the Project dropdown. You can further refine your search by choosing a content type related to your Episerver Project. The content types listed are Block, CMS, and Commerce.
This filter-set will return a flat list as there is no hierarchy structure to Episerver Projects.
When you want to view or action assets within your Episerver Blocks, simply filter the Episerver Content to Episerver Blocks. You can further refine your search by choosing a specific block from Episerver, under the Block Type dropdown.
This filter-set will return a nested list as there is a hierarchy structure to Episerver Blocks. A breadcrumb of your nested list will appear on the top of the asset list.
When you want to view or action assets within your Episerver CMS instance, simply filter the Episerver Content to Episerver CMS. You can further refine your search by choosing specific content from Episerver CMS, under the Content Type dropdown.
This filter-set will return a nested list as there is a hierarchy structure to Episerver CMS. A breadcrumb of your nested list will appear on the top of the asset list.
When you want to view or action assets within your Episerver Commerce instance, simply filter the Episerver Content to Episerver Commerce. You can further refine your search by selecting a specific catalog from Episerver Commerce, under the Catalog dropdown.
Catalog's include display names in the asset list, which are also searchable in the global search.
This filter-set will return a nested list, as there is a hierarchy structure to Episerver Commerce. A breadcrumb of your nested list will appear on the top of the asset list.
Episerver workflow statuses
|It is likely you will be translating Published content from Episerver, as the content found on other workflow steps may be updated before publishing.|
||This search will apply to your current filter set|
Completed: all content translated and successfully delivered to Episerver. Smartling Connector starts to track changes in the source content.
Failed: a fatal error occurred, neither progress nor source content is tracked
|Language||List of target languages configured in Smartling's Linguistic Assets for the Episerver project||Target Languages must also be configured in Episerver and mapped in the Episerver Configuration found in the Smartling Project Settings.|
Navigating the Asset List
For all Episerver Content types, excluding Episerver Projects, the Asset List can be hyperlinked to bring you through the hierarchy structure, as laid out in your Episerver platform. You will see an icon that represents the type of Episerver content the asset belongs to. There are icons for pages, folders, variants, categories, and blocks.
The information icon links to the Asset Details page. Here you can see further information on that asset, including the translation status for each language. From here, you can also Request Translations or Export Translations for that specific asset.
This shows the current translation status for the asset, combined for all locales. The statues that exist are;
- Not Translated - the asset has not been requested for translation for any locales
- In Progress - the asset is in an In Progress or New state for at least one locale, and no locales are in a Failed state
- Failed - at least one locale is in a Failed state
- Complete - the translated asset has been returned to Episerver for all requested locales
This shows the Episerver status for the item. The statues are Draft or Published.
This will provide the user information about the asset's content type within Episerver, such as CMS, Commerce, Blocks and it will also provide the specific sub-content type that it belongs to.
This will provide the date the asset was last updated in Episerver.
Above the Asset List will display the hierarchy breadcrumb for CMS, Commerce and Block content. The breadcrumb is a representation of their current position in the Episerver hierarchy and structure for blocks. This breadcrumb will update as you navigate within the structure.
To the right of the breadcrumb, you will see a magnifying glass icon - this is the Global Search. You can use the Global Search to search for all Episerver assets within the chosen content type, CMS, Blocks, Commerce. This search does not apply to Projects.