Two things to think about when you manage a site that has translations are how to reuse or make more simple updates.

Images – AR locale

Images such as your logo and possibly generic images on the site don’t have to be translated if they have no text in them and are appropriate for the locales. You can use the AR, All region, locale to import images that should be fallen back to for these items. AR locale gives you the ability to create graphics that can automatically go to the translated site with no updates or versioning. If you happen to find that you only have an image that relates to your US site then you can go into a system like AEM and create a US locale instead, even if you have an AR of the same image already created, you can still add locales over that and ensure through your fallback rules with IT that the locale versions such as US will override the AR locale.

Content Fragments

We recently started using content fragments as a way to do the old school method of include files. This means in your page template allow a content fragment to be added, then in your Experience Fragments area you create a component that can be used in your template pages. It’s an ingenious idea I’m not sure anyone else has tried but this means you go to your experience fragment to edit the text in the CF file and when you publish that file – all pages that have this CF will update accordingly. It’s an amazing new feature in Adobe AEM.

Global Dictionary

This item is used to store labels in your CMS and in your page design, (that are usually replicated across many pages), in giving you the ability to have one source update of the text and ability to customize the translated text you need for this label across your sites.

Items like navigation links that need to be translated, template instructions or component description text for the fields are also items that are helpful to enter into your global site dictionary.