This article is for Developers using the Global Delivery Network.
The Smartling Global Delivery Network (GDN) supports a list of pre-defined classes and tags that you can add to your source code which instruct Smartling to handle the translation or rendering of your translated site in a particular way.
Integrating at your source code level is the most stable and scalable way to customize the behavior of the GDN to suit the needs of your organization. This approach allows you complete visibility and control of your integration points so your team can develop your site code with localization in mind.
The out of the box tags that can be applied to your source code are documented in the table below:
| Name | Function | Markup |
| Hide Class | Hide source element from all translated sites | sl_hide |
| Javascript Tag | Capture Javascript content for translation | <sl:translate> |
| JSON Tag | Capture JSON content for translation | sl_translate, sl_all, sl_none, sl_notranslate |
| No Rewrite Class | Prevent link rewriting | sl_norewrite |
| No Translate Class | Prevent capture and translation | notranslate |
| Opaque Class | Prevent link rewriting AND translation | sl_opaque |
| Plural Class | Identify strings with plural forms | sl_plural |
| Search Class | Integrate embedded search | sl-search-input, sl-search-keyword |
| Sort Class | Sort dropdown values alphabetically after translation | sl_sort |
| Split Class | Change content segmentation | sl_split |
| Swap Class | Display different content than source site, by region | sl_swap |
| Translate Class | Translate HTML element not captured by default | translate |
| Variant Attribute | Create variant for identical string | data-sl-variant, data-sl-attr-variant, sl_variant |
| Whiteout Class | Obscure sensitive data | sl_whiteout |
If you are unable to alter certain areas of your source code, there are other methods that can be used to control GDN behavior. Read more about these strategies here.