AiTO.CMS.Translation.Extension 1.3.3

AiTO CMS Translation Extension for Dynamicweb 10

AiTO CMS Translation Extension for Dynamicweb 10, developed by Mardi Gras, simplifies the export and import of translatable CMS content. The app supports text fields from pages, paragraphs and Swift 2 item types. Content is exported in a translation-friendly format and imported directly back into the correct language version, reducing manual work and minimizing errors.

Key Features

• Effortless Export: Export the translatable text of a language website, or of selected pages, to a JSON file or an XLIFF 1.2 file for your translator or translation tool. Text fields from pages, paragraphs and item types (Swift 2, Swift 1 and custom) are included, along with nested items such as slides and accordion items and the labels of buttons. Layout and design settings are left out. Choose the pages (the whole website, or selected pages with or without their sub pages; optionally skip unpublished pages or pages exported before) and the texts: all texts, untranslated texts, outdated texts (the source changed after translation), texts whose source changed since they were last exported, or texts whose source was changed after a given date. Export SEO fields only or everything except them, and leave out texts marked as translated.
• CAT Tool Support (XLIFF): Translate in Trados, memoQ, Phrase, Smartcat, Redokun or any other tool that reads XLIFF 1.2. Texts are split into one segment per sentence, so your translation memory gets the best matches. The source is the master website's text, existing translations are included as targets, and HTML markup and Dynamicweb template tags (such as {{Ecom:Order.Customer.Name}}) are protected as placeholders so translators only see the text.
• Seamless Import: Import the translated file (JSON or XLIFF) directly back into the correct language website. Only text is written, and fields that already have the translated value are left untouched. The result of the import stays on screen, with a link to the fields it changed.
• Safe Import with Preview: Before importing, see how many fields will be updated and which fields were changed in the CMS after the export. Those changes are kept unless you choose to overwrite them, and each one shows whether it came from an earlier import or a manual edit.
• Import History & Undo: Every import is logged with time, user, file and each changed field with its old and new value. An import can be undone; fields edited since the import are kept.
• Translation Status: See how much of each language website is translated, with an overview of key numbers and charts (progress per site, pages per site, all fields by status, translation activity per week). Drill down from site to page to field; rows are coloured green (translated), amber (partly translated or outdated) and red (not translated). Pages whose source text changed after they were translated are marked as outdated.
• Fix Single Fields: Edit a field's text directly next to the master text, or mark fields as translated when the text is correct as it is (names, numbers, terms that are the same in both languages). Both are logged in the import history and can be undone.
• File Management: Browse, download (several files as a zip), upload and delete export and import files directly in the backoffice.

Getting Started

All features are found in the Translate area of the Dynamicweb Administration panel:

• Translation status — Overview shows key numbers and charts for all language websites; Language sites lists them, and a site opens its pages and a page its fields.
• Websites to translate — pick a website to see its language websites, then choose Export for translation.
• Import translations — select a translated file, review the import check and start the import. Import history lists earlier imports and lets you undo them.
• Files — the exported files and the files uploaded for import.

A typical workflow:

1. Export the language website (or the pages you need) from Websites to translate.
2. Download the file from the export screen or Files → Export and send it for translation.
3. Upload the translated file under Files → Import and open it in Import translations.
4. Review the import check, start the import, and follow the progress under Translation status.

What's New

1.3.3

• One segment per sentence in XLIFF: texts are split into sentences (and paragraphs, headings and list items) in the XLIFF file, so CAT tools such as Redokun, which use the file's segments as they are, show one sentence per row and your translation memory gets better matches. On import the sentences are joined again, with the HTML exactly as before.
• Cleaner segments in CAT tools: characters written as HTML entities (such as the apostrophe in Don't) are exported as plain characters instead of tags, and Dynamicweb template tags ({{Ecom:Order.Customer.Name}}) are protected as tags, so translators can't change them.
• Import result on screen: after an import, its result (fields and pages updated, conflicts, skipped fields and the message) stays on the import screen, green when it completed and red when it failed, with Show changed fields to see what was changed.
• Tooltips on every export setting.
• Fixes:
  • The internal names of item paragraphs (shown only in the backoffice's paragraph list, e.g. a name copied with the paragraph) are no longer exported; the item's title and texts still are.
  • Fields with nothing to translate (only template tags, numbers or spaces) are no longer exported or counted as untranslated in the translation status.
  • A failed export (e.g. no license, no file name) no longer leaves a blank screen with "Unknown layout type" errors.

1.3.2

• Fix: the export screen and the translation status lists showed "The view ... was not found" on sites that installed or updated the app from the App Store without a restart.
• Security: updated System.Security.Cryptography.Pkcs to 10.0.14 (fixes a known denial of service vulnerability in the version Dynamicweb references).

1.3.1

• Updated app description in the Dynamicweb App Store. No functional changes.

1.3.0

• Export options: export only untranslated texts, outdated texts, texts whose source changed since they were last exported or after a given date; include the sub pages of the selected pages (folders can then be selected); export SEO fields only or everything except them; skip unpublished pages, pages exported before or texts marked as translated.
• Translation status in the page selector: pages are coloured by their translation status when you pick pages to export, with the status in the page's tooltip.
• Back buttons on the export and import screens; Cancel on the text editor returns to the page's fields.
• Fixes:
  • Internal page links in texts imported from XLIFF now point to the language website's own pages instead of the master's.
  • JSON exports leave out empty lists and the item ids of paragraphs without item texts, so the file only shows what there is to translate.

1.2.0

• XLIFF 1.2 export and import for CAT tools (Trados, memoQ, Phrase, Smartcat and others).
• Translation status per field: open a page to see which fields are translated, edit a text, or mark fields as translated.
• Overview with charts of every language website's progress, and coloured rows in the status lists.
• Fixes:
  • Text that only differs from the master in its internal page links (which Dynamicweb points to the language website's own pages) is no longer counted as translated.
  • Text that still matches an earlier version of the master text (after a master edit or an undo) is no longer counted as translated.
  • Websites in the recycle bin are no longer listed.
  • The language website list counts only pages with text to translate.
  • The Back buttons in the status and import history screens keep the navigation intact after an action that reloads the list.

1.1.0

• Import preview with conflict check, import history with undo, translation status, file management (download, zip, upload, delete) and support for any item type, including nested items and button labels.

Installation

Option 1: Via Dynamicweb App Store (Recommended)

1. Log in to your Dynamicweb 10 Administration panel.
2. Navigate to APPS → Available apps.
3. Search for AiTO CMS Translation Extension.
4. Click Install. The system will automatically download and deploy the extension.

Option 2: Via .NET CLI / Visual Studio

If you are developing locally or prefer manual installation, add the package using the .NET CLI:

dotnet add package AiTO.CMS.Translation.Extension

License Activation

This application strictly requires a valid license key to function. The core export, import, undo and field editing features are locked and require an active license across all environments, including local development (localhost).

1. Log in to the Dynamicweb Administration panel.
2. Navigate to Settings → Apps settings → AiTO licensing.
3. Paste the license key provided to you by Mardigras.
4. Click Save. The application will instantly validate the key against your current domain.

To purchase a license key or renew an existing subscription, please contact Mardigras.

System Requirements

• Platform: Dynamicweb 10.27.10+
• Runtime: .NET 10.0+
• Deployment: Fully supports Dynamicweb SaaS Cloud & On-Premise environments

Support & Documentation

For complete documentation, integration guides, and support tickets, please visit our documentation site.

© 2026 Mardigras. All rights reserved. Proprietary License.