## Opening the correct language variant before you edit
Before you change any translated content in Sherkety ERP & Website Platform, make sure you are editing the right language version of the page or content entry. Start from the **Content** area in the admin section, open the page or section you want to update, and check the language control in the editor header before typing into any field.

1. Open the content item you want to edit from **Admin > Content**.
2. In the editor header, find the **language selector** and choose the language you want to work on.
3. Confirm the active language shown in the editor before updating fields such as **Title**, **Summary**, or body content.
4. Look at each field carefully to see whether it behaves as a translated field or a shared field.
5. If the page has not been fully prepared in its main version yet, finish the source content first so you have a clear version to translate.

Use the language selector every time you switch from one translation to another. This is especially important when you are moving quickly between Arabic and English content, because the same page can show different values depending on the selected language.

Not every field changes by language. In Sherkety ERP & Website Platform, some page details stay shared across all language versions. These are usually page-level settings rather than reader-facing text. For example, a page identifier, publishing state, or other global settings may stay the same no matter which language is selected. If you edit one of these shared fields, the change affects the page as a whole rather than only the current language.

[SCREENSHOT: Content editor header showing the language selector and active language label]

If you need a refresher on the editor layout before switching languages, see [Managing Multilingual Fields in the Content Editor](doc:managing-multilingual-fields-in-the-content-editor).

## Updating translated field values in the editor
Once the correct language is selected, update only the fields that belong to that language version. In Sherkety ERP & Website Platform, translated fields usually include reader-facing text such as **Title**, **Summary**, **SEO Title**, **SEO Description**, button labels, and longer body content.

1. Select the target language in the editor header.
2. Click into a translated field such as **Title** or **Summary** and enter the text for that language.
3. Scroll through the editor and update longer content areas, including rich text sections and body copy, while staying in the same language.
4. Review page metadata fields like **SEO Title** and **SEO Description** so search-facing text matches the translated page.
5. Click **Save** and wait for the confirmation message before switching to another language.

When you edit rich text content, keep your focus on the selected language only. Sherkety ERP & Website Platform stores translated values separately for fields that are set up for localization, so updating the Arabic version of a page should not replace the English body copy if you are working in the correct language and field.

If a required translated field is missing, the editor may show a validation message when you try to save. Check the fields highlighted in the form and complete any missing translated values before saving again. This often happens with short but important fields such as **Title** or **SEO Title**, which may be required even when the main body text is still being drafted.

[SCREENSHOT: Localized content form with Title, Summary, SEO Title, SEO Description, and Save button]

For previewing changes while you work, use the process described in [Using Live Preview to Check Page Updates](doc:using-live-preview-to-check-page-updates) rather than switching languages back and forth on the public page.

## Comparing one language version against another
A good translation workflow is not just about entering text. You also need to compare language versions to make sure the page says the same thing in each supported language. In Sherkety ERP & Website Platform, the easiest way to do this is to switch the editor between languages and review the same fields one by one.

1. Open the content item in the editor and note the current values in key fields such as **Title**, **Summary**, body content, **SEO Title**, and **SEO Description**.
2. Change the language using the editor header.
3. Review the same fields in the second language and compare them with the source version.
4. Repeat this process for each supported language until all important fields are aligned.
5. Save any missing or corrected translations before moving on.

Pay special attention to empty fields and fallback behavior. If a field looks blank or appears to still reflect the source language, that usually means the translated value has not been entered yet or the field is not localized. Compare carefully instead of assuming the page is complete.

When the page includes structured sections or repeating items, verify that each language version contains the same set of items in the same order. If one version has three feature blocks and another has only two, the page may feel incomplete even if the visible text is translated correctly. Also check supporting details such as media captions, image alt text, and link labels so they match the surrounding translated content.

[SCREENSHOT: Editor showing one language selected, with the same page reopened in another language for comparison]

If you are comparing sections that contain repeated cards, lists, or grouped content, the next guide on [Managing Repeating Content Items in the Editor](doc:managing-repeating-content-items-in-the-editor) will help with that part in more detail.

## Keeping localized page structure aligned across languages
In Sherkety ERP & Website Platform, page structure and page text do not always behave the same way. Some parts of a page are shared across all languages, while the wording inside those parts can be translated separately. When you update multilingual content, keep the structure aligned so visitors see the same sections, calls to action, and flow regardless of language.

1. Review the page section by section after selecting the source language.
2. Switch to the translated language and confirm the same sections appear in the same order.
3. Update translated text inside each section without changing the intended layout.
4. Check repeatable blocks, cards, or grouped items to make sure the translated version has matching entries.
5. Save and recheck navigation labels, button text, and links in each language.

This matters most when the source page has recently changed. If someone adds a new homepage section, removes a feature card, or reorders content blocks, translated versions can drift out of sync unless you review them deliberately. Keep the same block order whenever possible so readers in every language move through the page in the same sequence.

Also review labels tied to actions, such as buttons and links. A translated page may have correct body text but still show an outdated call to action, navigation label, or internal link label. These smaller fields are easy to miss, especially when you are focused on longer content.

For pages with modular sections, it helps to compare from top to bottom instead of jumping around the editor. That makes it easier to spot a missing block, an untranslated heading, or a section that was added in one language but not updated in another.

[SCREENSHOT: Multi-section content editor with repeated blocks and translated labels]

## Managing permissions and publishing translated content
Access to multilingual editing in Sherkety ERP & Website Platform depends on your sign-in permissions. The admin area includes protected pages, so not every signed-in user can open the **Content** area, edit translated fields, or publish changes. If you can reach **Admin > Content**, your account already has access to at least part of the content workflow.

Editors typically work with the language versions available to their account. If a language does not appear in the language selector, it may not be enabled for your workspace or your role may not be allowed to edit it. In that case, you will need help from someone who manages admin access or site settings.

When you click **Save** in a translated page, the result depends on whether the field is localized or shared:

| What you edit | What the save affects |
|---|---|
| Translated text fields such as **Title**, **Summary**, or body content | The currently selected language version |
| Shared page settings such as global page details | All language versions tied to that page |

Publishing can also feel different when some translations are complete and others are still in progress. A page may have shared page settings already in place while one language version still needs translated text. Always review the active language before saving or publishing so you do not assume another language is ready just because the page itself already exists.

If you cannot open admin pages such as **Dashboard**, **Content**, **Users**, **Settings**, or other restricted areas, review [Managing Users and Role Based Access](doc:managing-users-and-role-based-access) and [Understanding Role Visibility and Access Restrictions](doc:understanding-role-visibility-and-access-restrictions).

## Fixing missing translations, overwritten values, and locale mismatches
Most multilingual editing problems in Sherkety ERP & Website Platform come from one of three issues: the wrong language was selected, the field is shared instead of translated, or the translated page structure no longer matches the source version. When something looks wrong, troubleshoot field by field instead of trying to fix the whole page at once.

- **A translated field is blank after switching languages**
  - Check the language selector in the editor header and confirm you are viewing the intended language.
  - Make sure you clicked **Save** after entering the translated text.
  - Compare the same field in another language to confirm whether it is truly missing or simply not localized.

- **Editing one language changed all languages**
  - Review whether the field is a shared page field rather than a translated field.
  - If a page-level setting changed everywhere, that is expected behavior for shared values.
  - Reopen the page and test with a clearly translated field such as **Title** or **SEO Description**.

- **One language version looks incomplete**
  - Compare the page section by section.
  - Check headings, body text, metadata, repeated items, link labels, and media text.
  - Look for missing cards, reordered blocks, or untranslated action buttons.

- **You cannot access a language or publish its content**
  - Confirm the language appears in the language selector.
  - Check whether your account can access the required admin area.
  - Ask an administrator to review enabled languages or your editing permissions.

[SCREENSHOT: Content editor showing a blank translated field, validation message, and language selector]

For save errors, warning messages, or missing content states, see [Validating Saving and Reviewing Content Changes](doc:validating-saving-and-reviewing-content-changes) and [Recognizing Warnings Errors and Dismissible Notices](doc:recognizing-warnings-errors-and-dismissible-notices).

## Overview
Sherkety ERP & Website Platform lets content editors maintain public website content in more than one language from the same editing workspace. The key to working smoothly is knowing which parts of a page are language-specific and which parts are shared across every version of that page.

This guide focuses on four practical tasks:

- choosing the correct language from the editor header before you begin
- updating translated fields such as **Title**, **Summary**, body text, and search-facing text
- comparing one language version against another to catch gaps
- keeping page sections, repeated items, and action labels aligned across languages

You will use these steps most often when editing public-facing pages such as service pages, company guidance pages, ERP product pages, and shared website sections. Because Sherkety ERP & Website Platform supports both public content and admin configuration, it is important to distinguish between text that should change by language and settings that should stay the same for everyone.

This guide does not repeat the full live preview workflow. If you want to check how your edits appear before or after saving, use [Using Live Preview to Check Page Updates](doc:using-live-preview-to-check-page-updates). It also does not go deep into repeated content structures, since that is covered next in [Managing Repeating Content Items in the Editor](doc:managing-repeating-content-items-in-the-editor).

Use this page when you need to answer questions like:

- “Am I editing the Arabic or English version right now?”
- “Why did this field change in every language?”
- “Why is one page version missing content?”
- “Which fields should I compare before I publish?”

## Prerequisites
Before you edit localized content in Sherkety ERP & Website Platform, make sure the basics are already in place. This will help you avoid saving changes in the wrong language or spending time translating content that is still changing in the source version.

- You can sign in to the admin area and open **Admin > Content**.
- Your account has permission to edit website content.
- The page, section, or content entry you want to translate already exists.
- The source-language version is complete enough to use as a reference.
- You know which supported language you are expected to update.
- You are familiar with the editor layout and save flow.

It also helps if you have already worked through these related guides:

- [Editing Multilingual Content in the Editor](doc:editing-multilingual-content-in-the-editor)
- [Managing Multilingual Fields in the Content Editor](doc:managing-multilingual-fields-in-the-content-editor)
- [Using Live Preview to Check Page Updates](doc:using-live-preview-to-check-page-updates)

Before starting, open the page once and scan the available fields. Look for obvious translated text such as **Title**, **Summary**, body content, and search-facing fields. Then note any page-level settings that appear to stay the same no matter which language is selected. That quick check makes it much easier to avoid accidental changes to shared values.

If your team recently changed the source page by adding sections, removing blocks, or updating calls to action, plan to compare the translated version section by section after editing. The next guide, [Managing Repeating Content Items in the Editor](doc:managing-repeating-content-items-in-the-editor), is the best follow-up when your translated pages include cards, lists, grouped items, or other repeated content.